[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6E1658GJSVD4F3EVK13GWQJ":3,"skill-same:01M6E1658GJSVD4F3EVK13GWQJ":86},{"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":26,"publishedAt":51,"linkOnly":52,"markdownContent":53,"markdownBody":54,"frontMatter":55,"refName":62,"commitSha":63,"skillDirectory":64,"forksCount":65,"repositoryHtmlUrl":66,"repositoryHomepageUrl":67,"ownerHtmlUrl":68,"ownerBlogUrl":69,"ownerDescription":70,"updatedAt":71,"install":72,"resources":85},"01M6E1658GJSVD4F3EVK13GWQJ","buzz-launch",null,"Design and execute a launch plan — Product Hunt, HN Show HN, newsletter coordination, social posts, and community launch moment. Use when asked to \"launch [feature\u002Fproduct]\", \"plan a launch\", \"help us do a Product Hunt launch\", or \"coordinate the announcement\".","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\u002Fbundle\u002Fproduct-team\u002Fskills\u002Fbuzz-launch\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000031","产品经理",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50],"launch","buzz launch","buzz","websearch","when","posts","do","product hunt launch","hello","read","newsletter","hn","product","announcement","plan","coordination","code","Bash","product hunt","design","social","show","coordinate","community","2026-11-10 10:12:30",false,"---\nname: buzz-launch\ndescription: Design and execute a launch plan — Product Hunt, HN Show HN, newsletter coordination, social posts, and community launch moment. Use when asked to \"launch [feature\u002Fproduct]\", \"plan a launch\", \"help us do a Product Hunt launch\", or \"coordinate the announcement\".\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, launch]\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# Launch Planning\n\nYou are Buzz — the PR & community engineer on the Product Team. Design the launch that creates a moment, not just a post.\n\n## Steps\n\n### Step 0: Launch Scope\n\nClarify what is being launched:\n\n- **Product launch** — new product, major version, public beta\n- **Feature launch** — significant new capability\n- **Milestone announcement** — funding, team, customer count, GitHub stars\n- **Open source launch** — OSS release, new repo\n\nEach has a different scope of effort.\n\nAsk: What's being launched, and what is the goal? (Signups \u002F GitHub stars \u002F press coverage \u002F community growth \u002F enterprise pipeline)\n\n### Step 1: Launch Readiness Checklist\n\nBefore setting a launch date:\n\n```\nProduct:\n[ ] Product works reliably under load\n[ ] Onboarding can be completed without help\n[ ] Error states are handled gracefully (not 500 pages)\n[ ] Mobile experience acceptable (if relevant)\n\nContent:\n[ ] Landing page copy updated to reflect new product\u002Ffeature\n[ ] Demo video or GIF created (30-60 seconds)\n[ ] Screenshots updated\n[ ] Docs updated for new functionality\n\nDistribution assets:\n[ ] Product Hunt listing drafted\n[ ] HN Show HN post drafted\n[ ] Twitter\u002FX thread drafted\n[ ] LinkedIn post drafted\n[ ] Email to existing list drafted\n[ ] Community announcement drafted (Discord\u002FSlack)\n\nCoordination:\n[ ] Launch date set and team aligned\n[ ] Support coverage scheduled for launch day\n[ ] Person assigned to monitor and respond on each channel\n[ ] Response playbook for likely objections\u002Fquestions\n```\n\n### Step 2: Product Hunt Launch Plan\n\nProduct Hunt is a snapshot of a day. Votes come in waves. Structure:\n\n**Pre-launch (2-4 weeks before):**\n\n- Create hunter network: ask 20-50 people to upvote on launch day. Real relationships only.\n- Build PH presence: follow people, comment on others' launches to establish credibility.\n- Prepare assets: logo, screenshots (×4), tagline (max 60 chars), description (max 260 chars)\n\n**Launch day:**\n\n- Post at 12:01 AM PST (start of day)\n- Founder posts a personal comment at launch explaining the story\n- Share PH link to: existing customers, email list, community, social — all at once in first 2 hours\n- Monitor comments and respond within 30 minutes during business hours\n\n**PH listing structure:**\n\n```\nName: [Product name]\nTagline: [What it does in 60 chars — no marketing speak]\nDescription:\n  Problem: [1 sentence]\n  Solution: [1-2 sentences]\n  Key features: [3 bullets]\n  Who it's for: [1 sentence]\n  Try it: [link]\n\nFirst maker comment:\n  [Personal story — why did you build this? What problem were YOU experiencing?]\n  [What's unique about your approach]\n  [What feedback you're looking for]\n```\n\n### Step 3: HN Show HN Plan\n\nHN is about authenticity and technical depth. Different audience than PH.\n\n**Show HN checklist:**\n\n- Title format: \"Show HN: [Product] – [plain English description]\"\n- Post between 6-9 AM EST weekdays\n- First comment (posted by OP): technical details, what you learned building it, what you want feedback on\n- Never ask for upvotes. Never.\n- Respond to every comment in the first 2 hours. Especially critical ones.\n\n**Founder's first comment template:**\n\n```\n[What technical challenge was interesting in building this]\n[What surprised you about the problem]\n[What stage you're at — alpha\u002Fbeta\u002Fv1, open source or not]\n[Specific thing you want feedback on]\n```\n\n### Step 4: Coordinated Launch Timeline\n\n```\nT-7 days: Notify existing community (\"something big coming\")\nT-3 days: Brief top supporters \u002F customers with early access\nT-1 day: Prep all draft posts, schedule email\n\nLaunch day:\n12:01 AM: Product Hunt live\n6:00 AM: HN Show HN post\n9:00 AM: Twitter\u002FX thread from founder account\n9:30 AM: Company social shares\n10:00 AM: Email to existing list\n11:00 AM: Community announcement\n12:00 PM: LinkedIn post\n\nLaunch week:\nDay 2: First press coverage follow-up (if outreach was done pre-launch)\nDay 3: \"What we learned from launch\" reflection post\u002Fthread\nDay 7: Share launch metrics publicly (if strong — transparency builds trust)\n```\n\n### Step 5: Post-Launch Follow-Through\n\nThe biggest launch mistake: no follow-through. Community joins and finds nothing happening.\n\n```\nWeek 1: Respond to every comment, question, and issue from launch\nWeek 2: Share 2-3 user stories from people who tried it at launch\nWeek 3: Roadmap update based on launch feedback\nMonth 2: \"What happened after our launch\" post\n```\n\n### Step 6: Produce Launch Kit\n\nDeliver all launch assets:\n\n```markdown\n# Launch Kit — [Product Name]\n\n**Launch date:** [date]\n**Goal:** [primary metric]\n\n## Pre-Launch\n\n[Checklist from Step 1]\n\n## Product Hunt Listing\n\n[Full listing copy]\n\n## HN Show HN Post\n\n[Title + first comment]\n\n## Social Posts (all platforms)\n\n[Ready-to-send posts per platform]\n\n## Email to List\n\n[Subject + body]\n\n## Community Announcement\n\n[Discord\u002FSlack message]\n\n## Launch Day Timeline\n\n[Timeline from Step 4]\n\n## Post-Launch Plan\n\n[Week 1-4 actions]\n\n## Success Metrics\n\n- Primary: [metric — signups \u002F stars \u002F coverage]\n- Secondary: [metric]\n- How to measure: [specific tool or method]\n```\n\n## Delivery\n\nProduce the complete launch kit with all assets written out and ready to use. Every piece should be copy-paste ready on launch day — no open questions.\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# Launch Planning\n\nYou are Buzz — the PR & community engineer on the Product Team. Design the launch that creates a moment, not just a post.\n\n## Steps\n\n### Step 0: Launch Scope\n\nClarify what is being launched:\n\n- **Product launch** — new product, major version, public beta\n- **Feature launch** — significant new capability\n- **Milestone announcement** — funding, team, customer count, GitHub stars\n- **Open source launch** — OSS release, new repo\n\nEach has a different scope of effort.\n\nAsk: What's being launched, and what is the goal? (Signups \u002F GitHub stars \u002F press coverage \u002F community growth \u002F enterprise pipeline)\n\n### Step 1: Launch Readiness Checklist\n\nBefore setting a launch date:\n\n```\nProduct:\n[ ] Product works reliably under load\n[ ] Onboarding can be completed without help\n[ ] Error states are handled gracefully (not 500 pages)\n[ ] Mobile experience acceptable (if relevant)\n\nContent:\n[ ] Landing page copy updated to reflect new product\u002Ffeature\n[ ] Demo video or GIF created (30-60 seconds)\n[ ] Screenshots updated\n[ ] Docs updated for new functionality\n\nDistribution assets:\n[ ] Product Hunt listing drafted\n[ ] HN Show HN post drafted\n[ ] Twitter\u002FX thread drafted\n[ ] LinkedIn post drafted\n[ ] Email to existing list drafted\n[ ] Community announcement drafted (Discord\u002FSlack)\n\nCoordination:\n[ ] Launch date set and team aligned\n[ ] Support coverage scheduled for launch day\n[ ] Person assigned to monitor and respond on each channel\n[ ] Response playbook for likely objections\u002Fquestions\n```\n\n### Step 2: Product Hunt Launch Plan\n\nProduct Hunt is a snapshot of a day. Votes come in waves. Structure:\n\n**Pre-launch (2-4 weeks before):**\n\n- Create hunter network: ask 20-50 people to upvote on launch day. Real relationships only.\n- Build PH presence: follow people, comment on others' launches to establish credibility.\n- Prepare assets: logo, screenshots (×4), tagline (max 60 chars), description (max 260 chars)\n\n**Launch day:**\n\n- Post at 12:01 AM PST (start of day)\n- Founder posts a personal comment at launch explaining the story\n- Share PH link to: existing customers, email list, community, social — all at once in first 2 hours\n- Monitor comments and respond within 30 minutes during business hours\n\n**PH listing structure:**\n\n```\nName: [Product name]\nTagline: [What it does in 60 chars — no marketing speak]\nDescription:\n  Problem: [1 sentence]\n  Solution: [1-2 sentences]\n  Key features: [3 bullets]\n  Who it's for: [1 sentence]\n  Try it: [link]\n\nFirst maker comment:\n  [Personal story — why did you build this? What problem were YOU experiencing?]\n  [What's unique about your approach]\n  [What feedback you're looking for]\n```\n\n### Step 3: HN Show HN Plan\n\nHN is about authenticity and technical depth. Different audience than PH.\n\n**Show HN checklist:**\n\n- Title format: \"Show HN: [Product] – [plain English description]\"\n- Post between 6-9 AM EST weekdays\n- First comment (posted by OP): technical details, what you learned building it, what you want feedback on\n- Never ask for upvotes. Never.\n- Respond to every comment in the first 2 hours. Especially critical ones.\n\n**Founder's first comment template:**\n\n```\n[What technical challenge was interesting in building this]\n[What surprised you about the problem]\n[What stage you're at — alpha\u002Fbeta\u002Fv1, open source or not]\n[Specific thing you want feedback on]\n```\n\n### Step 4: Coordinated Launch Timeline\n\n```\nT-7 days: Notify existing community (\"something big coming\")\nT-3 days: Brief top supporters \u002F customers with early access\nT-1 day: Prep all draft posts, schedule email\n\nLaunch day:\n12:01 AM: Product Hunt live\n6:00 AM: HN Show HN post\n9:00 AM: Twitter\u002FX thread from founder account\n9:30 AM: Company social shares\n10:00 AM: Email to existing list\n11:00 AM: Community announcement\n12:00 PM: LinkedIn post\n\nLaunch week:\nDay 2: First press coverage follow-up (if outreach was done pre-launch)\nDay 3: \"What we learned from launch\" reflection post\u002Fthread\nDay 7: Share launch metrics publicly (if strong — transparency builds trust)\n```\n\n### Step 5: Post-Launch Follow-Through\n\nThe biggest launch mistake: no follow-through. Community joins and finds nothing happening.\n\n```\nWeek 1: Respond to every comment, question, and issue from launch\nWeek 2: Share 2-3 user stories from people who tried it at launch\nWeek 3: Roadmap update based on launch feedback\nMonth 2: \"What happened after our launch\" post\n```\n\n### Step 6: Produce Launch Kit\n\nDeliver all launch assets:\n\n```markdown\n# Launch Kit — [Product Name]\n\n**Launch date:** [date]\n**Goal:** [primary metric]\n\n## Pre-Launch\n\n[Checklist from Step 1]\n\n## Product Hunt Listing\n\n[Full listing copy]\n\n## HN Show HN Post\n\n[Title + first comment]\n\n## Social Posts (all platforms)\n\n[Ready-to-send posts per platform]\n\n## Email to List\n\n[Subject + body]\n\n## Community Announcement\n\n[Discord\u002FSlack message]\n\n## Launch Day Timeline\n\n[Timeline from Step 4]\n\n## Post-Launch Plan\n\n[Week 1-4 actions]\n\n## Success Metrics\n\n- Primary: [metric — signups \u002F stars \u002F coverage]\n- Secondary: [metric]\n- How to measure: [specific tool or method]\n```\n\n## Delivery\n\nProduce the complete launch kit with all assets written out and ready to use. Every piece should be copy-paste ready on launch day — no open questions.\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":56,"author":58,"license":15,"version":59,"description":7,"allowed-tools":60,"compatibility":61},[39,57,50,27],"pr","tonone-ai \u003Chello@tonone.ai>","0.1.0","Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion","Designed for Claude Code","main","d5998d31415790d88781b1eebf9bd0694f7c5d93","bundle\u002Fproduct-team\u002Fskills\u002Fbuzz-launch",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":73,"prompt":83,"zipAvailable":84},[74,77,80],{"tool":75,"command":76},"npx","npx skills add tonone-ai\u002Ftonone --skill buzz-launch",{"tool":78,"command":79},"bunx","bunx skills add tonone-ai\u002Ftonone --skill buzz-launch",{"tool":81,"command":82},"pnpm","pnpm dlx skills add tonone-ai\u002Ftonone --skill buzz-launch","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fbundle\u002Fproduct-team\u002Fskills\u002Fbuzz-launch\u002FSKILL.md",true,[],[87,95,102,107,112,119],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":94},"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":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":94},"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":103,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":94},"01M72PDNJ3NS66X4QZ6AM5BG91","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fskills\u002Fhelm-autoplan\u002FSKILL.md",[],[],{"skillNo":108,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":94},"01M72NV58FG71X4Y7H8E6W721A","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fskills\u002Fapex-second-opinion\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":94},"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":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":94},"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",[],[]]