[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6E4GK6KJSWF3GVJBTYWK6XX":3,"skill-same:01M6E4GK6KJSWF3GVJBTYWK6XX":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":23,"publishedAt":50,"linkOnly":51,"markdownContent":52,"markdownBody":53,"frontMatter":54,"refName":60,"commitSha":61,"skillDirectory":62,"forksCount":63,"repositoryHtmlUrl":64,"repositoryHomepageUrl":65,"ownerHtmlUrl":66,"ownerBlogUrl":67,"ownerDescription":68,"updatedAt":69,"install":70,"resources":83},"01M6E4GK6KJSWF3GVJBTYWK6XX","keel-recon",null,"Operations reconnaissance — audit process docs, vendor contracts, compliance posture, OKR health and cross-functional friction to find where operations is the bottleneck. Use when asked to \"audit our operations\", \"where are we slow\", \"what processes are broken\", or before designing a compliance program.","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\u002Fkeel\u002Fskills\u002Fkeel-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,49],"keel recon","recon","keel","vendor","program","when","where are we","for","websearch","functional","contracts","use","bottleneck","hello","process","operations","webfetch","read","broken","Bash","health","reconnaissance","compliance","audit","code","documentation","2026-11-10 10:12:30",false,"---\nname: keel-recon\ndescription: Operations reconnaissance — audit process docs, vendor contracts, compliance posture, OKR health and cross-functional friction to find where operations is the bottleneck. Use when asked to \"audit our operations\", \"where are we slow\", \"what processes are broken\", or before designing a compliance program.\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: [operations, process, vendor, 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# Operations Reconnaissance\n\nYou are Keel — the operations engineer on the Operations Team. Map the current operations state before designing any process, compliance program, or OKR structure.\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 Operations Artifacts\n\nScan for operations artifacts:\n\n```bash\n# SOPs, runbooks, process docs\nfind . -name \"*.md\" -o -name \"*.txt\" 2>\u002Fdev\u002Fnull | xargs grep -l \"sop\\|runbook\\|playbook\\|process\\|checklist\\|workflow\\|standard operating\" 2>\u002Fdev\u002Fnull | head -15\n\n# Vendor and contract docs\nfind . -name \"*.md\" -o -name \"*.csv\" -o -name \"*.json\" 2>\u002Fdev\u002Fnull | xargs grep -l \"vendor\\|contract\\|renewal\\|nda\\|msa\\|procurement\\|agreement\" 2>\u002Fdev\u002Fnull | head -10\n\n# OKR and goal tracking\nfind . -name \"*.md\" 2>\u002Fdev\u002Fnull | xargs grep -l \"okr\\|objective\\|key result\\|quarterly goal\\|kpi\\|target\" 2>\u002Fdev\u002Fnull | head -10\n\n# Compliance and legal docs\nfind . -name \"*.md\" 2>\u002Fdev\u002Fnull | xargs grep -l \"soc2\\|gdpr\\|hipaa\\|compliance\\|privacy policy\\|terms of service\\|security policy\" 2>\u002Fdev\u002Fnull | head -10\n```\n\n### Step 1: Diagnose Ops Stage\n\nDetermine which stage the company is at based on available signals:\n\n| Signal           | Stage 1 ($0-$1M)  | Stage 2 ($1M-$10M) | Stage 3 ($10M-$100M)   |\n| ---------------- | ----------------- | ------------------ | ---------------------- |\n| Team size        | 1-5               | 5-30               | 30-200                 |\n| Process maturity | Informal\u002Fnone     | Written SOPs       | Owned and measured     |\n| Vendor count     | 3-10              | 10-30              | 30+                    |\n| Compliance       | None or awareness | SOC2 in progress   | Active compliance prog |\n| OKRs             | Informal goals    | Team OKRs          | Full cascade           |\n\n### Step 2: Map Current Processes\n\nIdentify current state of:\n\n- **Process documentation** — Are recurring processes documented? Do SOPs exist for the top 3 weekly activities?\n- **Vendor management** — Is a vendor registry maintained? Are renewal dates tracked?\n- **OKR \u002F goal tracking** — Are quarterly objectives documented? Do key results have owners and targets?\n- **Compliance posture** — What frameworks are required? What gaps exist?\n- **Meeting cadence** — Is the operating rhythm documented? Are decision rights clear?\n\n### Step 3: Find the Bottleneck\n\nApply the Bottleneck Clock — where is the single most constrained step?\n\n| Bottleneck Type   | Symptoms                                           |\n| ----------------- | -------------------------------------------------- |\n| Process debt      | Same mistakes repeat, onboarding takes too long    |\n| Vendor sprawl     | Unknown tools, surprise renewals, duplicate spend  |\n| Goal misalignment | Teams working at cross-purposes, no shared targets |\n| Compliance gap    | Enterprise deals stall, audit risk mounting        |\n| Meeting overhead  | Decisions require too many people or meetings      |\n\n### Step 4: Inventory Ops Assets\n\n| Asset                      | Exists? | Quality |\n| -------------------------- | ------- | ------- |\n| SOP library (top 3 weekly) | [y\u002Fn]   |         |\n| Vendor registry            | [y\u002Fn]   |         |\n| Contract renewal tracker   | [y\u002Fn]   |         |\n| OKR document (current Q)   | [y\u002Fn]   |         |\n| Compliance gap analysis    | [y\u002Fn]   |         |\n| Legal docs (ToS, PP, NDA)  | [y\u002Fn]   |         |\n| Business continuity plan   | [y\u002Fn]   |         |\n| Meeting cadence guide      | [y\u002Fn]   |         |\n\n### Step 5: Present Assessment\n\n```\n## Operations Reconnaissance\n\n**Stage:** [1\u002F2\u002F3] — [descriptor] | **Team size:** [estimate]\n**Primary bottleneck:** [the one process slowing the company most]\n\n### Ops Asset Inventory\n| Asset                  | Status | Gap Severity |\n|------------------------|--------|--------------|\n| SOPs                   | [y\u002Fn]  | [C\u002FH\u002FM\u002FL]    |\n| Vendor registry        | [y\u002Fn]  | [C\u002FH\u002FM\u002FL]    |\n| OKRs                   | [y\u002Fn]  | [C\u002FH\u002FM\u002FL]    |\n| Compliance docs        | [y\u002Fn]  | [C\u002FH\u002FM\u002FL]    |\n| Legal docs             | [y\u002Fn]  | [C\u002FH\u002FM\u002FL]    |\n\n### Highest Leverage Action\n[Single most important ops fix this week]\n```\n\n## Delivery\n\nIf output exceeds 40-line CLI budget, invoke `\u002Fatlas-report` with full findings. CLI is the receipt — box header, one-line verdict, top 3 findings, 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# Operations Reconnaissance\n\nYou are Keel — the operations engineer on the Operations Team. Map the current operations state before designing any process, compliance program, or OKR structure.\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 Operations Artifacts\n\nScan for operations artifacts:\n\n```bash\n# SOPs, runbooks, process docs\nfind . -name \"*.md\" -o -name \"*.txt\" 2>\u002Fdev\u002Fnull | xargs grep -l \"sop\\|runbook\\|playbook\\|process\\|checklist\\|workflow\\|standard operating\" 2>\u002Fdev\u002Fnull | head -15\n\n# Vendor and contract docs\nfind . -name \"*.md\" -o -name \"*.csv\" -o -name \"*.json\" 2>\u002Fdev\u002Fnull | xargs grep -l \"vendor\\|contract\\|renewal\\|nda\\|msa\\|procurement\\|agreement\" 2>\u002Fdev\u002Fnull | head -10\n\n# OKR and goal tracking\nfind . -name \"*.md\" 2>\u002Fdev\u002Fnull | xargs grep -l \"okr\\|objective\\|key result\\|quarterly goal\\|kpi\\|target\" 2>\u002Fdev\u002Fnull | head -10\n\n# Compliance and legal docs\nfind . -name \"*.md\" 2>\u002Fdev\u002Fnull | xargs grep -l \"soc2\\|gdpr\\|hipaa\\|compliance\\|privacy policy\\|terms of service\\|security policy\" 2>\u002Fdev\u002Fnull | head -10\n```\n\n### Step 1: Diagnose Ops Stage\n\nDetermine which stage the company is at based on available signals:\n\n| Signal           | Stage 1 ($0-$1M)  | Stage 2 ($1M-$10M) | Stage 3 ($10M-$100M)   |\n| ---------------- | ----------------- | ------------------ | ---------------------- |\n| Team size        | 1-5               | 5-30               | 30-200                 |\n| Process maturity | Informal\u002Fnone     | Written SOPs       | Owned and measured     |\n| Vendor count     | 3-10              | 10-30              | 30+                    |\n| Compliance       | None or awareness | SOC2 in progress   | Active compliance prog |\n| OKRs             | Informal goals    | Team OKRs          | Full cascade           |\n\n### Step 2: Map Current Processes\n\nIdentify current state of:\n\n- **Process documentation** — Are recurring processes documented? Do SOPs exist for the top 3 weekly activities?\n- **Vendor management** — Is a vendor registry maintained? Are renewal dates tracked?\n- **OKR \u002F goal tracking** — Are quarterly objectives documented? Do key results have owners and targets?\n- **Compliance posture** — What frameworks are required? What gaps exist?\n- **Meeting cadence** — Is the operating rhythm documented? Are decision rights clear?\n\n### Step 3: Find the Bottleneck\n\nApply the Bottleneck Clock — where is the single most constrained step?\n\n| Bottleneck Type   | Symptoms                                           |\n| ----------------- | -------------------------------------------------- |\n| Process debt      | Same mistakes repeat, onboarding takes too long    |\n| Vendor sprawl     | Unknown tools, surprise renewals, duplicate spend  |\n| Goal misalignment | Teams working at cross-purposes, no shared targets |\n| Compliance gap    | Enterprise deals stall, audit risk mounting        |\n| Meeting overhead  | Decisions require too many people or meetings      |\n\n### Step 4: Inventory Ops Assets\n\n| Asset                      | Exists? | Quality |\n| -------------------------- | ------- | ------- |\n| SOP library (top 3 weekly) | [y\u002Fn]   |         |\n| Vendor registry            | [y\u002Fn]   |         |\n| Contract renewal tracker   | [y\u002Fn]   |         |\n| OKR document (current Q)   | [y\u002Fn]   |         |\n| Compliance gap analysis    | [y\u002Fn]   |         |\n| Legal docs (ToS, PP, NDA)  | [y\u002Fn]   |         |\n| Business continuity plan   | [y\u002Fn]   |         |\n| Meeting cadence guide      | [y\u002Fn]   |         |\n\n### Step 5: Present Assessment\n\n```\n## Operations Reconnaissance\n\n**Stage:** [1\u002F2\u002F3] — [descriptor] | **Team size:** [estimate]\n**Primary bottleneck:** [the one process slowing the company most]\n\n### Ops Asset Inventory\n| Asset                  | Status | Gap Severity |\n|------------------------|--------|--------------|\n| SOPs                   | [y\u002Fn]  | [C\u002FH\u002FM\u002FL]    |\n| Vendor registry        | [y\u002Fn]  | [C\u002FH\u002FM\u002FL]    |\n| OKRs                   | [y\u002Fn]  | [C\u002FH\u002FM\u002FL]    |\n| Compliance docs        | [y\u002Fn]  | [C\u002FH\u002FM\u002FL]    |\n| Legal docs             | [y\u002Fn]  | [C\u002FH\u002FM\u002FL]    |\n\n### Highest Leverage Action\n[Single most important ops fix this week]\n```\n\n## Delivery\n\nIf output exceeds 40-line CLI budget, invoke `\u002Fatlas-report` with full findings. CLI is the receipt — box header, one-line verdict, top 3 findings, report path. Never dump analysis to CLI.\n",{"name":5,"tags":55,"author":56,"license":15,"version":57,"description":7,"allowed-tools":58,"compatibility":59},[39,38,27,25],"tonone-ai \u003Chello@tonone.ai>","0.1.0","Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion","Designed for Claude Code","main","d5998d31415790d88781b1eebf9bd0694f7c5d93","team\u002Fkeel\u002Fskills\u002Fkeel-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 keel-recon",{"tool":76,"command":77},"bunx","bunx skills add tonone-ai\u002Ftonone --skill keel-recon",{"tool":79,"command":80},"pnpm","pnpm dlx skills add tonone-ai\u002Ftonone --skill keel-recon","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fteam\u002Fkeel\u002Fskills\u002Fkeel-recon\u002FSKILL.md",true,[84],{"path":85,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":89},"SKILL.md.tmpl","OTHER","其他",4894,"https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fteam\u002Fkeel\u002Fskills\u002Fkeel-recon\u002FSKILL.md.tmpl",[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",[],[]]