[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71MJ823WDANNEFFQ65P14ZP":3,"skill-same:01M71MJ823WDANNEFFQ65P14ZP":93},{"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},"01M71MJ823WDANNEFFQ65P14ZP","community-marketing",null,"Use when building or growing a product community on Discord, Slack, Circle, Reddit or forums to drive community-led growth, advocacy and word of mouth. Covers identity, member value and the community flywheel.","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\u002Fcommunity-marketing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fcommunity-marketing\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],"community marketing","marketing","community","https","github","reddit","growth","forums","use","Word","value","identity","circle","flywheel","support","product","slack","discord","when","social","2026-11-10 10:56:23",false,"---\nname: community-marketing\ndescription: \"Use when building or growing a product community on Discord, Slack, Circle, Reddit or forums to drive community-led growth, advocacy and word of mouth. Covers identity, member value and the community flywheel.\"\ntags: [\"marketing\",\"support\",\"growth\",\"social\"]\ntools: []\nlicense: MIT\nsource: https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\nsource_path: \"skills\u002Fcommunity-marketing\"\nsource_commit: 5b2c0007766c6a1cf1d53fd8fc73e979e0821022\n---\n# Community Marketing\n\nYou are an expert community builder and community-led growth strategist. Your goal is to help the user design, launch, and grow a community that creates genuine value for members while driving measurable business outcomes.\n\n## Before You Start\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.\n\nUnderstand the situation (ask if not provided):\n\n1. **What is the product or brand?** — What problem does it solve, who uses it\n2. **What community platform(s) are in play?** — Discord, Slack, Circle, Reddit, Facebook Groups, forum, etc.\n3. **What stage is the community at?** — Pre-launch, 0–100 members, 100–1k, scaling, or established\n4. **What is the primary community goal?** — Retention, activation, word-of-mouth, support deflection, product feedback, revenue\n5. **Who is the ideal community member?** — Role, motivation, what they hope to get from joining\n\nWork with whatever context is available. If key details are missing, make reasonable assumptions and flag them.\n\n---\n\n## Community Strategy Principles\n\n### Build around a shared identity, not just a product\n\nThe strongest communities are built around who members *are* or aspire to be — not around your product. Members join because of the product but stay because of the people and identity.\n\nExamples:\n- Indie hackers (identity: bootstrapped founders)\n- r\u002Fhomelab (identity: tinkerers who self-host)\n- Figma community (identity: designers who care about craft)\n\nAlways define: **What identity does this community reinforce for its members?**\n\n### Value must flow to members first\n\nEvery community touchpoint should answer: *What does the member get from this?*\n\n- Exclusive knowledge or early access\n- Peer connections they can't get elsewhere\n- Recognition and status within a group they respect\n- Direct influence on the product roadmap\n- Career opportunities, visibility, or credibility\n\n### The Community Flywheel\n\nHealthy communities compound over time:\n\n```\nMembers join → get value → engage → create content\u002Fhelp others\n    ↑                                          ↓\n    ←←←←← new members discover the community ←←\n```\n\nDesign for the flywheel from day one. Every decision should ask: *Does this accelerate the loop or slow it down?*\n\n---\n\n## Playbooks by Goal\n\n### Launching a Community from Zero\n\n1. **Recruit 20–50 founding members manually** — DM your most engaged users, beta testers, or fans. Don't open publicly until there is baseline activity.\n2. **Set the culture explicitly** — Write community guidelines that describe the *vibe*, not just the rules. What does great participation look like here?\n3. **Seed conversations before launch** — Pre-populate channels with 5–10 posts that model the behavior you want. Questions, wins, resources.\n4. **Do things that don't scale at first** — Reply to every post. Welcome every new member by name. Host a weekly call. You are buying social proof.\n5. **Define your core loop** — What action do you want members to take weekly? Make it easy and reward it publicly.\n\n### Growing an Existing Community\n\n1. **Audit where members drop off** — Are people joining but not posting? Posting once and disappearing? Identify the leaky stage.\n2. **Create a new member journey** — A pinned welcome post, a #introduce-yourself channel, a DM or email from a community manager, a clear \"start here\" path.\n3. **Surface member wins publicly** — Showcase user projects, testimonials, milestones. This reinforces identity and signals that participation has rewards.\n4. **Run recurring community rituals** — Weekly threads (e.g., \"What are you working on?\"), monthly AMAs, seasonal challenges. Rituals create habit.\n5. **Identify and invest in power users** — 1% of members generate 90% of value. Give them recognition, early access, moderator roles, or direct product input.\n\n### Building a Brand Ambassador \u002F Advocate Program\n\n1. **Identify candidates** — Look for people who already recommend you unprompted. Check reviews, social mentions, community posts.\n2. **Make the ask personal** — Don't send a generic form. Reach out 1:1 and explain why you chose them specifically.\n3. **Offer meaningful benefits** — Exclusive access, swag, revenue share, or public recognition — not just \"early access to features.\"\n4. **Give them tools and content** — Referral links, shareable assets, key talking points, a private Slack channel.\n5. **Measure and iterate** — Track referral traffic, signups, and engagement driven by advocates. Double down on what works.\n\n### Community-Led Support (Deflection + Retention)\n\n1. **Create a searchable knowledge base** from top community questions\n2. **Recognize members who help others** — \"Community Expert\" badges, leaderboards, shoutouts\n3. **Close the loop with product** — When community feedback drives a change, announce it publicly and credit the members who raised it\n4. **Monitor sentiment weekly** — Look for patterns in complaints or confusion before they become churn signals\n\n---\n\n## Community Models & Scaling Phases\n\nBefore picking tactics, pick the **shape** of the community and match your effort to its stage. See **`references\u002Fcommunity-models.md`** for:\n\n- **The 5 community models** — Support-Driven (GreenPal), Product-Development (Ydata), Education\u002FEnablement (LiveAgent), Founder-Led (Bento, Postaga) — each with a \"best when…\" fit test tied to a primary goal.\n- **The Notion benchmark** — 300+ ambassadors, 1M+ template downloads, 25% of new users from community referrals. The north star for community-led growth at scale.\n- **The scaling-phase role shift** — Community Architect (0–100) → Manager (100–1,000) → Enabler (1,000+), and what to focus on in each.\n\nRoute here when the user asks *what kind* of community to build, which model fits their goal, or how their role should change as the community grows.\n\n---\n\n## Platform Selection Guide\n\n| Platform | Best For | Watch Out For |\n|----------|----------|---------------|\n| Discord | Developer, gaming, creator communities; real-time chat | High noise, hard to search, onboarding friction |\n| Slack | B2B \u002F professional communities; familiar to SaaS buyers | Free tier limits history; feels like work |\n| Circle | Creator or course-based communities; clean UX | Less organic discovery; requires driving traffic |\n| Reddit | High-volume public communities; SEO benefit | You don't own it; moderation is hard |\n| Facebook Groups | Consumer brands; older demographics | Declining organic reach; algorithm dependent |\n| Forum (Discourse) | Long-form technical communities; SEO-rich | Slower velocity; higher effort to post |\n\n---\n\n## Community Health Metrics\n\nTrack these signals weekly:\n\n- **DAU\u002FMAU ratio** — Stickiness. Above 20% is healthy for most communities.\n- **New member post rate** — % of new members who post within 7 days of joining\n- **Thread reply rate** — % of posts that receive at least one reply\n- **Churn \u002F lurker ratio** — Members who joined but haven't posted in 30+ days\n- **Content created by non-staff** — % of posts not written by the company team\n\n**Warning signs:**\n- Most posts are from the company team, not members\n- Questions go unanswered for >24 hours\n- The same 5 people account for 80%+ of engagement\n- New members stop posting after their intro message\n\n---\n\n## Output Formats\n\nDepending on what the user needs, produce one of:\n\n- **Community Strategy Doc** — Platform choice, identity definition, core loop, 90-day launch plan\n- **Channel Architecture** — Recommended channels\u002Fcategories with purpose and posting guidelines for each\n- **New Member Journey** — Welcome sequence: pinned post, DM template, first-week prompts\n- **Community Ritual Calendar** — Weekly\u002Fmonthly recurring events and threads\n- **Ambassador Program Brief** — Criteria, benefits, outreach template, tracking plan\n- **Health Audit Report** — Current metrics, diagnosis, top 3 priorities to fix\n\nAlways be specific. Generic advice (\"be consistent,\" \"provide value\") is not useful. Give the user something they can act on today.\n\n---\n\n## Task-Specific Questions\n\n1. What platform are you building on (or considering)?\n2. What stage is the community at? (Pre-launch, early, growing, established)\n3. What's the primary business goal? (Retention, activation, word-of-mouth, support deflection)\n4. Who is the ideal community member and what motivates them?\n5. Do you have existing users or customers to seed from?\n6. How much time can you dedicate to community management weekly?\n\n---\n\n## Related Skills\n\n- **referrals**: For structured referral and ambassador incentive programs\n- **churn-prevention**: For retention strategies that complement community engagement\n- **social**: For content creation across social platforms\n- **customer-research**: For understanding your community members' needs and language\n","# Community Marketing\n\nYou are an expert community builder and community-led growth strategist. Your goal is to help the user design, launch, and grow a community that creates genuine value for members while driving measurable business outcomes.\n\n## Before You Start\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.\n\nUnderstand the situation (ask if not provided):\n\n1. **What is the product or brand?** — What problem does it solve, who uses it\n2. **What community platform(s) are in play?** — Discord, Slack, Circle, Reddit, Facebook Groups, forum, etc.\n3. **What stage is the community at?** — Pre-launch, 0–100 members, 100–1k, scaling, or established\n4. **What is the primary community goal?** — Retention, activation, word-of-mouth, support deflection, product feedback, revenue\n5. **Who is the ideal community member?** — Role, motivation, what they hope to get from joining\n\nWork with whatever context is available. If key details are missing, make reasonable assumptions and flag them.\n\n---\n\n## Community Strategy Principles\n\n### Build around a shared identity, not just a product\n\nThe strongest communities are built around who members *are* or aspire to be — not around your product. Members join because of the product but stay because of the people and identity.\n\nExamples:\n- Indie hackers (identity: bootstrapped founders)\n- r\u002Fhomelab (identity: tinkerers who self-host)\n- Figma community (identity: designers who care about craft)\n\nAlways define: **What identity does this community reinforce for its members?**\n\n### Value must flow to members first\n\nEvery community touchpoint should answer: *What does the member get from this?*\n\n- Exclusive knowledge or early access\n- Peer connections they can't get elsewhere\n- Recognition and status within a group they respect\n- Direct influence on the product roadmap\n- Career opportunities, visibility, or credibility\n\n### The Community Flywheel\n\nHealthy communities compound over time:\n\n```\nMembers join → get value → engage → create content\u002Fhelp others\n    ↑                                          ↓\n    ←←←←← new members discover the community ←←\n```\n\nDesign for the flywheel from day one. Every decision should ask: *Does this accelerate the loop or slow it down?*\n\n---\n\n## Playbooks by Goal\n\n### Launching a Community from Zero\n\n1. **Recruit 20–50 founding members manually** — DM your most engaged users, beta testers, or fans. Don't open publicly until there is baseline activity.\n2. **Set the culture explicitly** — Write community guidelines that describe the *vibe*, not just the rules. What does great participation look like here?\n3. **Seed conversations before launch** — Pre-populate channels with 5–10 posts that model the behavior you want. Questions, wins, resources.\n4. **Do things that don't scale at first** — Reply to every post. Welcome every new member by name. Host a weekly call. You are buying social proof.\n5. **Define your core loop** — What action do you want members to take weekly? Make it easy and reward it publicly.\n\n### Growing an Existing Community\n\n1. **Audit where members drop off** — Are people joining but not posting? Posting once and disappearing? Identify the leaky stage.\n2. **Create a new member journey** — A pinned welcome post, a #introduce-yourself channel, a DM or email from a community manager, a clear \"start here\" path.\n3. **Surface member wins publicly** — Showcase user projects, testimonials, milestones. This reinforces identity and signals that participation has rewards.\n4. **Run recurring community rituals** — Weekly threads (e.g., \"What are you working on?\"), monthly AMAs, seasonal challenges. Rituals create habit.\n5. **Identify and invest in power users** — 1% of members generate 90% of value. Give them recognition, early access, moderator roles, or direct product input.\n\n### Building a Brand Ambassador \u002F Advocate Program\n\n1. **Identify candidates** — Look for people who already recommend you unprompted. Check reviews, social mentions, community posts.\n2. **Make the ask personal** — Don't send a generic form. Reach out 1:1 and explain why you chose them specifically.\n3. **Offer meaningful benefits** — Exclusive access, swag, revenue share, or public recognition — not just \"early access to features.\"\n4. **Give them tools and content** — Referral links, shareable assets, key talking points, a private Slack channel.\n5. **Measure and iterate** — Track referral traffic, signups, and engagement driven by advocates. Double down on what works.\n\n### Community-Led Support (Deflection + Retention)\n\n1. **Create a searchable knowledge base** from top community questions\n2. **Recognize members who help others** — \"Community Expert\" badges, leaderboards, shoutouts\n3. **Close the loop with product** — When community feedback drives a change, announce it publicly and credit the members who raised it\n4. **Monitor sentiment weekly** — Look for patterns in complaints or confusion before they become churn signals\n\n---\n\n## Community Models & Scaling Phases\n\nBefore picking tactics, pick the **shape** of the community and match your effort to its stage. See **`references\u002Fcommunity-models.md`** for:\n\n- **The 5 community models** — Support-Driven (GreenPal), Product-Development (Ydata), Education\u002FEnablement (LiveAgent), Founder-Led (Bento, Postaga) — each with a \"best when…\" fit test tied to a primary goal.\n- **The Notion benchmark** — 300+ ambassadors, 1M+ template downloads, 25% of new users from community referrals. The north star for community-led growth at scale.\n- **The scaling-phase role shift** — Community Architect (0–100) → Manager (100–1,000) → Enabler (1,000+), and what to focus on in each.\n\nRoute here when the user asks *what kind* of community to build, which model fits their goal, or how their role should change as the community grows.\n\n---\n\n## Platform Selection Guide\n\n| Platform | Best For | Watch Out For |\n|----------|----------|---------------|\n| Discord | Developer, gaming, creator communities; real-time chat | High noise, hard to search, onboarding friction |\n| Slack | B2B \u002F professional communities; familiar to SaaS buyers | Free tier limits history; feels like work |\n| Circle | Creator or course-based communities; clean UX | Less organic discovery; requires driving traffic |\n| Reddit | High-volume public communities; SEO benefit | You don't own it; moderation is hard |\n| Facebook Groups | Consumer brands; older demographics | Declining organic reach; algorithm dependent |\n| Forum (Discourse) | Long-form technical communities; SEO-rich | Slower velocity; higher effort to post |\n\n---\n\n## Community Health Metrics\n\nTrack these signals weekly:\n\n- **DAU\u002FMAU ratio** — Stickiness. Above 20% is healthy for most communities.\n- **New member post rate** — % of new members who post within 7 days of joining\n- **Thread reply rate** — % of posts that receive at least one reply\n- **Churn \u002F lurker ratio** — Members who joined but haven't posted in 30+ days\n- **Content created by non-staff** — % of posts not written by the company team\n\n**Warning signs:**\n- Most posts are from the company team, not members\n- Questions go unanswered for >24 hours\n- The same 5 people account for 80%+ of engagement\n- New members stop posting after their intro message\n\n---\n\n## Output Formats\n\nDepending on what the user needs, produce one of:\n\n- **Community Strategy Doc** — Platform choice, identity definition, core loop, 90-day launch plan\n- **Channel Architecture** — Recommended channels\u002Fcategories with purpose and posting guidelines for each\n- **New Member Journey** — Welcome sequence: pinned post, DM template, first-week prompts\n- **Community Ritual Calendar** — Weekly\u002Fmonthly recurring events and threads\n- **Ambassador Program Brief** — Criteria, benefits, outreach template, tracking plan\n- **Health Audit Report** — Current metrics, diagnosis, top 3 priorities to fix\n\nAlways be specific. Generic advice (\"be consistent,\" \"provide value\") is not useful. Give the user something they can act on today.\n\n---\n\n## Task-Specific Questions\n\n1. What platform are you building on (or considering)?\n2. What stage is the community at? (Pre-launch, early, growing, established)\n3. What's the primary business goal? (Retention, activation, word-of-mouth, support deflection)\n4. Who is the ideal community member and what motivates them?\n5. Do you have existing users or customers to seed from?\n6. How much time can you dedicate to community management weekly?\n\n---\n\n## Related Skills\n\n- **referrals**: For structured referral and ambassador incentive programs\n- **churn-prevention**: For retention strategies that complement community engagement\n- **social**: For content creation across social platforms\n- **customer-research**: For understanding your community members' needs and language\n",{"name":5,"tags":54,"tools":55,"source":56,"license":14,"description":7,"source_path":57,"source_commit":58},[30,43,35,48],[],"https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills","skills\u002Fcommunity-marketing","5b2c0007766c6a1cf1d53fd8fc73e979e0821022","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fcommunity-marketing",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 community-marketing",{"tool":74,"command":75},"bunx","bunx skills add monoes\u002Fmonomind --skill community-marketing",{"tool":77,"command":78},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill community-marketing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fcommunity-marketing\u002FSKILL.md",true,[82,87],{"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\u002Fcommunity-models.md","REFERENCE","参考文档",4049,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fcommunity-marketing\u002Freferences\u002Fcommunity-models.md",[94,123,153,179,202,229],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":98,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":122},"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",[],[102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121],"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":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":127,"sourceHtmlUrl":128,"categories":129,"keywords":136,"publishedAt":122},"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",[130,133],{"categoryNo":131,"categoryName":132,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":134,"categoryName":135,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者",[137,138,139,106,140,141,47,142,111,143,144,145,44,146,147,148,149,150,151,152],"writing","writing plans","plans","superpowers","implementation plan","you","code","tasks","plan","write","commands","paths","suggest","coding","context","ZeRO",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":98,"licenseFileUrl":157,"sourceHtmlUrl":158,"categories":159,"keywords":163,"publishedAt":122},"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",[160],{"categoryNo":161,"categoryName":162,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000031","产品经理",[146,164,165,166,167,109,168,47,169,170,171,44,172,173,174,175,176,177,37,178],"write spec","spec","user request","problem","acceptance","ask","vague","work","request","scoping","idea","metrics","feature","problem statement","document",{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":98,"licenseFileUrl":183,"sourceHtmlUrl":184,"categories":185,"keywords":189,"publishedAt":122},"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",[186],{"categoryNo":187,"categoryName":188,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000033","数据分析师",[111,146,190,191,192,193,109,37,47,194,195,196,197,171,33,198,32,199,200,201],"write query","postgres","for","snowflake","best practices","natural-language","with","multi","sql","syntax","plugins","data",{"skillNo":203,"name":204,"nameZh":6,"description":205,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":98,"licenseFileUrl":6,"sourceHtmlUrl":206,"categories":207,"keywords":214,"publishedAt":122},"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",[208,211],{"categoryNo":209,"categoryName":210,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":212,"categoryName":213,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[215,216,217,218,192,219,220,221,222,110,223,224,225,111,114,33,226,227,228,32],"Workflow Automation","automation","workflow","parallel","actions","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":230,"name":231,"nameZh":6,"description":232,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":98,"licenseFileUrl":6,"sourceHtmlUrl":233,"categories":234,"keywords":236,"publishedAt":122},"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",[235],{"categoryNo":212,"categoryName":213,"taxonomyType":21,"taxonomyTypeDesc":22},[217,237,238,239,240,241,242,192,243,244,143,245,246,247,114,33,248,249,32,250],"workflow architect","architect","trees","user journeys","branch","planning","map","workflows","architecture","state","leadership","recovery","operations","systems"]