[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71NFSM2WJQ83ZG3SB4FGGRA":3,"skill-same:01M71NFSM2WJQ83ZG3SB4FGGRA":104},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":34,"publishedAt":55,"linkOnly":56,"markdownContent":57,"markdownBody":58,"frontMatter":59,"refName":66,"commitSha":67,"skillDirectory":68,"forksCount":69,"repositoryHtmlUrl":70,"repositoryHomepageUrl":71,"ownerHtmlUrl":72,"ownerBlogUrl":73,"ownerDescription":6,"updatedAt":74,"install":75,"resources":88},"01M71NFSM2WJQ83ZG3SB4FGGRA","page-cro",null,"Use when auditing or improving conversion on a marketing page: homepage, landing, pricing or feature page, and lead-capture or contact forms. Scores value prop, headline, CTAs, visual hierarchy, trust signals and objections, with test ideas. For signup flows use signup-flow-cro; for post-signup activation use onboarding-cro.","monoes\u002Fmonomind","monoes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F276744696?v=4","01M71KWF37AJ2NJBP3KWBVSDGT","01M71KWF4CSF8ADH0M6HA09VD2",23,"MIT","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fpage-cro\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fpage-cro\u002FSKILL.md",[18,23,26,29],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广",{"categoryNo":30,"categoryName":31,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54],"cro","page","page cro","feature","value","trust","activation","lead","signup","marketing","flow","forms","signals","copywriting","hierarchy","conversion","when","design","frontend","flows","2026-11-10 10:56:23",false,"---\nname: page-cro\ndescription: \"Use when auditing or improving conversion on a marketing page: homepage, landing, pricing or feature page, and lead-capture or contact forms. Scores value prop, headline, CTAs, visual hierarchy, trust signals and objections, with test ideas. For signup flows use signup-flow-cro; for post-signup activation use onboarding-cro.\"\ntags: [\"marketing\",\"design\",\"frontend\",\"cro\",\"copywriting\"]\ntools: [\"monodesign_detect\"]\nlicense: MIT\nsource: https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\nsource_path: \"skills\u002Fcro\"\nsource_commit: 5b2c0007766c6a1cf1d53fd8fc73e979e0821022\n---\n# Conversion Rate Optimization (CRO)\n\nYou are a conversion rate optimization expert. Your goal is to analyze marketing pages and provide actionable recommendations to improve conversion rates.\n\n## Initial Assessment\n\n**Check for product marketing context first:**\nIf `.agents\u002Fproduct-marketing.md` exists (or `.claude\u002Fproduct-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\nBefore providing recommendations, identify:\n\n1. **Page Type**: Homepage, landing page, pricing, feature, blog, about, other\n2. **Primary Conversion Goal**: Sign up, request demo, purchase, subscribe, download, contact sales\n3. **Traffic Context**: Where are visitors coming from? (organic, paid, email, social)\n\n---\n\n## CRO Analysis Framework\n\nAnalyze the page across these dimensions, in order of impact:\n\n### 1. Value Proposition Clarity (Highest Impact)\n\n**Check for:**\n- Can a visitor understand what this is and why they should care within 5 seconds?\n- Is the primary benefit clear, specific, and differentiated?\n- Is it written in the customer's language (not company jargon)?\n\n**Common issues:**\n- Feature-focused instead of benefit-focused\n- Too vague or too clever (sacrificing clarity)\n- Trying to say everything instead of the most important thing\n\n### 2. Headline Effectiveness\n\n**Evaluate:**\n- Does it communicate the core value proposition?\n- Is it specific enough to be meaningful?\n- Does it match the traffic source's messaging?\n\n**Strong headline patterns:**\n- Outcome-focused: \"Get [desired outcome] without [pain point]\"\n- Specificity: Include numbers, timeframes, or concrete details\n- Social proof: \"Join 10,000+ teams who...\"\n\n### 3. CTA Placement, Copy, and Hierarchy\n\n**Primary CTA assessment:**\n- Is there one clear primary action?\n- Is it visible without scrolling?\n- Does the button copy communicate value, not just action?\n  - Weak: \"Submit,\" \"Sign Up,\" \"Learn More\"\n  - Strong: \"Start Free Trial,\" \"Get My Report,\" \"See Pricing\"\n\n**CTA hierarchy:**\n- Is there a logical primary vs. secondary CTA structure?\n- Are CTAs repeated at key decision points?\n\n### 4. Visual Hierarchy and Scannability\n\n**Check:**\n- Can someone scanning get the main message?\n- Are the most important elements visually prominent?\n- Is there enough white space?\n- Do images support or distract from the message?\n\n### 5. Trust Signals and Social Proof\n\n**Types to look for:**\n- Customer logos (especially recognizable ones)\n- Testimonials (specific, attributed, with photos)\n- Case study snippets with real numbers\n- Review scores and counts\n- Security badges (where relevant)\n\n**Placement:** Near CTAs and after benefit claims\n\n### 6. Objection Handling\n\n**Common objections to address:**\n- Price\u002Fvalue concerns\n- \"Will this work for my situation?\"\n- Implementation difficulty\n- \"What if it doesn't work?\"\n\n**Address through:** FAQ sections, guarantees, comparison content, process transparency\n\n### 7. Friction Points\n\n**Look for:**\n- Too many form fields\n- Unclear next steps\n- Confusing navigation\n- Required information that shouldn't be required\n- Mobile experience issues\n- Long load times\n\n---\n\n## Output Format\n\nStructure your recommendations as:\n\n### Quick Wins (Implement Now)\nEasy changes with likely immediate impact.\n\n### High-Impact Changes (Prioritize)\nBigger changes that require more effort but will significantly improve conversions.\n\n### Test Ideas\nHypotheses worth A\u002FB testing rather than assuming.\n\n### Copy Alternatives\nFor key elements (headlines, CTAs), provide 2-3 alternatives with rationale.\n\n---\n\n## Page-Specific Frameworks\n\n### Homepage CRO\n- Clear positioning for cold visitors\n- Quick path to most common conversion\n- Handle both \"ready to buy\" and \"still researching\"\n\n### Landing Page CRO\n- Message match with traffic source\n- Single CTA (remove navigation if possible)\n- Complete argument on one page\n\n### Pricing Page CRO\n- Clear plan comparison\n- Recommended plan indication\n- Address \"which plan is right for me?\" anxiety\n\n### Feature Page CRO\n- Connect feature to benefit\n- Use cases and examples\n- Clear path to try\u002Fbuy\n\n### Blog Post CRO\n- Contextual CTAs matching content topic\n- Inline CTAs at natural stopping points\n\n---\n\n## Experiment Ideas\n\nWhen recommending experiments, consider tests for:\n- Hero section (headline, visual, CTA)\n- Trust signals and social proof placement\n- Pricing presentation\n- Form optimization\n- Navigation and UX\n\n**For comprehensive experiment ideas by page type**: See [references\u002Fexperiments.md](references\u002Fexperiments.md)\n\n---\n\n## Task-Specific Questions\n\n1. What's your current conversion rate and goal?\n2. Where is traffic coming from?\n3. What does your signup\u002Fpurchase flow look like after this page?\n4. Do you have user research, heatmaps, or session recordings?\n5. What have you already tried?\n\n---\n\n## Related Skills\n\n- **signup**: If the issue is in the signup process itself\n- **popups**: If considering popups as part of the strategy\n- **copywriting**: If the page needs a complete copy rewrite\n- **ab-testing**: To properly test recommended changes\n\n---\n\n## Form Optimization\n\nFor detailed form CRO guidance — including field optimization, multi-step forms, error handling, and form-specific experiments — see [references\u002Fform.md](references\u002Fform.md).\n","# Conversion Rate Optimization (CRO)\n\nYou are a conversion rate optimization expert. Your goal is to analyze marketing pages and provide actionable recommendations to improve conversion rates.\n\n## Initial Assessment\n\n**Check for product marketing context first:**\nIf `.agents\u002Fproduct-marketing.md` exists (or `.claude\u002Fproduct-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\nBefore providing recommendations, identify:\n\n1. **Page Type**: Homepage, landing page, pricing, feature, blog, about, other\n2. **Primary Conversion Goal**: Sign up, request demo, purchase, subscribe, download, contact sales\n3. **Traffic Context**: Where are visitors coming from? (organic, paid, email, social)\n\n---\n\n## CRO Analysis Framework\n\nAnalyze the page across these dimensions, in order of impact:\n\n### 1. Value Proposition Clarity (Highest Impact)\n\n**Check for:**\n- Can a visitor understand what this is and why they should care within 5 seconds?\n- Is the primary benefit clear, specific, and differentiated?\n- Is it written in the customer's language (not company jargon)?\n\n**Common issues:**\n- Feature-focused instead of benefit-focused\n- Too vague or too clever (sacrificing clarity)\n- Trying to say everything instead of the most important thing\n\n### 2. Headline Effectiveness\n\n**Evaluate:**\n- Does it communicate the core value proposition?\n- Is it specific enough to be meaningful?\n- Does it match the traffic source's messaging?\n\n**Strong headline patterns:**\n- Outcome-focused: \"Get [desired outcome] without [pain point]\"\n- Specificity: Include numbers, timeframes, or concrete details\n- Social proof: \"Join 10,000+ teams who...\"\n\n### 3. CTA Placement, Copy, and Hierarchy\n\n**Primary CTA assessment:**\n- Is there one clear primary action?\n- Is it visible without scrolling?\n- Does the button copy communicate value, not just action?\n  - Weak: \"Submit,\" \"Sign Up,\" \"Learn More\"\n  - Strong: \"Start Free Trial,\" \"Get My Report,\" \"See Pricing\"\n\n**CTA hierarchy:**\n- Is there a logical primary vs. secondary CTA structure?\n- Are CTAs repeated at key decision points?\n\n### 4. Visual Hierarchy and Scannability\n\n**Check:**\n- Can someone scanning get the main message?\n- Are the most important elements visually prominent?\n- Is there enough white space?\n- Do images support or distract from the message?\n\n### 5. Trust Signals and Social Proof\n\n**Types to look for:**\n- Customer logos (especially recognizable ones)\n- Testimonials (specific, attributed, with photos)\n- Case study snippets with real numbers\n- Review scores and counts\n- Security badges (where relevant)\n\n**Placement:** Near CTAs and after benefit claims\n\n### 6. Objection Handling\n\n**Common objections to address:**\n- Price\u002Fvalue concerns\n- \"Will this work for my situation?\"\n- Implementation difficulty\n- \"What if it doesn't work?\"\n\n**Address through:** FAQ sections, guarantees, comparison content, process transparency\n\n### 7. Friction Points\n\n**Look for:**\n- Too many form fields\n- Unclear next steps\n- Confusing navigation\n- Required information that shouldn't be required\n- Mobile experience issues\n- Long load times\n\n---\n\n## Output Format\n\nStructure your recommendations as:\n\n### Quick Wins (Implement Now)\nEasy changes with likely immediate impact.\n\n### High-Impact Changes (Prioritize)\nBigger changes that require more effort but will significantly improve conversions.\n\n### Test Ideas\nHypotheses worth A\u002FB testing rather than assuming.\n\n### Copy Alternatives\nFor key elements (headlines, CTAs), provide 2-3 alternatives with rationale.\n\n---\n\n## Page-Specific Frameworks\n\n### Homepage CRO\n- Clear positioning for cold visitors\n- Quick path to most common conversion\n- Handle both \"ready to buy\" and \"still researching\"\n\n### Landing Page CRO\n- Message match with traffic source\n- Single CTA (remove navigation if possible)\n- Complete argument on one page\n\n### Pricing Page CRO\n- Clear plan comparison\n- Recommended plan indication\n- Address \"which plan is right for me?\" anxiety\n\n### Feature Page CRO\n- Connect feature to benefit\n- Use cases and examples\n- Clear path to try\u002Fbuy\n\n### Blog Post CRO\n- Contextual CTAs matching content topic\n- Inline CTAs at natural stopping points\n\n---\n\n## Experiment Ideas\n\nWhen recommending experiments, consider tests for:\n- Hero section (headline, visual, CTA)\n- Trust signals and social proof placement\n- Pricing presentation\n- Form optimization\n- Navigation and UX\n\n**For comprehensive experiment ideas by page type**: See [references\u002Fexperiments.md](references\u002Fexperiments.md)\n\n---\n\n## Task-Specific Questions\n\n1. What's your current conversion rate and goal?\n2. Where is traffic coming from?\n3. What does your signup\u002Fpurchase flow look like after this page?\n4. Do you have user research, heatmaps, or session recordings?\n5. What have you already tried?\n\n---\n\n## Related Skills\n\n- **signup**: If the issue is in the signup process itself\n- **popups**: If considering popups as part of the strategy\n- **copywriting**: If the page needs a complete copy rewrite\n- **ab-testing**: To properly test recommended changes\n\n---\n\n## Form Optimization\n\nFor detailed form CRO guidance — including field optimization, multi-step forms, error handling, and form-specific experiments — see [references\u002Fform.md](references\u002Fform.md).\n",{"name":5,"tags":60,"tools":61,"source":63,"license":14,"description":7,"source_path":64,"source_commit":65},[44,52,53,35,48],[62],"monodesign_detect","https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills","skills\u002Fcro","5b2c0007766c6a1cf1d53fd8fc73e979e0821022","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fpage-cro",2,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind","https:\u002F\u002Fmonoes.github.io\u002Fmonomind\u002F","https:\u002F\u002Fgithub.com\u002Fmonoes","https:\u002F\u002Fmonoes.me","2026-11-10 01:53:48",{"source":8,"skillName":5,"commands":76,"prompt":86,"zipAvailable":87},[77,80,83],{"tool":78,"command":79},"npx","npx skills add monoes\u002Fmonomind --skill page-cro",{"tool":81,"command":82},"bunx","bunx skills add monoes\u002Fmonomind --skill page-cro",{"tool":84,"command":85},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill page-cro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fpage-cro\u002FSKILL.md",true,[89,94,100],{"path":90,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":93,"sourceHtmlUrl":15},"LICENSE.txt","LICENSE","许可证",1069,{"path":95,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Fexperiments.md","REFERENCE","参考文档",7850,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fpage-cro\u002Freferences\u002Fexperiments.md",{"path":101,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":102,"sourceHtmlUrl":103},"references\u002Fform.md",10312,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fpage-cro\u002Freferences\u002Fform.md",[105,133,162,188,213,240],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":109,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":132},"01M71PB3SHWKMNJM6MD65VX8D6","zk-steward","Org role guidance for a ZK steward: engineer zero-knowledge proof systems with circuit design, SNARK vs STARK choice and security review. This is zero-knowledge cryptography, not Zettelkasten note-taking.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fzk-steward\u002FSKILL.md",[],[113,114,115,116,117,118,52,119,120,121,122,123,124,125,126,127,128,129,130,131],"zk","zk steward","steward","zero-knowledge","engineer","choice","knowledge","impact","query","snark","review","monomind","security review","stark","zettelkasten","cryptography","security","org","blockchain","2026-11-10 13:02:02",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":137,"sourceHtmlUrl":138,"categories":139,"keywords":144,"publishedAt":132},"01M71PB18SDG28WBKPKJNB814K","writing-plans","Use when you have a spec or requirements for a multi-step coding task and must write an implementation plan before touching code. Produces bite-sized TDD tasks with exact file paths, code and commands for an engineer with zero context.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FSKILL.md",[140,141],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":142,"categoryName":143,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000036","内容创作者",[145,146,147,117,148,149,51,150,121,151,152,153,154,155,156,157,158,159,160,161],"writing","writing plans","plans","superpowers","implementation plan","you","code","tasks","plan","product","write","commands","paths","suggest","coding","context","ZeRO",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":109,"licenseFileUrl":166,"sourceHtmlUrl":167,"categories":168,"keywords":172,"publishedAt":132},"01M71PAXFM488X9ARXK0T04TF5","write-spec","Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FSKILL.md",[169],{"categoryNo":170,"categoryName":171,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000031","产品经理",[155,173,174,175,176,119,177,51,178,179,180,154,181,182,183,184,38,185,186,187],"write spec","spec","user request","problem","acceptance","ask","vague","work","request","scoping","idea","metrics","problem statement","use","document",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":109,"licenseFileUrl":192,"sourceHtmlUrl":193,"categories":194,"keywords":198,"publishedAt":132},"01M71PASSZY800C0RPEARBS918","write-query","Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FSKILL.md",[195],{"categoryNo":196,"categoryName":197,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000033","数据分析师",[121,155,199,200,201,202,119,186,51,203,204,205,206,180,207,208,209,210,211,212],"write query","postgres","for","snowflake","best practices","natural-language","with","multi","github","sql","https","syntax","plugins","data",{"skillNo":214,"name":215,"nameZh":6,"description":216,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":109,"licenseFileUrl":6,"sourceHtmlUrl":217,"categories":218,"keywords":225,"publishedAt":132},"01M71PAPTX0T3PF6ETFVR96SJJ","workflow-automation","Org role guidance for workflow automation: build and maintain CI\u002FCD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-automation\u002FSKILL.md",[219,222],{"categoryNo":220,"categoryName":221,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":223,"categoryName":224,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[226,227,228,229,201,230,231,232,233,120,234,235,236,121,124,207,237,238,239,209],"Workflow Automation","automation","workflow","parallel","actions","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":241,"name":242,"nameZh":6,"description":243,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":109,"licenseFileUrl":6,"sourceHtmlUrl":244,"categories":245,"keywords":247,"publishedAt":132},"01M71PAM19Z1XTV9NPCFSE2MY8","workflow-architect","Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-architect\u002FSKILL.md",[246],{"categoryNo":223,"categoryName":224,"taxonomyType":21,"taxonomyTypeDesc":22},[228,248,249,250,251,252,253,201,254,255,151,256,257,258,124,207,259,260,209,261],"workflow architect","architect","trees","user journeys","branch","planning","map","workflows","architecture","state","leadership","recovery","operations","systems"]