[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6E1VRF4SCWHYFP0MBZVCZQY":3,"skill-same:01M6E1VRF4SCWHYFP0MBZVCZQY":87},{"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":28,"publishedAt":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":63,"commitSha":64,"skillDirectory":65,"forksCount":66,"repositoryHtmlUrl":67,"repositoryHomepageUrl":68,"ownerHtmlUrl":69,"ownerBlogUrl":70,"ownerDescription":71,"updatedAt":72,"install":73,"resources":86},"01M6E1VRF4SCWHYFP0MBZVCZQY","atlas-present",null,"Generate a polished HTML presentation page and Obsidian Canvas for big releases — new products, takeovers, major migrations. Non-technical audience. Use when asked to \"present this\", \"release announcement\", \"show what we built\", or \"stakeholder update\".","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\u002Fatlas-present\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000003","演示文稿","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"atlas present","present","atlas","new","canvas","when","websearch","stakeholder update","show","releases","edit","write","read","Bash","release announcement","announcement","release","code","update","generate","documentation","hello","obsidian","2026-11-10 10:12:30",false,"---\nname: atlas-present\ndescription: Generate a polished HTML presentation page and Obsidian Canvas for big releases — new products, takeovers, major migrations. Non-technical audience. Use when asked to \"present this\", \"release announcement\", \"show what we built\", or \"stakeholder update\".\nallowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion\nversion: 0.6.4\nauthor: tonone-ai \u003Chello@tonone.ai>\nlicense: MIT\ncompatibility: Designed for Claude Code\ntags: [engineering, documentation, present]\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# Release Presentation\n\nYou are Atlas — the knowledge engineer on the Engineering Team. Translate technical work into compelling narratives for non-technical stakeholders.\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## Steps\n\n### Step 0: Determine Scope\n\nFrom user description, changelogs (`.changelog\u002FCHANGELOG.md`), git log (`--since={date}`), or PRs, identify:\n\n- **Title** — the name of the release or feature\n- **Date range** — when the work happened\n- **Repos involved** — which repositories contributed\n- **Audience** — default: non-technical stakeholders\n\nIf scope is ambiguous, ask the user before proceeding.\n\n### Step 1: Build the Narrative\n\nStructure for non-technical audience. Each section answers a stakeholder question:\n\n1. **Hero** — \"What is this?\" Big title, one-sentence summary\n2. **The Problem** — \"Why did we do this?\" What was broken\u002Fmissing\u002Fpainful\n3. **What We Built** — \"What can I do now?\" 3-5 feature cards, outcome-focused\n4. **How It Works** — \"Is this reliable?\" Simplified architecture diagram, no jargon\n5. **Before\u002FAfter** — \"Did it improve things?\" Side-by-side metrics, workflow comparison\n6. **Impact** — \"What are the numbers?\" Speed, cost, reliability improvements\n7. **What's Next** — \"What's coming?\" 2-3 upcoming items\n8. **Team** — \"Who did this?\" Credits\n\n**Non-technical writing rules:**\n\n- No acronyms without explanation\n- No implementation details\n- Outcome language: \"You can now X\" not \"We implemented Y\"\n- Numbers over adjectives: \"3x faster\" not \"significantly improved\"\n\n### Step 2: Generate HTML Presentation\n\nSingle scrollable page with section snapping (not slides).\n\n**Design:**\n\n- Single file, zero external deps (except Mermaid CDN)\n- Large typography: hero 4rem, headings 2rem, body 1.125rem\n- Generous whitespace: 6rem+ between sections\n- Section snap scrolling: `scroll-snap-type: y mandatory`\n- Feature cards: grid layout, inline SVG icons, subtle border, hover lift\n- Before\u002FAfter: two-column with divider\n- Mermaid diagrams simplified, no technical jargon\n- Brand-neutral\n\n**CSS tokens:**\n\n```css\n:root {\n  --bg: #0a0a0a;\n  --bg-card: #141414;\n  --text: #fafafa;\n  --text-muted: #a1a1aa;\n  --border: #27272a;\n  --accent: #3b82f6;\n  --accent-soft: #1e3a5f;\n  --success: #22c55e;\n  --font-sans: \"Inter\", system-ui, -apple-system, sans-serif;\n  --font-display: \"Inter\", system-ui, -apple-system, sans-serif;\n}\n```\n\n**HTML structure:**\n\n```html\n\u003C!DOCTYPE html>\n\u003Chtml lang=\"en\">\n  \u003Chead>\n    ...\n  \u003C\u002Fhead>\n  \u003Cbody>\n    \u003Csection class=\"hero\">\n      \u003Ch1>{Title}\u003C\u002Fh1>\n      \u003Cp class=\"subtitle\">{summary}\u003C\u002Fp>\n      \u003Ctime>{Date}\u003C\u002Ftime>\n    \u003C\u002Fsection>\n    \u003Csection class=\"problem\">...\u003C\u002Fsection>\n    \u003Csection class=\"built\">\u003C!-- feature cards grid -->\u003C\u002Fsection>\n    \u003Csection class=\"how\">\u003C!-- Mermaid diagram -->\u003C\u002Fsection>\n    \u003Csection class=\"compare\">\u003C!-- Before\u002FAfter -->\u003C\u002Fsection>\n    \u003Csection class=\"impact\">\u003C!-- Impact numbers -->\u003C\u002Fsection>\n    \u003Csection class=\"next\">\u003C!-- What's Next -->\u003C\u002Fsection>\n    \u003Csection class=\"team\">\u003C!-- Credits -->\u003C\u002Fsection>\n    \u003Cscript>\n      \u002F* Mermaid init, scroll behavior *\u002F\n    \u003C\u002Fscript>\n  \u003C\u002Fbody>\n\u003C\u002Fhtml>\n```\n\n### Step 3: Generate Obsidian Canvas Companion\n\nGenerate a JSON Canvas (`.canvas`) file alongside the HTML.\n\n**Canvas structure:**\n\n- Central node (text, color \"6\" purple): product\u002Ffeature name + description\n- Component nodes arranged radially: green (\"4\") for new, blue (\"6\") for modified, no color for unchanged\n- Group nodes for clusters: Frontend, Backend, Data, Infrastructure\n- Edges with labels (connection type)\n- Layout: center at (0,0), groups in quadrants, nodes 300px apart\n\n**JSON Canvas format example:**\n\n```json\n{\n  \"nodes\": [\n    {\n      \"id\": \"center\",\n      \"type\": \"text\",\n      \"x\": 0,\n      \"y\": 0,\n      \"width\": 400,\n      \"height\": 200,\n      \"text\": \"# {Title}\\n{summary}\",\n      \"color\": \"6\"\n    },\n    {\n      \"id\": \"group-frontend\",\n      \"type\": \"group\",\n      \"x\": -600,\n      \"y\": -500,\n      \"width\": 500,\n      \"height\": 400,\n      \"label\": \"Frontend\"\n    },\n    {\n      \"id\": \"comp-1\",\n      \"type\": \"text\",\n      \"x\": -550,\n      \"y\": -400,\n      \"width\": 200,\n      \"height\": 100,\n      \"text\": \"**{Component}**\\n{description}\",\n      \"color\": \"4\"\n    }\n  ],\n  \"edges\": [\n    {\n      \"id\": \"edge-1\",\n      \"fromNode\": \"comp-1\",\n      \"toNode\": \"center\",\n      \"fromSide\": \"right\",\n      \"toSide\": \"left\",\n      \"label\": \"REST API\"\n    }\n  ]\n}\n```\n\n### Step 4: Save and Open\n\n1. Save HTML to `.presentations\u002F{YYYY-MM-DD}-{kebab-title}\u002Findex.html`\n2. Save Canvas to `.presentations\u002F{YYYY-MM-DD}-{kebab-title}\u002F{kebab-title}.canvas`\n3. Create the directory if it does not exist\n4. Open the HTML in the default browser:\n   - macOS: `open {path}`\n\n### Step 5: Present CLI Summary\n\n```\n╭─ ATLAS ── atlas-present ────────────────────╮\n\n  ## Presentation generated\n\n  **Title:** {title}\n  **Scope:** {date range or milestone}\n  **Repos:** {list of repos involved}\n\n  ### Deliverables\n  → .presentations\u002F{dir}\u002Findex.html (opened in browser)\n  → .presentations\u002F{dir}\u002F{title}.canvas (Obsidian)\n\n  ### Sections\n  - Hero, Problem, What We Built ({N} features)\n  - How It Works (architecture diagram)\n  - Before\u002FAfter, Impact, What's Next, Team\n\n╰─────────────────────────────────────────────╯\n```\n\n## Key Rules\n\n- **Non-technical audience** — no jargon, no implementation details\n- **Outcome language** — \"You can now X\" not \"We added Y\"\n- **Numbers over adjectives** — \"3x faster\" not \"much faster\"\n- **Self-contained HTML** — offline except Mermaid CDN\n- **Canvas nodes must have meaningful descriptions** — not just component names\n- **Omit Before\u002FAfter if no data** — do not fabricate metrics\n- **Manual trigger only** — presentations are intentional\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# Release Presentation\n\nYou are Atlas — the knowledge engineer on the Engineering Team. Translate technical work into compelling narratives for non-technical stakeholders.\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## Steps\n\n### Step 0: Determine Scope\n\nFrom user description, changelogs (`.changelog\u002FCHANGELOG.md`), git log (`--since={date}`), or PRs, identify:\n\n- **Title** — the name of the release or feature\n- **Date range** — when the work happened\n- **Repos involved** — which repositories contributed\n- **Audience** — default: non-technical stakeholders\n\nIf scope is ambiguous, ask the user before proceeding.\n\n### Step 1: Build the Narrative\n\nStructure for non-technical audience. Each section answers a stakeholder question:\n\n1. **Hero** — \"What is this?\" Big title, one-sentence summary\n2. **The Problem** — \"Why did we do this?\" What was broken\u002Fmissing\u002Fpainful\n3. **What We Built** — \"What can I do now?\" 3-5 feature cards, outcome-focused\n4. **How It Works** — \"Is this reliable?\" Simplified architecture diagram, no jargon\n5. **Before\u002FAfter** — \"Did it improve things?\" Side-by-side metrics, workflow comparison\n6. **Impact** — \"What are the numbers?\" Speed, cost, reliability improvements\n7. **What's Next** — \"What's coming?\" 2-3 upcoming items\n8. **Team** — \"Who did this?\" Credits\n\n**Non-technical writing rules:**\n\n- No acronyms without explanation\n- No implementation details\n- Outcome language: \"You can now X\" not \"We implemented Y\"\n- Numbers over adjectives: \"3x faster\" not \"significantly improved\"\n\n### Step 2: Generate HTML Presentation\n\nSingle scrollable page with section snapping (not slides).\n\n**Design:**\n\n- Single file, zero external deps (except Mermaid CDN)\n- Large typography: hero 4rem, headings 2rem, body 1.125rem\n- Generous whitespace: 6rem+ between sections\n- Section snap scrolling: `scroll-snap-type: y mandatory`\n- Feature cards: grid layout, inline SVG icons, subtle border, hover lift\n- Before\u002FAfter: two-column with divider\n- Mermaid diagrams simplified, no technical jargon\n- Brand-neutral\n\n**CSS tokens:**\n\n```css\n:root {\n  --bg: #0a0a0a;\n  --bg-card: #141414;\n  --text: #fafafa;\n  --text-muted: #a1a1aa;\n  --border: #27272a;\n  --accent: #3b82f6;\n  --accent-soft: #1e3a5f;\n  --success: #22c55e;\n  --font-sans: \"Inter\", system-ui, -apple-system, sans-serif;\n  --font-display: \"Inter\", system-ui, -apple-system, sans-serif;\n}\n```\n\n**HTML structure:**\n\n```html\n\u003C!DOCTYPE html>\n\u003Chtml lang=\"en\">\n  \u003Chead>\n    ...\n  \u003C\u002Fhead>\n  \u003Cbody>\n    \u003Csection class=\"hero\">\n      \u003Ch1>{Title}\u003C\u002Fh1>\n      \u003Cp class=\"subtitle\">{summary}\u003C\u002Fp>\n      \u003Ctime>{Date}\u003C\u002Ftime>\n    \u003C\u002Fsection>\n    \u003Csection class=\"problem\">...\u003C\u002Fsection>\n    \u003Csection class=\"built\">\u003C!-- feature cards grid -->\u003C\u002Fsection>\n    \u003Csection class=\"how\">\u003C!-- Mermaid diagram -->\u003C\u002Fsection>\n    \u003Csection class=\"compare\">\u003C!-- Before\u002FAfter -->\u003C\u002Fsection>\n    \u003Csection class=\"impact\">\u003C!-- Impact numbers -->\u003C\u002Fsection>\n    \u003Csection class=\"next\">\u003C!-- What's Next -->\u003C\u002Fsection>\n    \u003Csection class=\"team\">\u003C!-- Credits -->\u003C\u002Fsection>\n    \u003Cscript>\n      \u002F* Mermaid init, scroll behavior *\u002F\n    \u003C\u002Fscript>\n  \u003C\u002Fbody>\n\u003C\u002Fhtml>\n```\n\n### Step 3: Generate Obsidian Canvas Companion\n\nGenerate a JSON Canvas (`.canvas`) file alongside the HTML.\n\n**Canvas structure:**\n\n- Central node (text, color \"6\" purple): product\u002Ffeature name + description\n- Component nodes arranged radially: green (\"4\") for new, blue (\"6\") for modified, no color for unchanged\n- Group nodes for clusters: Frontend, Backend, Data, Infrastructure\n- Edges with labels (connection type)\n- Layout: center at (0,0), groups in quadrants, nodes 300px apart\n\n**JSON Canvas format example:**\n\n```json\n{\n  \"nodes\": [\n    {\n      \"id\": \"center\",\n      \"type\": \"text\",\n      \"x\": 0,\n      \"y\": 0,\n      \"width\": 400,\n      \"height\": 200,\n      \"text\": \"# {Title}\\n{summary}\",\n      \"color\": \"6\"\n    },\n    {\n      \"id\": \"group-frontend\",\n      \"type\": \"group\",\n      \"x\": -600,\n      \"y\": -500,\n      \"width\": 500,\n      \"height\": 400,\n      \"label\": \"Frontend\"\n    },\n    {\n      \"id\": \"comp-1\",\n      \"type\": \"text\",\n      \"x\": -550,\n      \"y\": -400,\n      \"width\": 200,\n      \"height\": 100,\n      \"text\": \"**{Component}**\\n{description}\",\n      \"color\": \"4\"\n    }\n  ],\n  \"edges\": [\n    {\n      \"id\": \"edge-1\",\n      \"fromNode\": \"comp-1\",\n      \"toNode\": \"center\",\n      \"fromSide\": \"right\",\n      \"toSide\": \"left\",\n      \"label\": \"REST API\"\n    }\n  ]\n}\n```\n\n### Step 4: Save and Open\n\n1. Save HTML to `.presentations\u002F{YYYY-MM-DD}-{kebab-title}\u002Findex.html`\n2. Save Canvas to `.presentations\u002F{YYYY-MM-DD}-{kebab-title}\u002F{kebab-title}.canvas`\n3. Create the directory if it does not exist\n4. Open the HTML in the default browser:\n   - macOS: `open {path}`\n\n### Step 5: Present CLI Summary\n\n```\n╭─ ATLAS ── atlas-present ────────────────────╮\n\n  ## Presentation generated\n\n  **Title:** {title}\n  **Scope:** {date range or milestone}\n  **Repos:** {list of repos involved}\n\n  ### Deliverables\n  → .presentations\u002F{dir}\u002Findex.html (opened in browser)\n  → .presentations\u002F{dir}\u002F{title}.canvas (Obsidian)\n\n  ### Sections\n  - Hero, Problem, What We Built ({N} features)\n  - How It Works (architecture diagram)\n  - Before\u002FAfter, Impact, What's Next, Team\n\n╰─────────────────────────────────────────────╯\n```\n\n## Key Rules\n\n- **Non-technical audience** — no jargon, no implementation details\n- **Outcome language** — \"You can now X\" not \"We added Y\"\n- **Numbers over adjectives** — \"3x faster\" not \"much faster\"\n- **Self-contained HTML** — offline except Mermaid CDN\n- **Canvas nodes must have meaningful descriptions** — not just component names\n- **Omit Before\u002FAfter if no data** — do not fabricate metrics\n- **Manual trigger only** — presentations are intentional\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":57,"author":59,"license":15,"version":60,"description":7,"allowed-tools":61,"compatibility":62},[58,49,30],"engineering","tonone-ai \u003Chello@tonone.ai>","0.6.4","Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion","Designed for Claude Code","main","d5998d31415790d88781b1eebf9bd0694f7c5d93","skills\u002Fatlas-present",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":74,"prompt":84,"zipAvailable":85},[75,78,81],{"tool":76,"command":77},"npx","npx skills add tonone-ai\u002Ftonone --skill atlas-present",{"tool":79,"command":80},"bunx","bunx skills add tonone-ai\u002Ftonone --skill atlas-present",{"tool":82,"command":83},"pnpm","pnpm dlx skills add tonone-ai\u002Ftonone --skill atlas-present","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fskills\u002Fatlas-present\u002FSKILL.md",true,[],[88,96,103,108,113,120],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":95},"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":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":95},"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":104,"name":90,"nameZh":6,"description":91,"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":95},"01M72PDNJ3NS66X4QZ6AM5BG91","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fskills\u002Fhelm-autoplan\u002FSKILL.md",[],[],{"skillNo":109,"name":98,"nameZh":6,"description":99,"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":95},"01M72NV58FG71X4Y7H8E6W721A","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fskills\u002Fapex-second-opinion\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":95},"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":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":95},"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",[],[]]