[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XD7D3DT6A4MSQRERR5G0P8":3,"skill-same:01M6XD7D3DT6A4MSQRERR5G0P8":73},{"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":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":14,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":6,"ownerDescription":58,"updatedAt":59,"install":60,"resources":72},"01M6XD7D3DT6A4MSQRERR5G0P8","smoke-test",null,"Run the smoke checks a repository declares for its deploy targets and report whether production actually answers after a release. Use after a deploy, during release verification, and when confirming a rollback landed. Triggers on: \"smoke test\", \"run smoke checks\", \"is production healthy\", \"did the deploy work\", \"verify the release is live\".","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\u002Fexamples\u002Fminimal-consumer\u002F.claude\u002Fskills\u002Fsmoke-test\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"test","smoke test","smoke","when","for","true","targets","healthy","dry","triggers","live","use","read","work","Bash","verify","repository","verification","release","run","2026-11-10 10:12:30",false,"---\n# dotbabel:generated projection=sha256:591c53e174394358d68ef81c7317f081712ff692f3cff6eb585e7dda358bc898 source=skills\u002Fsmoke-test\u002FSKILL.md — do not edit directly\nallowed-tools: Read Grep Glob Bash\nargument-hint: \"[--dry-run] [--json]\"\ndescription: |\n  Run the smoke checks a repository declares for its deploy targets and report whether production actually answers after a release. Use after a deploy, during release verification, and when confirming a rollback landed. Triggers on: \"smoke test\", \"run smoke checks\", \"is production healthy\", \"did the deploy work\", \"verify the release is live\".\ndisable-model-invocation: true\nname: smoke-test\nuser-invocable: true\n---\n\n# Smoke Test\n\nRun the `smoke` checks declared per target in `.claude\u002Fdeploy-targets.json` and\nreport whether the deployed thing actually answers.\n\n`disable-model-invocation: true` is deliberate. These checks execute commands\nthe repository declares and send requests to production, so this skill runs\nwhen a person asks for it, not when a model infers it might be useful.\n\n## Workflow\n\n1. Resolve the helper script — the same two-step resolution `deploy-status`\n   uses, because it is the same helper and a skill that found only one of the\n   two locations would work for exactly one install shape:\n\n   ```bash\n   if [ -f \"$HOME\u002F.claude\u002Fskills\u002Fdeploy-status\u002Fscripts\u002Fdeploy-ops.mjs\" ]; then\n     DEPLOY_OPS=\"$HOME\u002F.claude\u002Fskills\u002Fdeploy-status\u002Fscripts\u002Fdeploy-ops.mjs\"\n   elif [ -f \"skills\u002Fdeploy-status\u002Fscripts\u002Fdeploy-ops.mjs\" ]; then\n     DEPLOY_OPS=\"skills\u002Fdeploy-status\u002Fscripts\u002Fdeploy-ops.mjs\"\n   else\n     echo \"deploy-status helper not found; re-run dotbabel bootstrap or dotbabel init\" >&2\n     exit 2\n   fi\n   ```\n\n2. Run the smoke command from the consuming project root, forwarding **only**\n   the flags this skill documents:\n\n   ```bash\n   node \"$DEPLOY_OPS\" smoke $ARGUMENTS\n   ```\n\n   `$ARGUMENTS` is raw caller text spliced into a command that reaches\n   production, so pass only `--dry-run` and `--json` — drop anything else\n   rather than forwarding it. A value carrying `;`, `|`, `&`, a backtick,\n   `$(`, or a newline is shell syntax, not a flag: refuse it and say so.\n\n3. Preserve the helper's exit code:\n   - `0` — every declared check passed, or none is declared, or it was a dry\n     run. None of those is a failure.\n   - `1` — at least one check failed, or the run hit its 300-second budget.\n   - `2` — target discovery failed.\n\n4. **Read `verdict`, not just the exit code.** The payload distinguishes four\n   states, and two of them exit 0 without having verified anything:\n\n   | `verdict`        | Meaning                                          |\n   | ---------------- | ------------------------------------------------ |\n   | `pass`           | Every declared check ran and passed              |\n   | `fail`           | At least one check failed, or the budget was hit |\n   | `not_configured` | No target declares `smoke` — nothing was checked |\n   | `not_run`        | `--dry-run`; checks were listed, none executed   |\n\n   Report `not_configured` and `not_run` as exactly that. Reporting either as a\n   pass claims a verification that did not happen.\n\n## On failure\n\nReport the failing checks and **recommend `\u002Frollback-prod`**. Then stop.\n\n**Never invoke `\u002Frollback-prod`, and never run the rollback helper directly.**\nRolling back is a production change, and both the rule floor and KD-13 require\nan explicit human instruction for one. `\u002Frollback-prod` additionally demands a\ntyped confirmation of its own, which exists precisely so that a chain of\nautomated judgments cannot end in an unattended production change.\n\nRecommend it, name the failing checks, and let the person decide.\n\n## What the checks are\n\nDeclared per target in `.claude\u002Fdeploy-targets.json`; see\n`skills\u002Fdeploy-status\u002FSKILL.md` for the full schema and the security guards.\nIn short: `http` checks are GET only, retry 3 times with 2s\u002F4s\u002F8s backoff, and\nabort after 10 seconds; `command` checks run their `argv` exactly once, because\na command may not be idempotent.\n\nSecrets are read only from named environment variables, and header values never\nappear in the output. If a check needs a token, export it before invoking:\n\n```bash\nSMOKE_BEARER=… \u002Fsmoke-test\n```\n\n## Rules\n\n- **Never roll back.** Recommend `\u002Frollback-prod` and stop.\n- **Never deploy or promote.** This skill only observes.\n- **Never invent a smoke check.** If a target declares none, report\n  `not_configured` rather than guessing at a health endpoint.\n- **Never report a dry run as a pass.** `--dry-run` lists what would run and\n  verifies nothing; its verdict is `not_run`.\n- **Never print a header value.** The helper redacts them; do not echo the\n  environment variable it read them from either.\n","# Smoke Test\n\nRun the `smoke` checks declared per target in `.claude\u002Fdeploy-targets.json` and\nreport whether the deployed thing actually answers.\n\n`disable-model-invocation: true` is deliberate. These checks execute commands\nthe repository declares and send requests to production, so this skill runs\nwhen a person asks for it, not when a model infers it might be useful.\n\n## Workflow\n\n1. Resolve the helper script — the same two-step resolution `deploy-status`\n   uses, because it is the same helper and a skill that found only one of the\n   two locations would work for exactly one install shape:\n\n   ```bash\n   if [ -f \"$HOME\u002F.claude\u002Fskills\u002Fdeploy-status\u002Fscripts\u002Fdeploy-ops.mjs\" ]; then\n     DEPLOY_OPS=\"$HOME\u002F.claude\u002Fskills\u002Fdeploy-status\u002Fscripts\u002Fdeploy-ops.mjs\"\n   elif [ -f \"skills\u002Fdeploy-status\u002Fscripts\u002Fdeploy-ops.mjs\" ]; then\n     DEPLOY_OPS=\"skills\u002Fdeploy-status\u002Fscripts\u002Fdeploy-ops.mjs\"\n   else\n     echo \"deploy-status helper not found; re-run dotbabel bootstrap or dotbabel init\" >&2\n     exit 2\n   fi\n   ```\n\n2. Run the smoke command from the consuming project root, forwarding **only**\n   the flags this skill documents:\n\n   ```bash\n   node \"$DEPLOY_OPS\" smoke $ARGUMENTS\n   ```\n\n   `$ARGUMENTS` is raw caller text spliced into a command that reaches\n   production, so pass only `--dry-run` and `--json` — drop anything else\n   rather than forwarding it. A value carrying `;`, `|`, `&`, a backtick,\n   `$(`, or a newline is shell syntax, not a flag: refuse it and say so.\n\n3. Preserve the helper's exit code:\n   - `0` — every declared check passed, or none is declared, or it was a dry\n     run. None of those is a failure.\n   - `1` — at least one check failed, or the run hit its 300-second budget.\n   - `2` — target discovery failed.\n\n4. **Read `verdict`, not just the exit code.** The payload distinguishes four\n   states, and two of them exit 0 without having verified anything:\n\n   | `verdict`        | Meaning                                          |\n   | ---------------- | ------------------------------------------------ |\n   | `pass`           | Every declared check ran and passed              |\n   | `fail`           | At least one check failed, or the budget was hit |\n   | `not_configured` | No target declares `smoke` — nothing was checked |\n   | `not_run`        | `--dry-run`; checks were listed, none executed   |\n\n   Report `not_configured` and `not_run` as exactly that. Reporting either as a\n   pass claims a verification that did not happen.\n\n## On failure\n\nReport the failing checks and **recommend `\u002Frollback-prod`**. Then stop.\n\n**Never invoke `\u002Frollback-prod`, and never run the rollback helper directly.**\nRolling back is a production change, and both the rule floor and KD-13 require\nan explicit human instruction for one. `\u002Frollback-prod` additionally demands a\ntyped confirmation of its own, which exists precisely so that a chain of\nautomated judgments cannot end in an unattended production change.\n\nRecommend it, name the failing checks, and let the person decide.\n\n## What the checks are\n\nDeclared per target in `.claude\u002Fdeploy-targets.json`; see\n`skills\u002Fdeploy-status\u002FSKILL.md` for the full schema and the security guards.\nIn short: `http` checks are GET only, retry 3 times with 2s\u002F4s\u002F8s backoff, and\nabort after 10 seconds; `command` checks run their `argv` exactly once, because\na command may not be idempotent.\n\nSecrets are read only from named environment variables, and header values never\nappear in the output. If a check needs a token, export it before invoking:\n\n```bash\nSMOKE_BEARER=… \u002Fsmoke-test\n```\n\n## Rules\n\n- **Never roll back.** Recommend `\u002Frollback-prod` and stop.\n- **Never deploy or promote.** This skill only observes.\n- **Never invent a smoke check.** If a target declares none, report\n  `not_configured` rather than guessing at a health endpoint.\n- **Never report a dry run as a pass.** `--dry-run` lists what would run and\n  verifies nothing; its verdict is `not_run`.\n- **Never print a header value.** The helper redacts them; do not echo the\n  environment variable it read them from either.\n",{"name":5,"description":49,"allowed-tools":50,"argument-hint":51,"user-invocable":52,"disable-model-invocation":52},"Run the smoke checks a repository declares for its deploy targets and report whether production actually answers after a release. Use after a deploy, during release verification, and when confirming a rollback landed. Triggers on: \"smoke test\", \"run smoke checks\", \"is production healthy\", \"did the deploy work\", \"verify the release is live\".\n","Read Grep Glob Bash","[--dry-run] [--json]",true,"main","91c337164997b99943fbcc64e8e362577b67bc81","examples\u002Fminimal-consumer\u002F.claude\u002Fskills\u002Fsmoke-test","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":61,"prompt":71,"zipAvailable":52},[62,65,68],{"tool":63,"command":64},"npx","npx skills add kaiohenricunha\u002Fdotbabel --skill smoke-test",{"tool":66,"command":67},"bunx","bunx skills add kaiohenricunha\u002Fdotbabel --skill smoke-test",{"tool":69,"command":70},"pnpm","pnpm dlx skills add kaiohenricunha\u002Fdotbabel --skill smoke-test","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fexamples\u002Fminimal-consumer\u002F.claude\u002Fskills\u002Fsmoke-test\u002FSKILL.md",[],[74,103,133,152,173,194],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":85,"publishedAt":44},"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",[80],{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[76,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,29,101,28,102],"testing","merge","code","start","access","session","ops","autonomy","releases","permission","full","runtime","scope","devex","hook","action","scoped",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":115,"publishedAt":44},"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",[109,112],{"categoryNo":110,"categoryName":111,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":113,"categoryName":114,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000037","律师与法务",[116,117,86,118,119,120,38,121,122,123,124,125,126,127,128,129,130,131,132,27],"audit","veracity audit","review","data pipeline","pipeline","math","coverage","only","engineer","formula","scoring","time","project","worker","end","at","invoke",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":44},"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",[],[140,141,142,86,118,43,143,116,38,37,36,144,123,145,146,147,148,149,150,151],"spec","validate","validate spec","acceptance","never","max","done","arch","line","2025","spec-driven","closure",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":161,"publishedAt":44},"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",[158],{"categoryNo":159,"categoryName":160,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",[162,163,164,118,165,166,43,116,167,38,36,168,169,145,170,32,149,171,131,172],"terragrunt","specialist","terragrunt specialist","orchestration","debugging","analysis","dependency","hooks","deep","remote","hierarchy",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":184,"publishedAt":44},"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",[179,180,181],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":159,"categoryName":160,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":182,"categoryName":183,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",[185,186,163,86,187,118,188,189,190,166,116,38,36,122,191,192,170,193,149,131],"terraform","terraform specialist","design","workflows","architecture","architecture review","test coverage","workspaces","problem",{"skillNo":195,"name":140,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":197,"categories":198,"keywords":203,"publishedAt":44},"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",[199,200],{"categoryNo":182,"categoryName":183,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":201,"categoryName":202,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000032","设计师",[140,187,204,189,205,206,207,208,209,35,210,211,33,212,213,28,214,215,216,217],"component","create","plan","projects","write","interactive","document","specification","opus","technical specification","trade-offs","technical plan","outputs","frontier"]