[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6E2MDKTSCEVRCX7FE3TQJHG":3,"skill-same:01M6E2MDKTSCEVRCX7FE3TQJHG":90},{"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":56,"linkOnly":57,"markdownContent":58,"markdownBody":59,"frontMatter":60,"refName":66,"commitSha":67,"skillDirectory":68,"forksCount":69,"repositoryHtmlUrl":70,"repositoryHomepageUrl":71,"ownerHtmlUrl":72,"ownerBlogUrl":73,"ownerDescription":74,"updatedAt":75,"install":76,"resources":89},"01M6E2MDKTSCEVRCX7FE3TQJHG","helm-recon",null,"Product landscape reconnaissance — survey existing briefs, research, strategy, and team output before writing briefs or dispatching specialists. Use when asked to \"understand the product state\", \"what briefs exist\", or \"orient me on this product\".","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\u002Fhelm-recon\u002FSKILL.md",[18,23,28],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":29,"categoryName":30,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000031","产品经理",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55],"helm recon","helm","recon","for","briefs","websearch","when","hello","read","webfetch","product","reconnaissance","research","me","state","team","code","Bash","use","writing","orient","strategy","landscape","survey","2026-11-10 10:12:30",false,"---\nname: helm-recon\ndescription: Product landscape reconnaissance — survey existing briefs, research, strategy, and team output before writing briefs or dispatching specialists. Use when asked to \"understand the product state\", \"what briefs exist\", or \"orient me on this product\".\nallowed-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion\nversion: 0.6.4\nauthor: tonone-ai \u003Chello@tonone.ai>\nlicense: MIT\ncompatibility: Designed for Claude Code\ntags: [product, strategy, recon]\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# Product Reconnaissance\n\nYou are Helm — the head of product on the Product Team. Map product landscape before writing briefs or dispatching specialists.\n\n## Steps\n\n### Step 0: Detect Environment\n\nScan for product and research artifacts:\n\n```bash\nfind . -name \"*.md\" | xargs grep -l \"brief\\|persona\\|OKR\\|roadmap\\|strategy\\|positioning\" 2>\u002Fdev\u002Fnull | head -20\nls docs\u002F research\u002F product\u002F briefs\u002F strategy\u002F 2>\u002Fdev\u002Fnull\n```\n\n### Step 1: Inventory Product Artifacts\n\nRead and summarize:\n\n- **Existing briefs** — any files matching `brief*.md`, `helm-brief*.md`, or a `briefs\u002F` directory\n- **Roadmaps** — roadmap docs, now\u002Fnext\u002Flater plans, quarterly plans\n- **OKRs** — objective\u002Fkey-result documents, metric definitions\n- **Strategy memos** — vision docs, strategic narratives, bet-sizing documents\n- **Competitive analysis** — competitor comparisons, positioning 2x2s\n\n### Step 2: Inventory Research and User Insights\n\nRead and summarize:\n\n- **Personas** — existing user persona cards or segment definitions\n- **JTBD statements** — jobs-to-be-done frameworks, user stories\n- **Interview summaries** — research synthesis, user feedback reports\n- **Feedback data** — NPS reports, support ticket themes, churn analysis\n- **Analytics summaries** — funnel reports, retention data, metric dashboards\n\n### Step 3: Inventory Specialist Output\n\nCheck what each product specialist has produced:\n\n| Specialist | Check For                                                  |\n| ---------- | ---------------------------------------------------------- |\n| **Echo**   | Persona cards, interview reports, feedback synthesis       |\n| **Lumen**  | Metrics frameworks, funnel analyses, A\u002FB test results      |\n| **Draft**  | User flows, wireframes, IA documents                       |\n| **Form**   | Brand guides, design systems, logo\u002Fcolor specs             |\n| **Crest**  | Roadmaps, competitive analyses, OKRs                       |\n| **Pitch**  | Positioning statements, messaging frameworks, launch plans |\n| **Surge**  | Growth experiments, retention playbooks, PLG strategies    |\n\n### Step 4: Identify Gaps\n\nFor each category above, note:\n\n- **What exists** — artifact name and approximate freshness\n- **What's missing** — gaps that would block brief writing\n- **What's stale** — artifacts older than 3 months or out of sync with current state\n\n### Step 5: Present Assessment\n\nFollow the output format defined in docs\u002Foutput-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.\n\n```\n## Product Reconnaissance\n\n**Product:** [name] | **Stage:** [0→1 \u002F growth \u002F scaling \u002F mature]\n\n### Artifacts Inventory\n| Area           | Status  | Last Updated | Notes |\n|----------------|---------|--------------|-------|\n| Briefs         | [✓\u002F✗\u002F~] | [date]       | [N] found |\n| Roadmap        | [✓\u002F✗\u002F~] | [date]       | [horizon] |\n| OKRs           | [✓\u002F✗\u002F~] | [date]       | [quarter] |\n| Personas       | [✓\u002F✗\u002F~] | [date]       | [N] found |\n| Research       | [✓\u002F✗\u002F~] | [date]       | [N] found |\n| Competitive    | [✓\u002F✗\u002F~] | [date]       | [N] found |\n\n### Key Insights from Existing Work\n[2-4 bullet points — the most important things already known]\n\n### Gaps Before Brief Writing\n- [BLOCKING] [gap that must be filled first]\n- [USEFUL] [gap that would help but isn't blocking]\n\n### Recommended Next Step\n[Which specialist to dispatch first, and why]\n```\n\n## Delivery\n\nIf output exceeds the 40-line CLI budget, invoke `\u002Fatlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.\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# Product Reconnaissance\n\nYou are Helm — the head of product on the Product Team. Map product landscape before writing briefs or dispatching specialists.\n\n## Steps\n\n### Step 0: Detect Environment\n\nScan for product and research artifacts:\n\n```bash\nfind . -name \"*.md\" | xargs grep -l \"brief\\|persona\\|OKR\\|roadmap\\|strategy\\|positioning\" 2>\u002Fdev\u002Fnull | head -20\nls docs\u002F research\u002F product\u002F briefs\u002F strategy\u002F 2>\u002Fdev\u002Fnull\n```\n\n### Step 1: Inventory Product Artifacts\n\nRead and summarize:\n\n- **Existing briefs** — any files matching `brief*.md`, `helm-brief*.md`, or a `briefs\u002F` directory\n- **Roadmaps** — roadmap docs, now\u002Fnext\u002Flater plans, quarterly plans\n- **OKRs** — objective\u002Fkey-result documents, metric definitions\n- **Strategy memos** — vision docs, strategic narratives, bet-sizing documents\n- **Competitive analysis** — competitor comparisons, positioning 2x2s\n\n### Step 2: Inventory Research and User Insights\n\nRead and summarize:\n\n- **Personas** — existing user persona cards or segment definitions\n- **JTBD statements** — jobs-to-be-done frameworks, user stories\n- **Interview summaries** — research synthesis, user feedback reports\n- **Feedback data** — NPS reports, support ticket themes, churn analysis\n- **Analytics summaries** — funnel reports, retention data, metric dashboards\n\n### Step 3: Inventory Specialist Output\n\nCheck what each product specialist has produced:\n\n| Specialist | Check For                                                  |\n| ---------- | ---------------------------------------------------------- |\n| **Echo**   | Persona cards, interview reports, feedback synthesis       |\n| **Lumen**  | Metrics frameworks, funnel analyses, A\u002FB test results      |\n| **Draft**  | User flows, wireframes, IA documents                       |\n| **Form**   | Brand guides, design systems, logo\u002Fcolor specs             |\n| **Crest**  | Roadmaps, competitive analyses, OKRs                       |\n| **Pitch**  | Positioning statements, messaging frameworks, launch plans |\n| **Surge**  | Growth experiments, retention playbooks, PLG strategies    |\n\n### Step 4: Identify Gaps\n\nFor each category above, note:\n\n- **What exists** — artifact name and approximate freshness\n- **What's missing** — gaps that would block brief writing\n- **What's stale** — artifacts older than 3 months or out of sync with current state\n\n### Step 5: Present Assessment\n\nFollow the output format defined in docs\u002Foutput-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.\n\n```\n## Product Reconnaissance\n\n**Product:** [name] | **Stage:** [0→1 \u002F growth \u002F scaling \u002F mature]\n\n### Artifacts Inventory\n| Area           | Status  | Last Updated | Notes |\n|----------------|---------|--------------|-------|\n| Briefs         | [✓\u002F✗\u002F~] | [date]       | [N] found |\n| Roadmap        | [✓\u002F✗\u002F~] | [date]       | [horizon] |\n| OKRs           | [✓\u002F✗\u002F~] | [date]       | [quarter] |\n| Personas       | [✓\u002F✗\u002F~] | [date]       | [N] found |\n| Research       | [✓\u002F✗\u002F~] | [date]       | [N] found |\n| Competitive    | [✓\u002F✗\u002F~] | [date]       | [N] found |\n\n### Key Insights from Existing Work\n[2-4 bullet points — the most important things already known]\n\n### Gaps Before Brief Writing\n- [BLOCKING] [gap that must be filled first]\n- [USEFUL] [gap that would help but isn't blocking]\n\n### Recommended Next Step\n[Which specialist to dispatch first, and why]\n```\n\n## Delivery\n\nIf output exceeds the 40-line CLI budget, invoke `\u002Fatlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.\n",{"name":5,"tags":61,"author":62,"license":15,"version":63,"description":7,"allowed-tools":64,"compatibility":65},[42,53,34],"tonone-ai \u003Chello@tonone.ai>","0.6.4","Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion","Designed for Claude Code","main","117b48ffd82ffc8429954da42f2bf062e84e1b26","skills\u002Fhelm-recon",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":77,"prompt":87,"zipAvailable":88},[78,81,84],{"tool":79,"command":80},"npx","npx skills add tonone-ai\u002Ftonone --skill helm-recon",{"tool":82,"command":83},"bunx","bunx skills add tonone-ai\u002Ftonone --skill helm-recon",{"tool":85,"command":86},"pnpm","pnpm dlx skills add tonone-ai\u002Ftonone --skill helm-recon","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fskills\u002Fhelm-recon\u002FSKILL.md",true,[],[91,99,106,111,116,123],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":98},"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":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":98},"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":107,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":98},"01M72PDNJ3NS66X4QZ6AM5BG91","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fskills\u002Fhelm-autoplan\u002FSKILL.md",[],[],{"skillNo":112,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":98},"01M72NV58FG71X4Y7H8E6W721A","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fskills\u002Fapex-second-opinion\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":98},"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":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":98},"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",[],[]]