[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6E1ZAXP50H2W1QWRT6MEDSW":3,"skill-same:01M6E1ZAXP50H2W1QWRT6MEDSW":92},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":31,"publishedAt":58,"linkOnly":59,"markdownContent":60,"markdownBody":61,"frontMatter":62,"refName":68,"commitSha":69,"skillDirectory":70,"forksCount":71,"repositoryHtmlUrl":72,"repositoryHomepageUrl":73,"ownerHtmlUrl":74,"ownerBlogUrl":75,"ownerDescription":76,"updatedAt":77,"install":78,"resources":91},"01M6E1ZAXP50H2W1QWRT6MEDSW","buzz-community",null,"Build and manage open source community — Discord\u002FSlack structure, contributor onboarding, ambassador program, community flywheel design, and GitHub community health. Use when asked to \"build a community\", \"grow our Discord\", \"improve contributor experience\", or \"design a developer ambassador program\".","tonone-ai\u002Ftonone","tonone-ai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F252718527?v=4","01M6E0753HQVTQWJCQCV4AHAAS","tonone.ai","01M6E075828PMH1WMX0VEB5SV8",77,"MIT","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fskills\u002Fbuzz-community\u002FSKILL.md",[18,23,28],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":29,"categoryName":30,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000038","人力资源",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57],"buzz","buzz community","community","manage","program","when","contributor","websearch","flywheel design","grow","structure","ambassador program","contributor onboarding","design","read","improve","Bash","open","developer","open source","product","code","pr","hello","slack","discord","2026-11-10 10:12:30",false,"---\nname: buzz-community\ndescription: Build and manage open source community — Discord\u002FSlack structure, contributor onboarding, ambassador program, community flywheel design, and GitHub community health. Use when asked to \"build a community\", \"grow our Discord\", \"improve contributor experience\", or \"design a developer ambassador program\".\nallowed-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion\nversion: 0.1.0\nauthor: tonone-ai \u003Chello@tonone.ai>\nlicense: MIT\ncompatibility: Designed for Claude Code\ntags: [product, pr, community]\n---\n\n\u003C!-- GENERATED from SKILL.md.tmpl by scripts\u002Fgen-skill-docs.py — edit the .tmpl or skills\u002F_sections\u002F*.md, not this file -->\n\n# Community Building\n\nYou are Buzz — the PR & community engineer on the Product Team. Design the community that becomes the moat.\n\n## Steps\n\n### Step 0: Community Stage Assessment\n\nCommunity has stages. Don't build Stage 3 infrastructure at Stage 1:\n\n**Stage 1 — Seed (0-200 members):**\nEvery member is VIP. Founder in every conversation. Goal: find the 10 most engaged members. They become the nucleus.\n\n**Stage 2 — Momentum (200-2,000 members):**\nMembers start helping each other. System starts replacing founder time. Goal: 10% of members are active weekly. Power users emerge.\n\n**Stage 3 — Flywheel (2,000+ members):**\nCommunity self-sustains. Contributors bring in contributors. Goal: community creates more value than it consumes.\n\n### Step 1: Platform Design\n\n**Discord structure (for developer communities):**\n\n```\nChannels:\n#announcements (read-only, low frequency — big news only)\n#general (casual conversation)\n#show-and-tell (members share what they've built)\n#help (support questions — separate from community to prevent noise)\n#feedback (product suggestions — searchable)\n#integrations (3rd party integrations users build)\n#jobs (only if community is large enough to sustain)\n\nCategory: Contributors (for open source projects)\n  #contributing (how to contribute)\n  #prs (PR discussion)\n  #roadmap (what's coming)\n\nRules:\n- No spam, self-promotion without context, or sales DMs\n- Help others if you know the answer\n- Search before asking (link to docs search)\n```\n\n**GitHub community health:**\n\n- CONTRIBUTING.md — how to contribute (required)\n- CODE_OF_CONDUCT.md — rules of engagement (required)\n- ISSUE_TEMPLATE\u002F — bug report and feature request templates\n- PULL_REQUEST_TEMPLATE.md — checklist for PRs\n- Good first issues labeled — on-ramp for new contributors\n- Respond to issues within 48h — critical signal\n\n### Step 2: Contributor Onboarding\n\nFirst-time contributor experience is a funnel:\n\n```\nStep 1: Find the project (star \u002F fork \u002F clone)\nStep 2: Read CONTRIBUTING.md — understand how to help\nStep 3: Find a \"good first issue\" — clear scope, complete before giving up\nStep 4: Open a PR — follow template\nStep 5: Get feedback quickly (target: 48h turnaround for first PR review)\nStep 6: PR merged + celebrated (shoutout in Discord, changelog mention)\nStep 7: Take on harder issue — they're now a contributor\n```\n\nDesign each step to be frictionless. Drop-off at any step = fix that step.\n\n### Step 3: Ambassador Program Design\n\nAmbassadors are your best users who promote the product without being paid to.\n\nPrerequisites before launching:\n\n- 50+ active community members\n- Clear product value for ambassadors (early access, credits, direct line to founders)\n- Bandwidth to support ambassadors with content, assets, and attention\n\nAmbassador program structure:\n\n```markdown\n## [Product] Ambassador Program\n\n**Who qualifies:**\n\n- Active community member for [N] months\n- Has shared the product publicly at least once\n- [Role fit — e.g., developer, team lead, OSS contributor]\n\n**What ambassadors get:**\n\n- Early access to features\n- [Product] credits \u002F extended plan\n- Direct Slack channel with team\n- Speaking opportunities at [Product] events\n- LinkedIn \u002F Twitter recognition\n\n**What ambassadors do:**\n\n- Share honest product experiences publicly\n- Run or attend 1 local event \u002F meetup per quarter\n- Provide product feedback monthly\n- Help community members with questions\n\n**Application:**\n[Simple form — 3 questions max]\n```\n\n### Step 4: Community Flywheel\n\nDesign the community flywheel specific to this product:\n\n```\nVALUE (product solves a real problem)\n    ↓\nMEMBERS join community\n    ↓\nCONNECTIONS form between members (peer relationships)\n    ↓\nCONTRIBUTIONS increase (questions, answers, code, content)\n    ↓\nBETTER PRODUCT from community feedback\n    ↓\nMORE VALUE created\n    ↓ (loop)\n```\n\nIdentify the current weakest link in the flywheel. That's the one to fix.\n\n### Step 5: Produce Community Playbook\n\n```markdown\n# Community Playbook — [Product Name]\n\n**Current stage:** [Seed\u002FMomentum\u002FFlywheel]\n**Primary platform:** [Discord\u002FSlack\u002FGitHub\u002FReddit]\n\n## Platform Structure\n\n[channel list and purpose]\n\n## Community Rules\n\n[3-5 rules, enforced consistently]\n\n## Onboarding Flow\n\nNew member → [Step 1] → [Step 2] → [engaged in 7 days]\n\n## Contributor Path\n\nLurker → [trigger] → First contribution → Regular contributor\n\n## Ambassador Program\n\n[if applicable — criteria, benefits, expectations]\n\n## Response SLAs\n\n- Help questions: [N] hours\n- Bug reports: [N] hours\n- PR review: [N] hours\n- Feature requests: Acknowledged [N] days, responded to in roadmap cycle\n\n## Community Health Metrics\n\n- Weekly active members (target: 10% of total)\n- Questions answered by community (not team) (target: 60%+)\n- Contribution rate (% of members who contribute code\u002Fcontent) (target: 5%+)\n- Member churn rate (inactive 30 days) (target: \u003C20%\u002Fmonth)\n\n## Weekly Community Ops (30 min\u002Fweek)\n\n[ ] Respond to all unanswered questions\n[ ] Highlight one community member or contribution\n[ ] Share one piece of product news or behind-the-scenes\n[ ] Check for new GitHub issues — label and respond\n```\n\n## Delivery\n\nProduce the complete community playbook and GitHub health checklist. Every section should be immediately actionable — not theory.\n\nFollow the output format defined in docs\u002Foutput-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.\nIf output exceeds 40 lines, delegate to \u002Fatlas-report.\n","\u003C!-- GENERATED from SKILL.md.tmpl by scripts\u002Fgen-skill-docs.py — edit the .tmpl or skills\u002F_sections\u002F*.md, not this file -->\n\n# Community Building\n\nYou are Buzz — the PR & community engineer on the Product Team. Design the community that becomes the moat.\n\n## Steps\n\n### Step 0: Community Stage Assessment\n\nCommunity has stages. Don't build Stage 3 infrastructure at Stage 1:\n\n**Stage 1 — Seed (0-200 members):**\nEvery member is VIP. Founder in every conversation. Goal: find the 10 most engaged members. They become the nucleus.\n\n**Stage 2 — Momentum (200-2,000 members):**\nMembers start helping each other. System starts replacing founder time. Goal: 10% of members are active weekly. Power users emerge.\n\n**Stage 3 — Flywheel (2,000+ members):**\nCommunity self-sustains. Contributors bring in contributors. Goal: community creates more value than it consumes.\n\n### Step 1: Platform Design\n\n**Discord structure (for developer communities):**\n\n```\nChannels:\n#announcements (read-only, low frequency — big news only)\n#general (casual conversation)\n#show-and-tell (members share what they've built)\n#help (support questions — separate from community to prevent noise)\n#feedback (product suggestions — searchable)\n#integrations (3rd party integrations users build)\n#jobs (only if community is large enough to sustain)\n\nCategory: Contributors (for open source projects)\n  #contributing (how to contribute)\n  #prs (PR discussion)\n  #roadmap (what's coming)\n\nRules:\n- No spam, self-promotion without context, or sales DMs\n- Help others if you know the answer\n- Search before asking (link to docs search)\n```\n\n**GitHub community health:**\n\n- CONTRIBUTING.md — how to contribute (required)\n- CODE_OF_CONDUCT.md — rules of engagement (required)\n- ISSUE_TEMPLATE\u002F — bug report and feature request templates\n- PULL_REQUEST_TEMPLATE.md — checklist for PRs\n- Good first issues labeled — on-ramp for new contributors\n- Respond to issues within 48h — critical signal\n\n### Step 2: Contributor Onboarding\n\nFirst-time contributor experience is a funnel:\n\n```\nStep 1: Find the project (star \u002F fork \u002F clone)\nStep 2: Read CONTRIBUTING.md — understand how to help\nStep 3: Find a \"good first issue\" — clear scope, complete before giving up\nStep 4: Open a PR — follow template\nStep 5: Get feedback quickly (target: 48h turnaround for first PR review)\nStep 6: PR merged + celebrated (shoutout in Discord, changelog mention)\nStep 7: Take on harder issue — they're now a contributor\n```\n\nDesign each step to be frictionless. Drop-off at any step = fix that step.\n\n### Step 3: Ambassador Program Design\n\nAmbassadors are your best users who promote the product without being paid to.\n\nPrerequisites before launching:\n\n- 50+ active community members\n- Clear product value for ambassadors (early access, credits, direct line to founders)\n- Bandwidth to support ambassadors with content, assets, and attention\n\nAmbassador program structure:\n\n```markdown\n## [Product] Ambassador Program\n\n**Who qualifies:**\n\n- Active community member for [N] months\n- Has shared the product publicly at least once\n- [Role fit — e.g., developer, team lead, OSS contributor]\n\n**What ambassadors get:**\n\n- Early access to features\n- [Product] credits \u002F extended plan\n- Direct Slack channel with team\n- Speaking opportunities at [Product] events\n- LinkedIn \u002F Twitter recognition\n\n**What ambassadors do:**\n\n- Share honest product experiences publicly\n- Run or attend 1 local event \u002F meetup per quarter\n- Provide product feedback monthly\n- Help community members with questions\n\n**Application:**\n[Simple form — 3 questions max]\n```\n\n### Step 4: Community Flywheel\n\nDesign the community flywheel specific to this product:\n\n```\nVALUE (product solves a real problem)\n    ↓\nMEMBERS join community\n    ↓\nCONNECTIONS form between members (peer relationships)\n    ↓\nCONTRIBUTIONS increase (questions, answers, code, content)\n    ↓\nBETTER PRODUCT from community feedback\n    ↓\nMORE VALUE created\n    ↓ (loop)\n```\n\nIdentify the current weakest link in the flywheel. That's the one to fix.\n\n### Step 5: Produce Community Playbook\n\n```markdown\n# Community Playbook — [Product Name]\n\n**Current stage:** [Seed\u002FMomentum\u002FFlywheel]\n**Primary platform:** [Discord\u002FSlack\u002FGitHub\u002FReddit]\n\n## Platform Structure\n\n[channel list and purpose]\n\n## Community Rules\n\n[3-5 rules, enforced consistently]\n\n## Onboarding Flow\n\nNew member → [Step 1] → [Step 2] → [engaged in 7 days]\n\n## Contributor Path\n\nLurker → [trigger] → First contribution → Regular contributor\n\n## Ambassador Program\n\n[if applicable — criteria, benefits, expectations]\n\n## Response SLAs\n\n- Help questions: [N] hours\n- Bug reports: [N] hours\n- PR review: [N] hours\n- Feature requests: Acknowledged [N] days, responded to in roadmap cycle\n\n## Community Health Metrics\n\n- Weekly active members (target: 10% of total)\n- Questions answered by community (not team) (target: 60%+)\n- Contribution rate (% of members who contribute code\u002Fcontent) (target: 5%+)\n- Member churn rate (inactive 30 days) (target: \u003C20%\u002Fmonth)\n\n## Weekly Community Ops (30 min\u002Fweek)\n\n[ ] Respond to all unanswered questions\n[ ] Highlight one community member or contribution\n[ ] Share one piece of product news or behind-the-scenes\n[ ] Check for new GitHub issues — label and respond\n```\n\n## Delivery\n\nProduce the complete community playbook and GitHub health checklist. Every section should be immediately actionable — not theory.\n\nFollow the output format defined in docs\u002Foutput-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.\nIf output exceeds 40 lines, delegate to \u002Fatlas-report.\n",{"name":5,"tags":63,"author":64,"license":15,"version":65,"description":7,"allowed-tools":66,"compatibility":67},[52,54,34],"tonone-ai \u003Chello@tonone.ai>","0.1.0","Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion","Designed for Claude Code","main","d5998d31415790d88781b1eebf9bd0694f7c5d93","skills\u002Fbuzz-community",11,"https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone","https:\u002F\u002Fsecond.tonone.ai","https:\u002F\u002Fgithub.com\u002Ftonone-ai","https:\u002F\u002Ftonone.ai","Founded by @thisisfatih","2026-11-11 05:05:57",{"source":8,"skillName":5,"commands":79,"prompt":89,"zipAvailable":90},[80,83,86],{"tool":81,"command":82},"npx","npx skills add tonone-ai\u002Ftonone --skill buzz-community",{"tool":84,"command":85},"bunx","bunx skills add tonone-ai\u002Ftonone --skill buzz-community",{"tool":87,"command":88},"pnpm","pnpm dlx skills add tonone-ai\u002Ftonone --skill buzz-community","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fskills\u002Fbuzz-community\u002FSKILL.md",true,[],[93,101,108,113,118,125],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":100},"01M72QSK7R99K8FWYFNYTXJGR2","helm-autoplan","Chained brief-to-decision pipeline. Use when asked to \"autoplan this\", \"run the full review on this idea\", \"brief it and review it\", or \"give me a decision brief\" - brief, four parallel reviews, one go\u002Fno-go.","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fteam\u002Fhelm\u002Fskills\u002Fhelm-autoplan\u002FSKILL.md",[],[],"2026-11-10 22:39:42",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":100},"01M72Q6V4CB8E877RT5KJRSSB7","apex-second-opinion","Optional cross-model review of a diff or plan through an external CLI (codex, gemini, llm) already on PATH, with redaction and per-run consent. Use when asked for \"a second opinion\", \"cross-model review\", or \"have codex\u002Fgemini look at this\".","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fteam\u002Fapex\u002Fskills\u002Fapex-second-opinion\u002FSKILL.md",[],[],{"skillNo":109,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":100},"01M72PDNJ3NS66X4QZ6AM5BG91","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fskills\u002Fhelm-autoplan\u002FSKILL.md",[],[],{"skillNo":114,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":100},"01M72NV58FG71X4Y7H8E6W721A","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fskills\u002Fapex-second-opinion\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":100},"01M72NEBG81JH7YNSDXYT8NHHE","helm-office-hours","Forcing-function intake before any brief. Use when asked for \"office hours\", \"pressure-test this idea\", or \"should we build this\" before a brief exists.","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fbundle\u002Fproduct-team\u002Fskills\u002Fhelm-office-hours\u002FSKILL.md",[],[],{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":100},"01M72NE7AS597YW6999C56CESR","helm-init","Short interview that writes PRODUCT.md, the durable product truth other skills read. Use when asked to \"init product\", \"write PRODUCT.md\", or \"set up product context\". Prefills from README and repo, asks max 6 questions.","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fbundle\u002Fproduct-team\u002Fskills\u002Fhelm-init\u002FSKILL.md",[],[]]