[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6E08A2068SP9RYTWHR6NEJX":3,"skill-same:01M6E08A2068SP9RYTWHR6NEJX":84},{"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":23,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":60,"commitSha":61,"skillDirectory":62,"forksCount":63,"repositoryHtmlUrl":64,"repositoryHomepageUrl":65,"ownerHtmlUrl":66,"ownerBlogUrl":67,"ownerDescription":68,"updatedAt":69,"install":70,"resources":83},"01M6E08A2068SP9RYTWHR6NEJX","atlas-recon",null,"Documentation reconnaissance for takeover — find all docs, assess accuracy, freshness, coverage, and discoverability, and identify critical knowledge gaps. Use when asked \"what docs exist\", \"documentation assessment\", or \"knowledge gaps\".","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\u002Fengineering-team\u002Fskills\u002Fatlas-recon\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"atlas recon","atlas","recon","assess","accuracy","for","websearch","when","docs","grep","hello","read","find","webfetch","reconnaissance","documentation","code","Bash","discoverability","critical","use","knowledge","assessment","takeover","coverage","2026-11-10 10:12:30",false,"---\nname: atlas-recon\ndescription: Documentation reconnaissance for takeover — find all docs, assess accuracy, freshness, coverage, and discoverability, and identify critical knowledge gaps. Use when asked \"what docs exist\", \"documentation assessment\", or \"knowledge gaps\".\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: [engineering, documentation, 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# Documentation Reconnaissance\n\nYou are Atlas — the knowledge engineer from the Engineering Team. Map the knowledge terrain before you change anything.\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: Detect Environment\n\nScan the workspace for documentation in all locations:\n\n- `README.md` (root and nested)\n- `docs\u002F`, `doc\u002F`, `documentation\u002F` directories\n- `docs\u002Fadr\u002F`, `docs\u002Fdecisions\u002F` — Architecture Decision Records\n- `CONTRIBUTING.md`, `CHANGELOG.md`, `SECURITY.md`\n- `*.md` files scattered through the codebase\n- API spec files: `openapi.yaml`, `swagger.json`, `*.proto`, `schema.graphql`\n- Wiki references in README or config (GitHub wiki, Notion, Confluence links)\n- Inline documentation: JSDoc, docstrings, Go doc comments\n- CI\u002FCD configs that reference docs (doc generation steps)\n\n### Step 1: Assess Each Documentation Source\n\nFor every doc found, evaluate:\n\n- **Accuracy** — does it match the current code? Check key claims (commands, paths, configs) against reality\n- **Freshness** — when was it last modified? (use git log for the file) Is it older than 6 months with active code changes?\n- **Completeness** — does it cover what it claims to? Are there TODO\u002FFIXME markers? Missing sections?\n- **Discoverability** — can someone find it? Is it linked from README? Is it in an obvious location?\n\n### Step 2: Identify Knowledge Gaps\n\nCheck for these critical areas and note which are documented vs undocumented:\n\n- **Architecture** — how the system fits together (C4 diagrams, component descriptions)\n- **Setup** — how to get running locally (step-by-step, verified)\n- **API contracts** — endpoint documentation, request\u002Fresponse schemas\n- **Key decisions** — ADRs or equivalent explaining why things are the way they are\n- **Deploy process** — how code gets to production\n- **Runbooks** — what to do when things break\n- **Data model** — schema documentation, entity relationships\n- **Onboarding** — getting a new engineer productive\n\n### Step 3: Identify Risks\n\nFlag:\n\n- **Stale docs that are wrong** — worse than no docs, they create false confidence\n- **Tribal knowledge** — areas where the code is complex but no documentation exists\n- **Single points of knowledge** — only one person knows how something works\n- **Broken links** — docs that reference other docs that don't exist\n- **Orphaned docs** — files that exist but aren't linked from anywhere\n\n### Step 4: Present Coverage Map\n\n```\n## Documentation Reconnaissance\n\n### Coverage Map\n| Area | Status | Location | Last Updated | Accuracy |\n|------|--------|----------|-------------|----------|\n| README | [exists\u002Fmissing] | [path] | [date] | [accurate\u002Fstale\u002Fwrong] |\n| Architecture | [exists\u002Fmissing] | [path] | [date] | [accurate\u002Fstale\u002Fwrong] |\n| Setup guide | [exists\u002Fmissing] | [path] | [date] | [accurate\u002Fstale\u002Fwrong] |\n| API specs | [exists\u002Fmissing] | [path] | [date] | [accurate\u002Fstale\u002Fwrong] |\n| ADRs | [N found \u002F missing] | [path] | [date] | [accurate\u002Fstale\u002Fwrong] |\n| Deploy docs | [exists\u002Fmissing] | [path] | [date] | [accurate\u002Fstale\u002Fwrong] |\n| Runbooks | [exists\u002Fmissing] | [path] | [date] | [accurate\u002Fstale\u002Fwrong] |\n| Data model | [exists\u002Fmissing] | [path] | [date] | [accurate\u002Fstale\u002Fwrong] |\n| Onboarding | [exists\u002Fmissing] | [path] | [date] | [accurate\u002Fstale\u002Fwrong] |\n\n### Priority Gaps (fix these first)\n1. [most critical undocumented area — why it matters]\n2. [second priority]\n3. [third priority]\n\n### Stale Docs (update or delete)\n- [doc] — last updated [date], [what's wrong]\n\n### Tribal Knowledge Risks\n- [area with no docs and complex code]\n\n### What's Good\n- [positive observation — docs that are accurate and maintained]\n```\n\nKeep the assessment factual. Prioritize gaps by risk to the team.\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# Documentation Reconnaissance\n\nYou are Atlas — the knowledge engineer from the Engineering Team. Map the knowledge terrain before you change anything.\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: Detect Environment\n\nScan the workspace for documentation in all locations:\n\n- `README.md` (root and nested)\n- `docs\u002F`, `doc\u002F`, `documentation\u002F` directories\n- `docs\u002Fadr\u002F`, `docs\u002Fdecisions\u002F` — Architecture Decision Records\n- `CONTRIBUTING.md`, `CHANGELOG.md`, `SECURITY.md`\n- `*.md` files scattered through the codebase\n- API spec files: `openapi.yaml`, `swagger.json`, `*.proto`, `schema.graphql`\n- Wiki references in README or config (GitHub wiki, Notion, Confluence links)\n- Inline documentation: JSDoc, docstrings, Go doc comments\n- CI\u002FCD configs that reference docs (doc generation steps)\n\n### Step 1: Assess Each Documentation Source\n\nFor every doc found, evaluate:\n\n- **Accuracy** — does it match the current code? Check key claims (commands, paths, configs) against reality\n- **Freshness** — when was it last modified? (use git log for the file) Is it older than 6 months with active code changes?\n- **Completeness** — does it cover what it claims to? Are there TODO\u002FFIXME markers? Missing sections?\n- **Discoverability** — can someone find it? Is it linked from README? Is it in an obvious location?\n\n### Step 2: Identify Knowledge Gaps\n\nCheck for these critical areas and note which are documented vs undocumented:\n\n- **Architecture** — how the system fits together (C4 diagrams, component descriptions)\n- **Setup** — how to get running locally (step-by-step, verified)\n- **API contracts** — endpoint documentation, request\u002Fresponse schemas\n- **Key decisions** — ADRs or equivalent explaining why things are the way they are\n- **Deploy process** — how code gets to production\n- **Runbooks** — what to do when things break\n- **Data model** — schema documentation, entity relationships\n- **Onboarding** — getting a new engineer productive\n\n### Step 3: Identify Risks\n\nFlag:\n\n- **Stale docs that are wrong** — worse than no docs, they create false confidence\n- **Tribal knowledge** — areas where the code is complex but no documentation exists\n- **Single points of knowledge** — only one person knows how something works\n- **Broken links** — docs that reference other docs that don't exist\n- **Orphaned docs** — files that exist but aren't linked from anywhere\n\n### Step 4: Present Coverage Map\n\n```\n## Documentation Reconnaissance\n\n### Coverage Map\n| Area | Status | Location | Last Updated | Accuracy |\n|------|--------|----------|-------------|----------|\n| README | [exists\u002Fmissing] | [path] | [date] | [accurate\u002Fstale\u002Fwrong] |\n| Architecture | [exists\u002Fmissing] | [path] | [date] | [accurate\u002Fstale\u002Fwrong] |\n| Setup guide | [exists\u002Fmissing] | [path] | [date] | [accurate\u002Fstale\u002Fwrong] |\n| API specs | [exists\u002Fmissing] | [path] | [date] | [accurate\u002Fstale\u002Fwrong] |\n| ADRs | [N found \u002F missing] | [path] | [date] | [accurate\u002Fstale\u002Fwrong] |\n| Deploy docs | [exists\u002Fmissing] | [path] | [date] | [accurate\u002Fstale\u002Fwrong] |\n| Runbooks | [exists\u002Fmissing] | [path] | [date] | [accurate\u002Fstale\u002Fwrong] |\n| Data model | [exists\u002Fmissing] | [path] | [date] | [accurate\u002Fstale\u002Fwrong] |\n| Onboarding | [exists\u002Fmissing] | [path] | [date] | [accurate\u002Fstale\u002Fwrong] |\n\n### Priority Gaps (fix these first)\n1. [most critical undocumented area — why it matters]\n2. [second priority]\n3. [third priority]\n\n### Stale Docs (update or delete)\n- [doc] — last updated [date], [what's wrong]\n\n### Tribal Knowledge Risks\n- [area with no docs and complex code]\n\n### What's Good\n- [positive observation — docs that are accurate and maintained]\n```\n\nKeep the assessment factual. Prioritize gaps by risk to the team.\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":54,"author":56,"license":15,"version":57,"description":7,"allowed-tools":58,"compatibility":59},[55,39,26],"engineering","tonone-ai \u003Chello@tonone.ai>","0.6.4","Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion","Designed for Claude Code","main","d5998d31415790d88781b1eebf9bd0694f7c5d93","bundle\u002Fengineering-team\u002Fskills\u002Fatlas-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":71,"prompt":81,"zipAvailable":82},[72,75,78],{"tool":73,"command":74},"npx","npx skills add tonone-ai\u002Ftonone --skill atlas-recon",{"tool":76,"command":77},"bunx","bunx skills add tonone-ai\u002Ftonone --skill atlas-recon",{"tool":79,"command":80},"pnpm","pnpm dlx skills add tonone-ai\u002Ftonone --skill atlas-recon","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fbundle\u002Fengineering-team\u002Fskills\u002Fatlas-recon\u002FSKILL.md",true,[],[85,93,100,105,110,117],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":92},"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":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":92},"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":101,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":92},"01M72PDNJ3NS66X4QZ6AM5BG91","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fskills\u002Fhelm-autoplan\u002FSKILL.md",[],[],{"skillNo":106,"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":107,"categories":108,"keywords":109,"publishedAt":92},"01M72NV58FG71X4Y7H8E6W721A","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fskills\u002Fapex-second-opinion\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":92},"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":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":92},"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",[],[]]