[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XDGTZVNFK3B8XEVRVB9K34":3,"skill-same:01M6XDGTZVNFK3B8XEVRVB9K34":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":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":63,"commitSha":64,"skillDirectory":65,"forksCount":14,"repositoryHtmlUrl":66,"repositoryHomepageUrl":6,"ownerHtmlUrl":67,"ownerBlogUrl":6,"ownerDescription":68,"updatedAt":69,"install":70,"resources":83},"01M6XDGTZVNFK3B8XEVRVB9K34","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\u002Fskills\u002Fcreate-audit\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"create audit","create","audit","write","at","opus","2025","devex","triggers","deep","wed","evidence","review","read","technical","Bash","save","Evaluation","assessment","documentation","2026-11-10 10:12:30",false,"---\nid: create-audit\nname: create-audit\ntype: skill\nversion: 1.0.0\ndomain:\n  - devex\nplatform:\n  - none\ntask:\n  - review\n  - documentation\nmaturity: validated\nowner: \"@kaiohenricunha\"\ncreated: 2025-01-01T00:00:00.000Z\nupdated: 2026-04-17T00:00:00.000Z\ndescription: |\n  Create an evidence-based audit document and save it to docs\u002Faudits\u002F. Triggers on: \"audit\", \"review\", \"assessment\".\nargument-hint: \"[subject]\"\ntools: Read, Grep, Glob, Bash, Write\nallowed-tools: Read Grep Glob Bash Write\nmodel: opus\ndotbabel:\n  compute:\n    mode: dynamic\n    requirement: deep\n    binding: consumer\n    rationale: Evidence-based investigation or evaluation must hold several technical constraints at once.\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",{"id":5,"name":5,"task":44,"type":45,"model":24,"owner":46,"tools":47,"domain":48,"created":49,"updated":50,"version":51,"dotbabel":52,"maturity":57,"platform":58,"description":60,"allowed-tools":61,"argument-hint":62},[31,38],"skill","@kaiohenricunha","Read, Grep, Glob, Bash, Write",[26],1735689600000,1776384000000,"1.0.0",{"compute":53},{"mode":54,"binding":55,"rationale":56,"requirement":28},"dynamic","consumer","Evidence-based investigation or evaluation must hold several technical constraints at once.","validated",[59],"none","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","skills\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":71,"prompt":81,"zipAvailable":82},[72,75,78],{"tool":73,"command":74},"npx","npx skills add kaiohenricunha\u002Fdotbabel --skill create-audit",{"tool":76,"command":77},"bunx","bunx skills add kaiohenricunha\u002Fdotbabel --skill create-audit",{"tool":79,"command":80},"pnpm","pnpm dlx skills add kaiohenricunha\u002Fdotbabel --skill create-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Fcreate-audit\u002FSKILL.md",true,[],[85,115,145,165,186,209],{"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":96,"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",[91],{"categoryNo":92,"categoryName":93,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[87,97,98,99,100,101,102,103,104,105,106,107,108,109,26,110,111,112,113,114],"testing","merge","code","start","access","session","ops","autonomy","releases","permission","full","runtime","scope","hook","true","action","for","scoped",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":129,"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",[121,126],{"categoryNo":122,"categoryName":123,"taxonomyType":124,"taxonomyTypeDesc":125},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":127,"categoryName":128,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000037","律师与法务",[21,130,97,31,131,132,34,133,134,135,136,137,138,139,140,141,142,23,143,144],"veracity audit","data pipeline","pipeline","math","coverage","only","engineer","formula","scoring","time","project","worker","end","invoke","when",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":151,"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",[],[152,153,154,97,31,155,156,21,34,157,32,158,135,159,160,161,162,25,163,164],"spec","validate","validate spec","run","acceptance","work","never","max","done","arch","line","spec-driven","closure",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":174,"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",[171],{"categoryNo":172,"categoryName":173,"taxonomyType":124,"taxonomyTypeDesc":125},"01JBSEEDCAT000000000000011","运维与部署",[175,176,177,31,178,179,155,21,180,34,32,181,182,159,28,183,25,184,23,185],"terragrunt","specialist","terragrunt specialist","orchestration","debugging","analysis","dependency","hooks","dry","remote","hierarchy",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":199,"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",[192,195,196],{"categoryNo":193,"categoryName":194,"taxonomyType":124,"taxonomyTypeDesc":125},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":172,"categoryName":173,"taxonomyType":124,"taxonomyTypeDesc":125},{"categoryNo":197,"categoryName":198,"taxonomyType":124,"taxonomyTypeDesc":125},"01JBSEEDCAT000000000000015","视觉设计",[200,201,176,97,202,31,203,204,205,179,21,34,32,134,206,207,28,208,25,23],"terraform","terraform specialist","design","workflows","architecture","architecture review","test coverage","workspaces","problem",{"skillNo":210,"name":152,"nameZh":6,"description":211,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":212,"categories":213,"keywords":218,"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",[214,215],{"categoryNo":197,"categoryName":198,"taxonomyType":124,"taxonomyTypeDesc":125},{"categoryNo":216,"categoryName":217,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000032","设计师",[152,202,219,204,20,220,221,22,222,223,224,225,27,24,226,113,227,228,229,230],"component","plan","projects","interactive","use","document","specification","technical specification","trade-offs","technical plan","outputs","frontier"]