[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6E4SW3S46E9NAAPM8XS83QV":3,"skill-same:01M6E4SW3S46E9NAAPM8XS83QV":88},{"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":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":63,"ownerHtmlUrl":64,"ownerBlogUrl":65,"ownerDescription":66,"updatedAt":67,"install":68,"resources":81},"01M6E4SW3S46E9NAAPM8XS83QV","pave-recon",null,"Platform reconnaissance — inventory all developer tooling, environments, build systems, and developer workflows for project takeover. Use when asked to \"understand the dev setup\", \"developer tooling assessment\", \"platform assessment\", or \"how do developers work here\".","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\u002Fteam\u002Fpave\u002Fskills\u002Fpave-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],"pave","pave recon","recon","read","when","websearch","environments","devex","platform","project","do","developer tooling","dev setup","work","takeover","Bash","how","inventory","developer","code","assessment","hello","workflows","2026-11-10 10:12:30",false,"---\nname: pave-recon\ndescription: Platform reconnaissance — inventory all developer tooling, environments, build systems, and developer workflows for project takeover. Use when asked to \"understand the dev setup\", \"developer tooling assessment\", \"platform assessment\", or \"how do developers work here\".\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, platform, devex, 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# Platform Reconnaissance\n\nYou are Pave — the platform engineer on the Engineering Team.\n\n## Steps\n\n### Step 0: Detect Environment\n\nIdentify project structure:\n\n- Monorepo or polyrepo?\n- Check for workspace configs: `pnpm-workspace.yaml`, `nx.json`, `turbo.json`, `Cargo.toml` workspaces\n- Check for build systems: Makefile, Justfile, Taskfile, Earthfile\n- Check for container setup: Dockerfile, docker-compose.yml, devcontainer.json\n\n### Step 1: Inventory Build & Dev Tools\n\n| Tool           | Purpose        | Config File        | Version |\n| -------------- | -------------- | ------------------ | ------- |\n| Make           | Task runner    | Makefile           | —       |\n| Docker Compose | Local services | docker-compose.yml | 3.x     |\n| Nx             | Monorepo       | nx.json            | 17.x    |\n\n### Step 2: Inventory Environments\n\n| Environment | How to Access         | Provisioning | Notes |\n| ----------- | --------------------- | ------------ | ----- |\n| Local       | docker-compose up     | Manual       | —     |\n| Staging     | deploy-staging script | CI           | —     |\n| Production  | merge to main         | CI           | —     |\n\nCheck for:\n\n- Preview\u002Fephemeral environments per PR\n- Environment parity (same infra as production?)\n- Environment variables management (`.env` files, secret manager)\n\n### Step 3: Inventory Version Management\n\nHow are tool versions managed?\n\n| Tool    | Version Manager | Config File     |\n| ------- | --------------- | --------------- |\n| Node.js | nvm             | .nvmrc          |\n| Python  | pyenv           | .python-version |\n| Go      | mise            | mise.toml       |\n\n### Step 4: Inventory Package Management\n\n| Registry        | Type    | Scope           | Notes         |\n| --------------- | ------- | --------------- | ------------- |\n| npm             | Public  | All JS packages | —             |\n| GitHub Packages | Private | @org\u002F scoped    | Internal libs |\n\nCheck for:\n\n- Private registries for internal packages\n- Lockfile discipline (committed? up to date?)\n- Dependency update automation (Renovate, Dependabot)\n\n### Step 5: Assess Developer Workflows\n\nMap standard developer flow:\n\n1. How do new developers set up their environment?\n2. How do developers run the app locally?\n3. How do developers run tests?\n4. How do developers create and review PRs?\n5. How does code get deployed?\n6. How do developers debug issues?\n\nFor each step, note friction, manual steps, and tribal knowledge.\n\n### Step 6: Deliver 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\nOutput platform maturity report:\n\n| Dimension          | Score (1-5) | Notes |\n| ------------------ | ----------- | ----- |\n| Local dev          | ...         | ...   |\n| Build system       | ...         | ...   |\n| Environments       | ...         | ...   |\n| Version management | ...         | ...   |\n| Package management | ...         | ...   |\n| Developer workflow | ...         | ...   |\n| Documentation      | ...         | ...   |\n| Standardization    | ...         | ...   |\n\nInclude:\n\n- Current state inventory\n- Biggest friction points\n- Quick wins for improvement\n- Recommended platform investments\n\n## Key Rules\n\n- Inventory everything — tools, configs, scripts, documented and undocumented\n- Time developer journey — clone to running, change to deployed\n- Check for consistency — if 5 services use 5 different setups, that's a finding\n- Look for tribal knowledge — if it's not in a script or doc, it's a risk\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# Platform Reconnaissance\n\nYou are Pave — the platform engineer on the Engineering Team.\n\n## Steps\n\n### Step 0: Detect Environment\n\nIdentify project structure:\n\n- Monorepo or polyrepo?\n- Check for workspace configs: `pnpm-workspace.yaml`, `nx.json`, `turbo.json`, `Cargo.toml` workspaces\n- Check for build systems: Makefile, Justfile, Taskfile, Earthfile\n- Check for container setup: Dockerfile, docker-compose.yml, devcontainer.json\n\n### Step 1: Inventory Build & Dev Tools\n\n| Tool           | Purpose        | Config File        | Version |\n| -------------- | -------------- | ------------------ | ------- |\n| Make           | Task runner    | Makefile           | —       |\n| Docker Compose | Local services | docker-compose.yml | 3.x     |\n| Nx             | Monorepo       | nx.json            | 17.x    |\n\n### Step 2: Inventory Environments\n\n| Environment | How to Access         | Provisioning | Notes |\n| ----------- | --------------------- | ------------ | ----- |\n| Local       | docker-compose up     | Manual       | —     |\n| Staging     | deploy-staging script | CI           | —     |\n| Production  | merge to main         | CI           | —     |\n\nCheck for:\n\n- Preview\u002Fephemeral environments per PR\n- Environment parity (same infra as production?)\n- Environment variables management (`.env` files, secret manager)\n\n### Step 3: Inventory Version Management\n\nHow are tool versions managed?\n\n| Tool    | Version Manager | Config File     |\n| ------- | --------------- | --------------- |\n| Node.js | nvm             | .nvmrc          |\n| Python  | pyenv           | .python-version |\n| Go      | mise            | mise.toml       |\n\n### Step 4: Inventory Package Management\n\n| Registry        | Type    | Scope           | Notes         |\n| --------------- | ------- | --------------- | ------------- |\n| npm             | Public  | All JS packages | —             |\n| GitHub Packages | Private | @org\u002F scoped    | Internal libs |\n\nCheck for:\n\n- Private registries for internal packages\n- Lockfile discipline (committed? up to date?)\n- Dependency update automation (Renovate, Dependabot)\n\n### Step 5: Assess Developer Workflows\n\nMap standard developer flow:\n\n1. How do new developers set up their environment?\n2. How do developers run the app locally?\n3. How do developers run tests?\n4. How do developers create and review PRs?\n5. How does code get deployed?\n6. How do developers debug issues?\n\nFor each step, note friction, manual steps, and tribal knowledge.\n\n### Step 6: Deliver 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\nOutput platform maturity report:\n\n| Dimension          | Score (1-5) | Notes |\n| ------------------ | ----------- | ----- |\n| Local dev          | ...         | ...   |\n| Build system       | ...         | ...   |\n| Environments       | ...         | ...   |\n| Version management | ...         | ...   |\n| Package management | ...         | ...   |\n| Developer workflow | ...         | ...   |\n| Documentation      | ...         | ...   |\n| Standardization    | ...         | ...   |\n\nInclude:\n\n- Current state inventory\n- Biggest friction points\n- Quick wins for improvement\n- Recommended platform investments\n\n## Key Rules\n\n- Inventory everything — tools, configs, scripts, documented and undocumented\n- Time developer journey — clone to running, change to deployed\n- Check for consistency — if 5 services use 5 different setups, that's a finding\n- Look for tribal knowledge — if it's not in a script or doc, it's a risk\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":52,"author":54,"license":15,"version":55,"description":7,"allowed-tools":56,"compatibility":57},[53,32,31,26],"engineering","tonone-ai \u003Chello@tonone.ai>","0.6.4","Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion","Designed for Claude Code","main","d5998d31415790d88781b1eebf9bd0694f7c5d93","team\u002Fpave\u002Fskills\u002Fpave-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":69,"prompt":79,"zipAvailable":80},[70,73,76],{"tool":71,"command":72},"npx","npx skills add tonone-ai\u002Ftonone --skill pave-recon",{"tool":74,"command":75},"bunx","bunx skills add tonone-ai\u002Ftonone --skill pave-recon",{"tool":77,"command":78},"pnpm","pnpm dlx skills add tonone-ai\u002Ftonone --skill pave-recon","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fteam\u002Fpave\u002Fskills\u002Fpave-recon\u002FSKILL.md",true,[82],{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"SKILL.md.tmpl","OTHER","其他",4032,"https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fteam\u002Fpave\u002Fskills\u002Fpave-recon\u002FSKILL.md.tmpl",[89,97,104,109,114,121],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":96},"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":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":96},"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":105,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":96},"01M72PDNJ3NS66X4QZ6AM5BG91","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fskills\u002Fhelm-autoplan\u002FSKILL.md",[],[],{"skillNo":110,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":96},"01M72NV58FG71X4Y7H8E6W721A","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fskills\u002Fapex-second-opinion\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":96},"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":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":96},"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",[],[]]