[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XDBBMCRAXJVDM0W1TTQC67":3,"skill-same:01M6XDBBMCRAXJVDM0W1TTQC67":68},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":14,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":6,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M6XDBBMCRAXJVDM0W1TTQC67","ground-first",null,"Produce a code-grounded analysis before any edit is proposed. Triggers on: \"analyze\", \"understand behavior\", \"how does this work\".","kaiohenricunha\u002Fdotbabel","kaiohenricunha","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F69804490?v=4","01M6XCZD37W0KPCDGEA40Y610V","Kaio Cunha","01M6XCZD7SX714D114H3ZPNW09",0,"MIT","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fplugins\u002Fdotbabel\u002Ftemplates\u002Fclaude\u002Fskills\u002Fground-first\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],"first","ground first","code","produce","analysis","how","Bash","analyze","grep","work","read","edit","behavior","triggers","understand","2026-11-10 10:12:30",false,"---\n# dotbabel:generated projection=sha256:7085e540f729873cc278c1c21e08c920c6834d398e231a037eb0b2f9ece7c15c source=skills\u002Fground-first\u002FSKILL.md — do not edit directly\nallowed-tools: Read Grep Glob Bash\nargument-hint: \"[subject]\"\ndescription: |\n  Produce a code-grounded analysis before any edit is proposed. Triggers on: \"analyze\", \"understand behavior\", \"how does this work\".\nname: ground-first\n---\n\nProduce a code-grounded analysis of a subject before any edits are proposed.\n\nTrigger: when the user asks for a fix, change, or investigation on non-trivial code and has not yet confirmed you understand current behavior. Also triggered directly via `\u002Fground-first`.\n\nArguments: `$ARGUMENTS` — a description of what to analyze (e.g. \"auth token refresh race condition\", \"why ingest job retries forever\", \"issue #140\").\n\n## Steps\n\n1. **Parse the subject** from `$ARGUMENTS`. If empty or vague, infer from recent conversation. If still unclear, ask the user what they want analyzed.\n\n2. **Locate the relevant code.** Use these tools, in this order:\n   - `Glob` to find candidate files by name pattern\n   - `Grep` to find candidate files by symbol\u002Fstring\n   - `Read` every candidate file that survives the first two steps. Read the actual file — do not infer from its name.\n\n3. **Produce the analysis** in this format:\n\n   ```markdown\n   ## Subject\n\n   \u003Cone-line restatement of the subject>\n\n   ## Current behavior\n\n   - \u003Cclaim>. `path\u002Fto\u002Ffile.go:42`\n   - \u003Cclaim>. `path\u002Fto\u002Fother.ts:120–140`\n\n   ## Relevant entry points\n\n   - `path\u002Fto\u002Fhandler.go:15` — `HandleIngest()`\n   - `path\u002Fto\u002Fconfig.yaml:8` — `retries: 3`\n\n   ## What I do not yet know\n\n   - \u003Cspecific unknown, e.g. \"whether the retry limit is overridden at runtime\">\n   - \u003Cspecific unknown>\n\n   ## Proposed next steps (not yet actioned)\n\n   1. \u003Cstep>\n   2. \u003Cstep>\n   ```\n\n4. **STOP.** Do not call `Edit`, `Write`, or any other mutation tool. Wait for the user to confirm the analysis matches reality or to correct it.\n\n## Rules\n\n- Every claim must cite a `file:line` or `file:line–line` reference from a file you actually read in this session.\n- If you cannot find a file that supports a claim, list the claim under \"What I do not yet know\" instead of asserting it.\n- Do not propose edits. Do not run tests. Do not make changes. This command is read-only by design.\n- Keep the analysis under ~30 lines. Cite more, narrate less.\n- If the subject turns out to be trivial (e.g., a typo fix), say so and hand control back — don't pad.\n","Produce a code-grounded analysis of a subject before any edits are proposed.\n\nTrigger: when the user asks for a fix, change, or investigation on non-trivial code and has not yet confirmed you understand current behavior. Also triggered directly via `\u002Fground-first`.\n\nArguments: `$ARGUMENTS` — a description of what to analyze (e.g. \"auth token refresh race condition\", \"why ingest job retries forever\", \"issue #140\").\n\n## Steps\n\n1. **Parse the subject** from `$ARGUMENTS`. If empty or vague, infer from recent conversation. If still unclear, ask the user what they want analyzed.\n\n2. **Locate the relevant code.** Use these tools, in this order:\n   - `Glob` to find candidate files by name pattern\n   - `Grep` to find candidate files by symbol\u002Fstring\n   - `Read` every candidate file that survives the first two steps. Read the actual file — do not infer from its name.\n\n3. **Produce the analysis** in this format:\n\n   ```markdown\n   ## Subject\n\n   \u003Cone-line restatement of the subject>\n\n   ## Current behavior\n\n   - \u003Cclaim>. `path\u002Fto\u002Ffile.go:42`\n   - \u003Cclaim>. `path\u002Fto\u002Fother.ts:120–140`\n\n   ## Relevant entry points\n\n   - `path\u002Fto\u002Fhandler.go:15` — `HandleIngest()`\n   - `path\u002Fto\u002Fconfig.yaml:8` — `retries: 3`\n\n   ## What I do not yet know\n\n   - \u003Cspecific unknown, e.g. \"whether the retry limit is overridden at runtime\">\n   - \u003Cspecific unknown>\n\n   ## Proposed next steps (not yet actioned)\n\n   1. \u003Cstep>\n   2. \u003Cstep>\n   ```\n\n4. **STOP.** Do not call `Edit`, `Write`, or any other mutation tool. Wait for the user to confirm the analysis matches reality or to correct it.\n\n## Rules\n\n- Every claim must cite a `file:line` or `file:line–line` reference from a file you actually read in this session.\n- If you cannot find a file that supports a claim, list the claim under \"What I do not yet know\" instead of asserting it.\n- Do not propose edits. Do not run tests. Do not make changes. This command is read-only by design.\n- Keep the analysis under ~30 lines. Cite more, narrate less.\n- If the subject turns out to be trivial (e.g., a typo fix), say so and hand control back — don't pad.\n",{"name":5,"description":44,"allowed-tools":45,"argument-hint":46},"Produce a code-grounded analysis before any edit is proposed. Triggers on: \"analyze\", \"understand behavior\", \"how does this work\".\n","Read Grep Glob Bash","[subject]","main","91c337164997b99943fbcc64e8e362577b67bc81","plugins\u002Fdotbabel\u002Ftemplates\u002Fclaude\u002Fskills\u002Fground-first","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha","I'm a Platform\u002FInfra engineer who happens to work in cybersec and write Go code.","2026-10-26 14:12:51",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add kaiohenricunha\u002Fdotbabel --skill ground-first",{"tool":60,"command":61},"bunx","bunx skills add kaiohenricunha\u002Fdotbabel --skill ground-first",{"tool":63,"command":64},"pnpm","pnpm dlx skills add kaiohenricunha\u002Fdotbabel --skill ground-first","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fplugins\u002Fdotbabel\u002Ftemplates\u002Fclaude\u002Fskills\u002Fground-first\u002FSKILL.md",true,[],[69,95,128,148,169,192],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":76,"publishedAt":39},"01M6XDQ7QMASPFZ355MYKCD06T","yolo","Start temporary autonomy for the current task or an explicit scope with a required --for expiry. Codex permits scoped pushes, merges, deploys, and releases after strict testing and validation; Full access is a separate runtime setting. Claude Code uses a session permission hook with a protected-action denylist.","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Fyolo\u002FSKILL.md",[75],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[71,77,78,26,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94],"testing","merge","start","access","session","ops","autonomy","releases","permission","full","runtime","scope","devex","hook","true","action","for","scoped",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":109,"publishedAt":39},"01M6XDQ1N21VE4KH98JWGZ7GN9","veracity-audit","Audit a data pipeline for Veracity and Value. Dispatches data-scientist, compliance-auditor, and data-engineer agents with project context injected at dispatch time. All source paths are supplied via flags — no defaults, no project assumptions. Subcommands: audit (full pipeline walk), score-check (scoring math only), gate-check (gate coverage only), source-trace \u003Clabel> (single source end-to-end). Invoke when: \"audit pipeline\", \"veracity check\", \"scoring math correct?\", \"check gates\", \"trace source\", \"verify quality gates\", \"formula correct?\".","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Fveracity-audit\u002FSKILL.md",[101,106],{"categoryNo":102,"categoryName":103,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":107,"categoryName":108,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000037","律师与法务",[110,111,77,112,113,114,30,115,116,117,118,119,120,121,122,123,124,125,126,127],"audit","veracity audit","review","data pipeline","pipeline","math","coverage","only","engineer","formula","scoring","time","project","worker","end","at","invoke","when",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":39},"01M6XDPVDKBR376C06CEK9BC5S","validate-spec","Audit an already-implemented spec against the codebase. Walks each constraint (ARCH-N, PERF-N, KD-N, etc.) and acceptance criterion, grounds findings in file:line evidence, runs the spec.json acceptance_commands, and writes a single audit doc to docs\u002Faudits\u002F. Use whenever the user asks to \"validate a spec\", \"audit a spec\", \"check if spec is implemented\", \"verify the spec is done\", \"is this spec really done\", or otherwise wants closure on spec-driven work. Read-only against the spec — produces an audit, never modifies the spec itself.","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Fvalidate-spec\u002FSKILL.md",[],[135,136,137,77,112,138,139,110,30,33,34,140,117,141,142,143,144,145,146,147],"spec","validate","validate spec","run","acceptance","never","max","done","arch","line","2025","spec-driven","closure",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":157,"publishedAt":39},"01M6XDPMMECH82RAW553Y94HDS","terragrunt-specialist","Deep-dive Terragrunt hierarchy review, DRY pattern audits, and run-all orchestration analysis. Use for structured investigations of multi-environment Terragrunt layouts, dependency graphs, remote state config, and hook correctness. Triggers on: \"Terragrunt audit\", \"run-all review\", \"dependency block\", \"DRY pattern review\", \"env hierarchy audit\", \"mock_outputs\", \"terragrunt hooks\".","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Fterragrunt-specialist\u002FSKILL.md",[154],{"categoryNo":155,"categoryName":156,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000011","运维与部署",[158,159,160,112,161,162,138,110,28,30,34,163,164,141,165,166,145,167,125,168],"terragrunt","specialist","terragrunt specialist","orchestration","debugging","dependency","hooks","deep","dry","remote","hierarchy",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":182,"publishedAt":39},"01M6XDPFJS2HGSE13RXF1HV8S7","terraform-specialist","Deep-dive Terraform architecture review, module design, state management, and migration. Use for structured investigations of Terraform workspaces, provider configuration, module coupling, import workflows, and test coverage. Triggers on: \"Terraform audit\", \"module review\", \"state management\", \"Terraform import\", \"workspace design\", \"provider config review\", \"Terraform testing\".","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Fterraform-specialist\u002FSKILL.md",[175,178,179],{"categoryNo":176,"categoryName":177,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":155,"categoryName":156,"taxonomyType":104,"taxonomyTypeDesc":105},{"categoryNo":180,"categoryName":181,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000015","视觉设计",[183,184,159,77,185,112,186,187,188,162,110,30,34,116,189,190,165,191,145,125],"terraform","terraform specialist","design","workflows","architecture","architecture review","test coverage","workspaces","problem",{"skillNo":193,"name":135,"nameZh":6,"description":194,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":195,"categories":196,"keywords":201,"publishedAt":39},"01M6XDP7V6H8WYPSXVEKYE6HJ6","Create structured engineering specs through interactive pairing. Use when the user wants to create a spec, design doc, technical specification, architecture document, RFC, or engineering plan. Triggers on \"let's spec this out\", \"create a spec\", \"design doc\", \"write a technical plan\", \"plan the architecture\". Works for greenfield and brownfield projects. Outputs to docs\u002Fspecs\u002F.","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Fspec\u002FSKILL.md",[197,198],{"categoryNo":180,"categoryName":181,"taxonomyType":104,"taxonomyTypeDesc":105},{"categoryNo":199,"categoryName":200,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000032","设计师",[135,185,202,187,203,204,205,206,207,208,209,210,37,211,212,93,213,214,215,216],"component","create","plan","projects","write","interactive","use","document","specification","opus","technical specification","trade-offs","technical plan","outputs","frontier"]