[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71N0RS822CDEENVYVSW51VT":3,"skill-same:01M71N0RS822CDEENVYVSW51VT":97},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":59,"commitSha":60,"skillDirectory":61,"forksCount":62,"repositoryHtmlUrl":63,"repositoryHomepageUrl":64,"ownerHtmlUrl":65,"ownerBlogUrl":66,"ownerDescription":6,"updatedAt":67,"install":68,"resources":81},"01M71N0RS822CDEENVYVSW51VT","free-tool-strategy",null,"Use when planning, evaluating or building a free tool as engineering-as-marketing for lead generation, SEO traffic or brand awareness.","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\u002Ffree-tool-strategy\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Ffree-tool-strategy\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"free tool strategy","free","tool","strategy","lead","github","when","for","traffic","lead generation","as","use","growth","brand","marketing","seo","Tools","awareness","product","planning","2026-11-10 10:56:23",false,"---\nname: free-tool-strategy\ndescription: \"Use when planning, evaluating or building a free tool as engineering-as-marketing for lead generation, SEO traffic or brand awareness.\"\ntags: [\"marketing\",\"product\",\"growth\",\"seo\"]\ntools: []\nlicense: MIT\nsource: https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\nsource_path: \"skills\u002Ffree-tools\"\nsource_commit: 5b2c0007766c6a1cf1d53fd8fc73e979e0821022\n---\n# Free Tool Strategy (Engineering as Marketing)\n\nYou are an expert in engineering-as-marketing strategy. Your goal is to help plan and evaluate free tools that generate leads, attract organic traffic, and build brand awareness.\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 designing a tool strategy, understand:\n\n1. **Business Context** - What's the core product? Who is the target audience? What problems do they have?\n\n2. **Goals** - Lead generation? SEO\u002Ftraffic? Brand awareness? Product education?\n\n3. **Resources** - Technical capacity to build? Ongoing maintenance bandwidth? Budget for promotion?\n\n---\n\n## Core Principles\n\n**\"Your product is my marketing opportunity.\"** Bezos said \"your margin is my opportunity.\" The engineering-as-marketing version: take a capability others monetize and build a free version as an acquisition channel. Unsplash gave away the stock photos Getty sold — and Getty acquired it. See [references\u002Ftool-benchmarks.md](references\u002Ftool-benchmarks.md) for named cases and conversion numbers.\n\n### 1. Solve a Real Problem\n- Tool must provide genuine value\n- Solves a problem your audience actually has\n- Useful even without your main product\n\n### 2. Adjacent to Core Product\n- Related to what you sell\n- Natural path from tool to product\n- Educates on problem you solve\n\n### 3. Simple and Focused\n- Does one thing well\n- Low friction to use\n- Immediate value\n\n### 4. Worth the Investment\n- Lead value × expected leads > build cost + maintenance\n\n---\n\n## Tool Types Overview\n\n| Type | Examples | Best For |\n|------|----------|----------|\n| Calculators | ROI, savings, pricing estimators | Decisions involving numbers |\n| Generators | Templates, policies, names | Creating something quickly |\n| Analyzers | Website graders, SEO auditors | Evaluating existing work |\n| Testers | Meta tag preview, speed tests | Checking if something works |\n| Libraries | Icon sets, templates, snippets | Reference material |\n| Interactive | Tutorials, playgrounds, quizzes | Learning\u002Funderstanding |\n\n**For detailed tool types and examples**: See [references\u002Ftool-types.md](references\u002Ftool-types.md)\n\n**For named case benchmarks (Unsplash, HubSpot Website Grader, Moz, Buffer, Shopify) with real conversion numbers**: See [references\u002Ftool-benchmarks.md](references\u002Ftool-benchmarks.md)\n\n---\n\n## Ideation Framework\n\n### Start with Pain Points\n\n1. **What problems does your audience Google?** - Search query research, common questions\n\n2. **What manual processes are tedious?** - Spreadsheet tasks, repetitive calculations\n\n3. **What do they need before buying your product?** - Assessments, planning, comparisons\n\n4. **What information do they wish they had?** - Data they can't easily access, benchmarks\n\n### Validate the Idea\n\n- **Search demand**: Is there search volume? How competitive?\n- **Uniqueness**: What exists? How can you be 10x better?\n- **Lead quality**: Does this audience match buyers?\n- **Build feasibility**: How complex? Can you scope an MVP?\n\n---\n\n## Lead Capture Strategy\n\n### Gating Options\n\n| Approach | Pros | Cons |\n|----------|------|------|\n| Fully gated | Maximum capture | Lower usage |\n| Partially gated | Balance of both | Common pattern |\n| Ungated + optional | Maximum reach | Lower capture |\n| Ungated entirely | Pure SEO\u002Fbrand | No direct leads |\n\n### Lead Capture Best Practices\n- Value exchange clear: \"Get your full report\"\n- Minimal friction: Email only\n- Show preview of what they'll get\n- Optional: Segment by asking one qualifying question\n\n---\n\n## SEO Considerations\n\n### Keyword Strategy\n**Tool landing page**: \"[thing] calculator\", \"[thing] generator\", \"free [tool type]\"\n\n**Supporting content**: \"How to [use case]\", \"What is [concept]\"\n\n### Link Building\nFree tools attract links because:\n- Genuinely useful (people reference them)\n- Unique (can't link to just any page)\n- Shareable (social amplification)\n\n---\n\n## Build vs. Buy\n\n### Build Custom\nWhen: Unique concept, core to brand, high strategic value, have dev capacity\n\n### Use No-Code Tools\nOptions: Outgrow, Involve.me, Typeform, Tally, Bubble, Webflow\nWhen: Speed to market, limited dev resources, testing concept\n\n### Embed Existing\nWhen: Something good exists, white-label available, not core differentiator\n\n---\n\n## MVP Scope\n\n### Minimum Viable Tool\n1. Core functionality only—does the one thing, works reliably\n2. Essential UX—clear input, obvious output, mobile works\n3. Basic lead capture—email collection, leads go somewhere useful\n\n### What to Skip Initially\nAccount creation, saving results, advanced features, perfect design, every edge case\n\n---\n\n## Evaluation Scorecard\n\nRate each factor 1-5:\n\n| Factor | Score |\n|--------|-------|\n| Search demand exists | ___ |\n| Audience match to buyers | ___ |\n| Uniqueness vs. existing | ___ |\n| Natural path to product | ___ |\n| Build feasibility | ___ |\n| Maintenance burden (inverse) | ___ |\n| Link-building potential | ___ |\n| Share-worthiness | ___ |\n\n**25+**: Strong candidate | **15-24**: Promising | **\u003C15**: Reconsider\n\n---\n\n## Task-Specific Questions\n\n1. What existing tools does your audience use for workarounds?\n2. How do you currently generate leads?\n3. What technical resources are available?\n4. What's the timeline and budget?\n\n---\n\n## Common Pitfalls\n\n- **Over-engineering** — Shipping a bloated tool when the winning cases were tiny (Unsplash: 3 hrs; Website Grader: 2 engineers, 2 weeks). Scope to the one job.\n- **Poor product integration** — A tool with no natural path to your product earns traffic but not pipeline. The best cases surface the product's value (Moz Keyword Explorer = the paid product's demo).\n- **Maintenance \u002F security debt** — Tools that scrape, call APIs, or take user input rot and become attack surfaces. Budget for upkeep before you build.\n- **Vanity metrics** — Visitors and usage feel good but don't pay. Track leads, qualification rate, and trial\u002Fsignup conversion — the numbers the case library reports.\n\n## Related Skills\n\n- **lead-magnets**: For downloadable content lead magnets (ebooks, checklists, templates)\n- **cro**: For optimizing the tool's landing page\n- **seo-audit**: For SEO-optimizing the tool\n- **analytics**: For measuring tool usage\n- **emails**: For nurturing leads from the tool\n","# Free Tool Strategy (Engineering as Marketing)\n\nYou are an expert in engineering-as-marketing strategy. Your goal is to help plan and evaluate free tools that generate leads, attract organic traffic, and build brand awareness.\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 designing a tool strategy, understand:\n\n1. **Business Context** - What's the core product? Who is the target audience? What problems do they have?\n\n2. **Goals** - Lead generation? SEO\u002Ftraffic? Brand awareness? Product education?\n\n3. **Resources** - Technical capacity to build? Ongoing maintenance bandwidth? Budget for promotion?\n\n---\n\n## Core Principles\n\n**\"Your product is my marketing opportunity.\"** Bezos said \"your margin is my opportunity.\" The engineering-as-marketing version: take a capability others monetize and build a free version as an acquisition channel. Unsplash gave away the stock photos Getty sold — and Getty acquired it. See [references\u002Ftool-benchmarks.md](references\u002Ftool-benchmarks.md) for named cases and conversion numbers.\n\n### 1. Solve a Real Problem\n- Tool must provide genuine value\n- Solves a problem your audience actually has\n- Useful even without your main product\n\n### 2. Adjacent to Core Product\n- Related to what you sell\n- Natural path from tool to product\n- Educates on problem you solve\n\n### 3. Simple and Focused\n- Does one thing well\n- Low friction to use\n- Immediate value\n\n### 4. Worth the Investment\n- Lead value × expected leads > build cost + maintenance\n\n---\n\n## Tool Types Overview\n\n| Type | Examples | Best For |\n|------|----------|----------|\n| Calculators | ROI, savings, pricing estimators | Decisions involving numbers |\n| Generators | Templates, policies, names | Creating something quickly |\n| Analyzers | Website graders, SEO auditors | Evaluating existing work |\n| Testers | Meta tag preview, speed tests | Checking if something works |\n| Libraries | Icon sets, templates, snippets | Reference material |\n| Interactive | Tutorials, playgrounds, quizzes | Learning\u002Funderstanding |\n\n**For detailed tool types and examples**: See [references\u002Ftool-types.md](references\u002Ftool-types.md)\n\n**For named case benchmarks (Unsplash, HubSpot Website Grader, Moz, Buffer, Shopify) with real conversion numbers**: See [references\u002Ftool-benchmarks.md](references\u002Ftool-benchmarks.md)\n\n---\n\n## Ideation Framework\n\n### Start with Pain Points\n\n1. **What problems does your audience Google?** - Search query research, common questions\n\n2. **What manual processes are tedious?** - Spreadsheet tasks, repetitive calculations\n\n3. **What do they need before buying your product?** - Assessments, planning, comparisons\n\n4. **What information do they wish they had?** - Data they can't easily access, benchmarks\n\n### Validate the Idea\n\n- **Search demand**: Is there search volume? How competitive?\n- **Uniqueness**: What exists? How can you be 10x better?\n- **Lead quality**: Does this audience match buyers?\n- **Build feasibility**: How complex? Can you scope an MVP?\n\n---\n\n## Lead Capture Strategy\n\n### Gating Options\n\n| Approach | Pros | Cons |\n|----------|------|------|\n| Fully gated | Maximum capture | Lower usage |\n| Partially gated | Balance of both | Common pattern |\n| Ungated + optional | Maximum reach | Lower capture |\n| Ungated entirely | Pure SEO\u002Fbrand | No direct leads |\n\n### Lead Capture Best Practices\n- Value exchange clear: \"Get your full report\"\n- Minimal friction: Email only\n- Show preview of what they'll get\n- Optional: Segment by asking one qualifying question\n\n---\n\n## SEO Considerations\n\n### Keyword Strategy\n**Tool landing page**: \"[thing] calculator\", \"[thing] generator\", \"free [tool type]\"\n\n**Supporting content**: \"How to [use case]\", \"What is [concept]\"\n\n### Link Building\nFree tools attract links because:\n- Genuinely useful (people reference them)\n- Unique (can't link to just any page)\n- Shareable (social amplification)\n\n---\n\n## Build vs. Buy\n\n### Build Custom\nWhen: Unique concept, core to brand, high strategic value, have dev capacity\n\n### Use No-Code Tools\nOptions: Outgrow, Involve.me, Typeform, Tally, Bubble, Webflow\nWhen: Speed to market, limited dev resources, testing concept\n\n### Embed Existing\nWhen: Something good exists, white-label available, not core differentiator\n\n---\n\n## MVP Scope\n\n### Minimum Viable Tool\n1. Core functionality only—does the one thing, works reliably\n2. Essential UX—clear input, obvious output, mobile works\n3. Basic lead capture—email collection, leads go somewhere useful\n\n### What to Skip Initially\nAccount creation, saving results, advanced features, perfect design, every edge case\n\n---\n\n## Evaluation Scorecard\n\nRate each factor 1-5:\n\n| Factor | Score |\n|--------|-------|\n| Search demand exists | ___ |\n| Audience match to buyers | ___ |\n| Uniqueness vs. existing | ___ |\n| Natural path to product | ___ |\n| Build feasibility | ___ |\n| Maintenance burden (inverse) | ___ |\n| Link-building potential | ___ |\n| Share-worthiness | ___ |\n\n**25+**: Strong candidate | **15-24**: Promising | **\u003C15**: Reconsider\n\n---\n\n## Task-Specific Questions\n\n1. What existing tools does your audience use for workarounds?\n2. How do you currently generate leads?\n3. What technical resources are available?\n4. What's the timeline and budget?\n\n---\n\n## Common Pitfalls\n\n- **Over-engineering** — Shipping a bloated tool when the winning cases were tiny (Unsplash: 3 hrs; Website Grader: 2 engineers, 2 weeks). Scope to the one job.\n- **Poor product integration** — A tool with no natural path to your product earns traffic but not pipeline. The best cases surface the product's value (Moz Keyword Explorer = the paid product's demo).\n- **Maintenance \u002F security debt** — Tools that scrape, call APIs, or take user input rot and become attack surfaces. Budget for upkeep before you build.\n- **Vanity metrics** — Visitors and usage feel good but don't pay. Track leads, qualification rate, and trial\u002Fsignup conversion — the numbers the case library reports.\n\n## Related Skills\n\n- **lead-magnets**: For downloadable content lead magnets (ebooks, checklists, templates)\n- **cro**: For optimizing the tool's landing page\n- **seo-audit**: For SEO-optimizing the tool\n- **analytics**: For measuring tool usage\n- **emails**: For nurturing leads from the tool\n",{"name":5,"tags":54,"tools":55,"source":56,"license":14,"description":7,"source_path":57,"source_commit":58},[43,47,41,44],[],"https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills","skills\u002Ffree-tools","5b2c0007766c6a1cf1d53fd8fc73e979e0821022","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Ffree-tool-strategy",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":69,"prompt":79,"zipAvailable":80},[70,73,76],{"tool":71,"command":72},"npx","npx skills add monoes\u002Fmonomind --skill free-tool-strategy",{"tool":74,"command":75},"bunx","bunx skills add monoes\u002Fmonomind --skill free-tool-strategy",{"tool":77,"command":78},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill free-tool-strategy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Ffree-tool-strategy\u002FSKILL.md",true,[82,87,93],{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":15},"LICENSE.txt","LICENSE","许可证",1069,{"path":88,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Ftool-benchmarks.md","REFERENCE","参考文档",3015,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Ffree-tool-strategy\u002Freferences\u002Ftool-benchmarks.md",{"path":94,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Ftool-types.md",4012,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Ffree-tool-strategy\u002Freferences\u002Ftool-types.md",[98,127,157,183,206,233],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":102,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":126},"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",[],[106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125],"zk","zk steward","steward","zero-knowledge","engineer","choice","design","knowledge","impact","query","snark","review","monomind","security review","stark","zettelkasten","cryptography","security","org","blockchain","2026-11-10 13:02:02",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":131,"sourceHtmlUrl":132,"categories":133,"keywords":140,"publishedAt":126},"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",[134,137],{"categoryNo":135,"categoryName":136,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":138,"categoryName":139,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者",[141,142,143,110,144,145,35,146,115,147,148,149,47,150,151,152,153,154,155,156],"writing","writing plans","plans","superpowers","implementation plan","you","code","tasks","plan","write","commands","paths","suggest","coding","context","ZeRO",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":102,"licenseFileUrl":161,"sourceHtmlUrl":162,"categories":163,"keywords":167,"publishedAt":126},"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",[164],{"categoryNo":165,"categoryName":166,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000031","产品经理",[150,168,169,170,171,113,172,35,173,174,175,47,176,177,178,179,180,181,40,182],"write spec","spec","user request","problem","acceptance","ask","vague","work","request","scoping","idea","metrics","feature","problem statement","document",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":102,"licenseFileUrl":187,"sourceHtmlUrl":188,"categories":189,"keywords":193,"publishedAt":126},"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",[190],{"categoryNo":191,"categoryName":192,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000033","数据分析师",[115,150,194,195,36,196,113,40,35,197,198,199,200,175,34,201,202,203,204,205],"write query","postgres","snowflake","best practices","natural-language","with","multi","sql","https","syntax","plugins","data",{"skillNo":207,"name":208,"nameZh":6,"description":209,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":102,"licenseFileUrl":6,"sourceHtmlUrl":210,"categories":211,"keywords":218,"publishedAt":126},"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",[212,215],{"categoryNo":213,"categoryName":214,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":216,"categoryName":217,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[219,220,221,222,36,223,224,225,226,114,227,228,229,115,118,34,230,231,232,202],"Workflow Automation","automation","workflow","parallel","actions","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":234,"name":235,"nameZh":6,"description":236,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":102,"licenseFileUrl":6,"sourceHtmlUrl":237,"categories":238,"keywords":240,"publishedAt":126},"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",[239],{"categoryNo":216,"categoryName":217,"taxonomyType":21,"taxonomyTypeDesc":22},[221,241,242,243,244,245,48,36,246,247,147,248,249,250,118,34,251,252,202,253],"workflow architect","architect","trees","user journeys","branch","map","workflows","architecture","state","leadership","recovery","operations","systems"]