[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XD9K9MVBJ0Z73485MQ42NW":3,"skill-same:01M6XD9K9MVBJ0Z73485MQ42NW":64},{"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":18,"publishedAt":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":14,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M6XD9K9MVBJ0Z73485MQ42NW","create-audit",null,"Create an evidence-based audit document and save it to docs\u002Faudits\u002F. Triggers on: \"audit\", \"review\", \"assessment\".","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\u002Fcreate-audit\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"create","audit","create audit","review","docs","assessment","save","Bash","grep","read","write","evidence","document","triggers","it","evidence-based","2026-11-10 10:12:30",false,"---\n# dotbabel:generated projection=sha256:89c252c8040dacb34efaacbd0360a9c10a54e18bf540ea05fadf559a6de63463 source=skills\u002Fcreate-audit\u002FSKILL.md — do not edit directly\nallowed-tools: Read Grep Glob Bash Write\nargument-hint: \"[subject]\"\ndescription: |\n  Create an evidence-based audit document and save it to docs\u002Faudits\u002F. Triggers on: \"audit\", \"review\", \"assessment\".\nname: create-audit\n---\n\nCreate a structured audit document and save it to the project's `docs\u002Faudits\u002F` directory.\n\nTrigger: when the user asks for an audit, review, or assessment of any system, feature, data quality, process, or component. Also triggered directly via `\u002Fcreate-audit`.\n\nArguments: `$ARGUMENTS` — a description of what to audit (e.g. \"data quality for user profiles\", \"API endpoint security\", \"deployment pipeline reliability\").\n\n## Steps\n\n1. **Parse the audit subject** from `$ARGUMENTS`. If empty or vague, infer the subject from recent conversation context. If still unclear, ask the user what they want audited.\n\n2. **Investigate the subject thoroughly.** Read relevant source files, configs, logs, test results, git history, and any external state (API responses, deployment status) needed to form an evidence-based assessment. Do not guess — verify.\n\n3. **Generate the audit document** with this structure:\n\n   ```markdown\n   # \u003CAudit Title> — \u003CYYYY-MM-DD>\n\n   \u003COne-line summary of what was audited and why.>\n\n   ## Scope\n\n   What was included and excluded from this audit.\n\n   ## Findings\n\n   ### \u003CFinding Category 1>\n\n   | Item | Status | Details |\n   | ---- | ------ | ------- |\n   | ...  | ...    | ...     |\n\n   \u003CNarrative explanation of the findings with evidence (file paths, line numbers, metrics, command output).>\n\n   ### \u003CFinding Category 2>\n\n   ...\n\n   ## Issues\n\n   | Severity | Issue | Location | Recommendation |\n   | -------- | ----- | -------- | -------------- |\n   | CRITICAL | ...   | ...      | ...            |\n   | WARNING  | ...   | ...      | ...            |\n   | INFO     | ...   | ...      | ...            |\n\n   If no issues: \"No issues found.\"\n\n   ## Summary\n\n   \u003C2-3 sentence verdict. What's healthy, what needs attention, what's the recommended next action.>\n   ```\n\n4. **Generate a filename** in the format: `\u003Ctopic-slug>-\u003CYYYY-MM-DD>.md` (e.g. `data-quality-2026-04-05.md`, `api-security-2026-04-09.md`). Use lowercase kebab-case.\n\n5. **Write the file** to `docs\u002Faudits\u002F\u003Cfilename>`. Create the `docs\u002Faudits\u002F` directory if it doesn't exist.\n\n6. **Report to the user**: show the file path and a brief summary of findings (critical\u002Fwarning\u002Finfo counts). Do not dump the full document into chat. To turn a specific CRITICAL\u002FWARNING finding into an isolated reproduction with a failing test, hand it to `\u002Freproduce-bug \u003Cfinding>`.\n\n## Rules\n\n- Every claim in the audit must be backed by evidence (a file read, command output, metric, or test result). No assumptions.\n- Severity levels: **CRITICAL** = broken or actively harmful, **WARNING** = degraded or risky, **INFO** = improvement opportunity.\n- Do not fix issues found. Report them. The user decides what to act on.\n- Do not commit the audit file. Leave it as an untracked file for the user to review.\n- Keep the document concise. Tables over prose where possible. No filler.\n","Create a structured audit document and save it to the project's `docs\u002Faudits\u002F` directory.\n\nTrigger: when the user asks for an audit, review, or assessment of any system, feature, data quality, process, or component. Also triggered directly via `\u002Fcreate-audit`.\n\nArguments: `$ARGUMENTS` — a description of what to audit (e.g. \"data quality for user profiles\", \"API endpoint security\", \"deployment pipeline reliability\").\n\n## Steps\n\n1. **Parse the audit subject** from `$ARGUMENTS`. If empty or vague, infer the subject from recent conversation context. If still unclear, ask the user what they want audited.\n\n2. **Investigate the subject thoroughly.** Read relevant source files, configs, logs, test results, git history, and any external state (API responses, deployment status) needed to form an evidence-based assessment. Do not guess — verify.\n\n3. **Generate the audit document** with this structure:\n\n   ```markdown\n   # \u003CAudit Title> — \u003CYYYY-MM-DD>\n\n   \u003COne-line summary of what was audited and why.>\n\n   ## Scope\n\n   What was included and excluded from this audit.\n\n   ## Findings\n\n   ### \u003CFinding Category 1>\n\n   | Item | Status | Details |\n   | ---- | ------ | ------- |\n   | ...  | ...    | ...     |\n\n   \u003CNarrative explanation of the findings with evidence (file paths, line numbers, metrics, command output).>\n\n   ### \u003CFinding Category 2>\n\n   ...\n\n   ## Issues\n\n   | Severity | Issue | Location | Recommendation |\n   | -------- | ----- | -------- | -------------- |\n   | CRITICAL | ...   | ...      | ...            |\n   | WARNING  | ...   | ...      | ...            |\n   | INFO     | ...   | ...      | ...            |\n\n   If no issues: \"No issues found.\"\n\n   ## Summary\n\n   \u003C2-3 sentence verdict. What's healthy, what needs attention, what's the recommended next action.>\n   ```\n\n4. **Generate a filename** in the format: `\u003Ctopic-slug>-\u003CYYYY-MM-DD>.md` (e.g. `data-quality-2026-04-05.md`, `api-security-2026-04-09.md`). Use lowercase kebab-case.\n\n5. **Write the file** to `docs\u002Faudits\u002F\u003Cfilename>`. Create the `docs\u002Faudits\u002F` directory if it doesn't exist.\n\n6. **Report to the user**: show the file path and a brief summary of findings (critical\u002Fwarning\u002Finfo counts). Do not dump the full document into chat. To turn a specific CRITICAL\u002FWARNING finding into an isolated reproduction with a failing test, hand it to `\u002Freproduce-bug \u003Cfinding>`.\n\n## Rules\n\n- Every claim in the audit must be backed by evidence (a file read, command output, metric, or test result). No assumptions.\n- Severity levels: **CRITICAL** = broken or actively harmful, **WARNING** = degraded or risky, **INFO** = improvement opportunity.\n- Do not fix issues found. Report them. The user decides what to act on.\n- Do not commit the audit file. Leave it as an untracked file for the user to review.\n- Keep the document concise. Tables over prose where possible. No filler.\n",{"name":5,"description":40,"allowed-tools":41,"argument-hint":42},"Create an evidence-based audit document and save it to docs\u002Faudits\u002F. Triggers on: \"audit\", \"review\", \"assessment\".\n","Read Grep Glob Bash Write","[subject]","main","91c337164997b99943fbcc64e8e362577b67bc81","plugins\u002Fdotbabel\u002Ftemplates\u002Fclaude\u002Fskills\u002Fcreate-audit","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":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add kaiohenricunha\u002Fdotbabel --skill create-audit",{"tool":56,"command":57},"bunx","bunx skills add kaiohenricunha\u002Fdotbabel --skill create-audit",{"tool":59,"command":60},"pnpm","pnpm dlx skills add kaiohenricunha\u002Fdotbabel --skill create-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fplugins\u002Fdotbabel\u002Ftemplates\u002Fclaude\u002Fskills\u002Fcreate-audit\u002FSKILL.md",true,[],[65,96,127,148,170,193],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":76,"publishedAt":35},"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",[71],{"categoryNo":72,"categoryName":73,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[67,77,78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95],"testing","merge","code","start","access","session","ops","autonomy","releases","permission","full","runtime","scope","devex","hook","true","action","for","scoped",{"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":110,"publishedAt":35},"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",[102,107],{"categoryNo":103,"categoryName":104,"taxonomyType":105,"taxonomyTypeDesc":106},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":108,"categoryName":109,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000037","律师与法务",[20,111,77,22,112,113,26,114,115,116,117,118,119,120,121,122,123,124,125,126],"veracity audit","data pipeline","pipeline","math","coverage","only","engineer","formula","scoring","time","project","worker","end","at","invoke","when",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":35},"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",[],[134,135,136,77,22,137,138,20,26,139,28,140,116,141,142,143,144,145,146,147],"spec","validate","validate spec","run","acceptance","work","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":35},"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":105,"taxonomyTypeDesc":106},"01JBSEEDCAT000000000000011","运维与部署",[158,159,160,22,161,162,137,20,163,26,28,164,165,141,166,167,145,168,124,169],"terragrunt","specialist","terragrunt specialist","orchestration","debugging","analysis","dependency","hooks","deep","dry","remote","hierarchy",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":183,"publishedAt":35},"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",[176,179,180],{"categoryNo":177,"categoryName":178,"taxonomyType":105,"taxonomyTypeDesc":106},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":155,"categoryName":156,"taxonomyType":105,"taxonomyTypeDesc":106},{"categoryNo":181,"categoryName":182,"taxonomyType":105,"taxonomyTypeDesc":106},"01JBSEEDCAT000000000000015","视觉设计",[184,185,159,77,186,22,187,188,189,162,20,26,28,115,190,191,166,192,145,124],"terraform","terraform specialist","design","workflows","architecture","architecture review","test coverage","workspaces","problem",{"skillNo":194,"name":134,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":196,"categories":197,"keywords":202,"publishedAt":35},"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",[198,199],{"categoryNo":181,"categoryName":182,"taxonomyType":105,"taxonomyTypeDesc":106},{"categoryNo":200,"categoryName":201,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000032","设计师",[134,186,203,188,19,204,205,29,206,207,31,208,32,209,210,94,211,212,213,214],"component","plan","projects","interactive","use","specification","opus","technical specification","trade-offs","technical plan","outputs","frontier"]