[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XD9QNT73966AYDK2F61TYT":3,"skill-same:01M6XD9QNT73966AYDK2F61TYT":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":18,"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},"01M6XD9QNT73966AYDK2F61TYT","create-experiment",null,"Run a scoped, local-only experiment and save the report to docs\u002Fexperiments\u002F. Triggers on: \"let's try\", \"compare A vs B\", \"prototype\", \"explore\".","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-experiment\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"create experiment","create","experiment","grep","scoped","compare","triggers","local","only","write","read","docs","explore","Bash","save","hypothesis","report","run","experiments","prototype","2026-11-10 10:12:30",false,"---\n# dotbabel:generated projection=sha256:918ffead4639dae228bb3784f7a3a681b6c15c9e4a9d417f15ed462bb6781dc6 source=skills\u002Fcreate-experiment\u002FSKILL.md — do not edit directly\nallowed-tools: Read Grep Glob Bash Write\nargument-hint: \"[topic or hypothesis]\"\ndescription: |\n  Run a scoped, local-only experiment and save the report to docs\u002Fexperiments\u002F. Triggers on: \"let's try\", \"compare A vs B\", \"prototype\", \"explore\".\nname: create-experiment\n---\n\nRun a scoped, local-only experiment and produce a structured report saved to the project's `docs\u002Fexperiments\u002F` directory.\n\nTrigger: when the user asks \"let's try X\", \"I want to compare A vs B\", \"can we prototype Y\", \"explore Z before we commit\", or invokes `\u002Fcreate-experiment` directly. Use this skill **before** `\u002Fspec` (which is for design docs, not exploratory probes) and **after** plain shell tinkering becomes too messy to track.\n\nArguments: `$ARGUMENTS` — a topic or hypothesis (e.g. \"ripgrep vs grep on this repo\", \"switch from pnpm to bun\", \"does Postgres LISTEN\u002FNOTIFY scale to N clients\"). Required — if empty, ask the user what they want to explore.\n\n## Purpose\n\n`\u002Fcreate-experiment` is **not** a spec (no formal design), **not** an audit (it doesn't enumerate issues), **not** a fix (it doesn't ship anything). It is a **decision-grade probe**: refine a hypothesis, run it locally, capture results — including negative ones — and recommend a next move.\n\nThe output is a dated markdown file under `docs\u002Fexperiments\u002F` plus a sandbox directory containing the runnable artifacts. Both are left untracked for the user to review.\n\n## Steps\n\n### Step 0 — Refine the goal (interactive, blocking)\n\nIf `$ARGUMENTS` already covers hypothesis + observable success signal, echo the refined goal back as a paragraph + bulleted success criteria and **wait for user sign-off** before proceeding. Skip questions already answered in `$ARGUMENTS` or recent context.\n\nOtherwise, ask up to 4 short questions:\n\n1. **What are you trying to learn?** — one-sentence hypothesis.\n2. **What does \"it worked\" look like?** — concrete, observable signal (a benchmark number, a working prototype, a config that boots, a passing test).\n3. **What's out of scope?** — what should NOT be touched.\n4. **Time-box** — sketch (≤30 min), half-day (≤4 hr), or full-day (≤8 hr).\n\nEcho the refined goal back as a paragraph + bulleted success criteria. **Wait for explicit user sign-off before continuing.** Do not proceed to Step 1 until the user confirms.\n\n### Step 1 — Plan the experiment\n\n- Propose 1–3 approaches to try. Each is a distinct path to the same hypothesis.\n- For each approach, sketch: what gets installed, what runs, what's measured.\n- Pick the sandbox target:\n  - **Default:** a fresh git worktree at `.claude\u002Fworktrees\u002Fexperiment-\u003Cslug>\u002F` branched from the latest `origin\u002Fmain`. Run `git fetch origin main` first.\n  - **Fallback:** `~\u002Fexperiments\u002F\u003Cslug>\u002F` if there is no enclosing git repo.\n- Show this plan to the user and get a final go-ahead before touching the system.\n\n### Step 2 — Set up the environment\n\nExecute setup commands in the sandbox. **Capture every command and its output** as the reproducibility ledger — redact any tokens or credentials before including output in the report. Examples:\n\n- `git worktree add .claude\u002Fworktrees\u002Fexperiment-\u003Cslug> -b experiment\u002F\u003Cslug> origin\u002Fmain`\n- `npm i \u003Cpkg>` \u002F `pnpm add \u003Cpkg>` \u002F `bun add \u003Cpkg>`\n- `python -m venv .venv && source .venv\u002Fbin\u002Factivate && pip install -r requirements.txt`\n- `docker compose up -d`\n- `cargo new \u003Cname> && cd \u003Cname>`\n\nIf a setup step fails, document the failure, attempt **one** recovery (e.g. install a missing system dep), and proceed only if it succeeds. Do not silently swallow errors.\n\n### Step 3 — Execute the approaches\n\nApproaches are independent by default — execute concurrently when possible (parallel tool calls or background jobs with per-approach log files). Fall back to serial execution only when one approach depends on another's artifact.\n\nFor each approach:\n\n- Save code\u002Fconfig under `experiments\u002F\u003Cslug>\u002F\u003Capproach>\u002F` inside the sandbox.\n- Run the approach. For measurement commands and any failing command, capture full output — at minimum the last 10 lines.\n- Evaluate against the success criteria from Step 0. Record the result as **PASS**, **PARTIAL**, or **FAIL**.\n- If an approach surfaces a blocker that invalidates the hypothesis itself, stop and surface that to the user before continuing — they may want to refine the goal.\n\n### Step 4 — Compare & recommend\n\nBuild a comparison table that maps each approach against the agreed success criteria. Pick a recommendation, **or** explicitly say \"none of these — here's why and what to try next.\" A clean negative result is a complete experiment.\n\n### Step 5 — Write the report\n\nGenerate a filename: `\u003Ctopic-slug>-\u003CYYYY-MM-DD>.md` in lowercase kebab-case (e.g. `ripgrep-vs-grep-2026-04-29.md`). Create `docs\u002Fexperiments\u002F` if it doesn't exist. Use this structure:\n\n````markdown\n# Experiment: \u003CTopic> — \u003CYYYY-MM-DD>\n\n\u003COne-sentence hypothesis.>\n\n## Goal\n\n\u003C2–3 sentences. What we're learning and why this experiment was run now.>\n\n## Success Criteria\n\n- \u003Cobservable signal 1>\n- \u003Cobservable signal 2>\n\n## Environment Setup\n\nSandbox: `\u003Cabsolute path chosen in Step 1>`\n\n```bash\n\u003Cexact commands run, in order>\n```\n\n\u003Coutput snippets for any measurement or failing command — last 10 lines minimum>\n\n## Approaches Tried\n\n### Approach 1: \u003CName>\n\n- **Idea:** \u003Cone line>\n- **Code\u002Fconfig:** `\u003Cpath-in-sandbox>`\n- **Commands:**\n\n  ```bash\n  \u003Ccommands>\n  ```\n\n- **Result:** PASS | PARTIAL | FAIL — \u003Cobserved signal vs criterion>\n- **Notes:** \u003Cgotchas, surprises, dead-ends>\n\n\u003C!-- Add sections for each approach tried; omit if only one approach was attempted -->\n\n## Comparison\n\n| Approach | Result | \u003CCriterion 1> | \u003CCriterion 2> | Effort |\n| -------- | ------ | ------------- | ------------- | ------ |\n| ...      | ...    | ...           | ...           | ...    |\n\n## Recommendation\n\n**\u003CAdopt Approach N | Iterate further | Abandon>**\n\n\u003C2–3 sentences. Why this conclusion best matches the success criteria. Call out\nassumptions or unresolved questions.>\n\n## Next Step\n\n- Promote to `\u002Fspec \u003Ctopic>` to formalize the chosen approach, OR\n- Run `\u002Ffix-with-evidence \u003Ctopic>` to implement directly, OR\n- Run `\u002Freproduce-bug \u003Csymptom>` to capture a surprising failure as a failing regression test, OR\n- Re-run `\u002Fcreate-experiment` with a refined hypothesis, OR\n- Drop it — this document is the negative-result record.\n\n## Sandbox Cleanup\n\n```bash\ngit worktree remove .claude\u002Fworktrees\u002Fexperiment-\u003Cslug>   # or\nrm -rf ~\u002Fexperiments\u002F\u003Cslug>\n```\n````\n\n### Step 6 — Report back\n\nReply with: doc path, one-sentence recommendation, and sandbox path. **Do not paste the full document into chat.**\n\n## Rules\n\n- All work runs **locally**. No production endpoints, no cloud writes, no real auth tokens, no shared infrastructure. If the experiment needs an external service, mock it or use a disposable test account.\n- Environment setup is part of the experiment — every install\u002Fconfig\u002Fboot command must appear in the report. Reproducibility is the bar.\n- Capture failed approaches too. Negative results are valuable signal and **must** be in the report.\n- Do not commit the experiment doc or the sandbox. Leave both untracked for the user.\n- Do not install global tools (`apt`, `brew`, `npm i -g`) without explicit user approval during Step 1.\n- Tables and code blocks over prose. No filler.\n- An experiment is **done when success criteria are evaluated** — not when \"everything works.\" A clean failure is a finished experiment.\n","Run a scoped, local-only experiment and produce a structured report saved to the project's `docs\u002Fexperiments\u002F` directory.\n\nTrigger: when the user asks \"let's try X\", \"I want to compare A vs B\", \"can we prototype Y\", \"explore Z before we commit\", or invokes `\u002Fcreate-experiment` directly. Use this skill **before** `\u002Fspec` (which is for design docs, not exploratory probes) and **after** plain shell tinkering becomes too messy to track.\n\nArguments: `$ARGUMENTS` — a topic or hypothesis (e.g. \"ripgrep vs grep on this repo\", \"switch from pnpm to bun\", \"does Postgres LISTEN\u002FNOTIFY scale to N clients\"). Required — if empty, ask the user what they want to explore.\n\n## Purpose\n\n`\u002Fcreate-experiment` is **not** a spec (no formal design), **not** an audit (it doesn't enumerate issues), **not** a fix (it doesn't ship anything). It is a **decision-grade probe**: refine a hypothesis, run it locally, capture results — including negative ones — and recommend a next move.\n\nThe output is a dated markdown file under `docs\u002Fexperiments\u002F` plus a sandbox directory containing the runnable artifacts. Both are left untracked for the user to review.\n\n## Steps\n\n### Step 0 — Refine the goal (interactive, blocking)\n\nIf `$ARGUMENTS` already covers hypothesis + observable success signal, echo the refined goal back as a paragraph + bulleted success criteria and **wait for user sign-off** before proceeding. Skip questions already answered in `$ARGUMENTS` or recent context.\n\nOtherwise, ask up to 4 short questions:\n\n1. **What are you trying to learn?** — one-sentence hypothesis.\n2. **What does \"it worked\" look like?** — concrete, observable signal (a benchmark number, a working prototype, a config that boots, a passing test).\n3. **What's out of scope?** — what should NOT be touched.\n4. **Time-box** — sketch (≤30 min), half-day (≤4 hr), or full-day (≤8 hr).\n\nEcho the refined goal back as a paragraph + bulleted success criteria. **Wait for explicit user sign-off before continuing.** Do not proceed to Step 1 until the user confirms.\n\n### Step 1 — Plan the experiment\n\n- Propose 1–3 approaches to try. Each is a distinct path to the same hypothesis.\n- For each approach, sketch: what gets installed, what runs, what's measured.\n- Pick the sandbox target:\n  - **Default:** a fresh git worktree at `.claude\u002Fworktrees\u002Fexperiment-\u003Cslug>\u002F` branched from the latest `origin\u002Fmain`. Run `git fetch origin main` first.\n  - **Fallback:** `~\u002Fexperiments\u002F\u003Cslug>\u002F` if there is no enclosing git repo.\n- Show this plan to the user and get a final go-ahead before touching the system.\n\n### Step 2 — Set up the environment\n\nExecute setup commands in the sandbox. **Capture every command and its output** as the reproducibility ledger — redact any tokens or credentials before including output in the report. Examples:\n\n- `git worktree add .claude\u002Fworktrees\u002Fexperiment-\u003Cslug> -b experiment\u002F\u003Cslug> origin\u002Fmain`\n- `npm i \u003Cpkg>` \u002F `pnpm add \u003Cpkg>` \u002F `bun add \u003Cpkg>`\n- `python -m venv .venv && source .venv\u002Fbin\u002Factivate && pip install -r requirements.txt`\n- `docker compose up -d`\n- `cargo new \u003Cname> && cd \u003Cname>`\n\nIf a setup step fails, document the failure, attempt **one** recovery (e.g. install a missing system dep), and proceed only if it succeeds. Do not silently swallow errors.\n\n### Step 3 — Execute the approaches\n\nApproaches are independent by default — execute concurrently when possible (parallel tool calls or background jobs with per-approach log files). Fall back to serial execution only when one approach depends on another's artifact.\n\nFor each approach:\n\n- Save code\u002Fconfig under `experiments\u002F\u003Cslug>\u002F\u003Capproach>\u002F` inside the sandbox.\n- Run the approach. For measurement commands and any failing command, capture full output — at minimum the last 10 lines.\n- Evaluate against the success criteria from Step 0. Record the result as **PASS**, **PARTIAL**, or **FAIL**.\n- If an approach surfaces a blocker that invalidates the hypothesis itself, stop and surface that to the user before continuing — they may want to refine the goal.\n\n### Step 4 — Compare & recommend\n\nBuild a comparison table that maps each approach against the agreed success criteria. Pick a recommendation, **or** explicitly say \"none of these — here's why and what to try next.\" A clean negative result is a complete experiment.\n\n### Step 5 — Write the report\n\nGenerate a filename: `\u003Ctopic-slug>-\u003CYYYY-MM-DD>.md` in lowercase kebab-case (e.g. `ripgrep-vs-grep-2026-04-29.md`). Create `docs\u002Fexperiments\u002F` if it doesn't exist. Use this structure:\n\n````markdown\n# Experiment: \u003CTopic> — \u003CYYYY-MM-DD>\n\n\u003COne-sentence hypothesis.>\n\n## Goal\n\n\u003C2–3 sentences. What we're learning and why this experiment was run now.>\n\n## Success Criteria\n\n- \u003Cobservable signal 1>\n- \u003Cobservable signal 2>\n\n## Environment Setup\n\nSandbox: `\u003Cabsolute path chosen in Step 1>`\n\n```bash\n\u003Cexact commands run, in order>\n```\n\n\u003Coutput snippets for any measurement or failing command — last 10 lines minimum>\n\n## Approaches Tried\n\n### Approach 1: \u003CName>\n\n- **Idea:** \u003Cone line>\n- **Code\u002Fconfig:** `\u003Cpath-in-sandbox>`\n- **Commands:**\n\n  ```bash\n  \u003Ccommands>\n  ```\n\n- **Result:** PASS | PARTIAL | FAIL — \u003Cobserved signal vs criterion>\n- **Notes:** \u003Cgotchas, surprises, dead-ends>\n\n\u003C!-- Add sections for each approach tried; omit if only one approach was attempted -->\n\n## Comparison\n\n| Approach | Result | \u003CCriterion 1> | \u003CCriterion 2> | Effort |\n| -------- | ------ | ------------- | ------------- | ------ |\n| ...      | ...    | ...           | ...           | ...    |\n\n## Recommendation\n\n**\u003CAdopt Approach N | Iterate further | Abandon>**\n\n\u003C2–3 sentences. Why this conclusion best matches the success criteria. Call out\nassumptions or unresolved questions.>\n\n## Next Step\n\n- Promote to `\u002Fspec \u003Ctopic>` to formalize the chosen approach, OR\n- Run `\u002Ffix-with-evidence \u003Ctopic>` to implement directly, OR\n- Run `\u002Freproduce-bug \u003Csymptom>` to capture a surprising failure as a failing regression test, OR\n- Re-run `\u002Fcreate-experiment` with a refined hypothesis, OR\n- Drop it — this document is the negative-result record.\n\n## Sandbox Cleanup\n\n```bash\ngit worktree remove .claude\u002Fworktrees\u002Fexperiment-\u003Cslug>   # or\nrm -rf ~\u002Fexperiments\u002F\u003Cslug>\n```\n````\n\n### Step 6 — Report back\n\nReply with: doc path, one-sentence recommendation, and sandbox path. **Do not paste the full document into chat.**\n\n## Rules\n\n- All work runs **locally**. No production endpoints, no cloud writes, no real auth tokens, no shared infrastructure. If the experiment needs an external service, mock it or use a disposable test account.\n- Environment setup is part of the experiment — every install\u002Fconfig\u002Fboot command must appear in the report. Reproducibility is the bar.\n- Capture failed approaches too. Negative results are valuable signal and **must** be in the report.\n- Do not commit the experiment doc or the sandbox. Leave both untracked for the user.\n- Do not install global tools (`apt`, `brew`, `npm i -g`) without explicit user approval during Step 1.\n- Tables and code blocks over prose. No filler.\n- An experiment is **done when success criteria are evaluated** — not when \"everything works.\" A clean failure is a finished experiment.\n",{"name":5,"description":44,"allowed-tools":45,"argument-hint":46},"Run a scoped, local-only experiment and save the report to docs\u002Fexperiments\u002F. Triggers on: \"let's try\", \"compare A vs B\", \"prototype\", \"explore\".\n","Read Grep Glob Bash Write","[topic or hypothesis]","main","91c337164997b99943fbcc64e8e362577b67bc81","plugins\u002Fdotbabel\u002Ftemplates\u002Fclaude\u002Fskills\u002Fcreate-experiment","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 create-experiment",{"tool":60,"command":61},"bunx","bunx skills add kaiohenricunha\u002Fdotbabel --skill create-experiment",{"tool":63,"command":64},"pnpm","pnpm dlx skills add kaiohenricunha\u002Fdotbabel --skill create-experiment","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fplugins\u002Fdotbabel\u002Ftemplates\u002Fclaude\u002Fskills\u002Fcreate-experiment\u002FSKILL.md",true,[],[69,99,131,151,173,196],{"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":80,"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":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[71,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,23],"testing","merge","code","start","access","session","ops","autonomy","releases","permission","full","runtime","scope","devex","hook","true","action","for",{"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":113,"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",[105,110],{"categoryNo":106,"categoryName":107,"taxonomyType":108,"taxonomyTypeDesc":109},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":111,"categoryName":112,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000037","律师与法务",[114,115,81,116,117,118,32,119,120,27,121,122,123,124,125,126,127,128,129,130],"audit","veracity audit","review","data pipeline","pipeline","math","coverage","engineer","formula","scoring","time","project","worker","end","at","invoke","when",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"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",[],[138,139,140,81,116,36,141,114,32,142,29,143,27,144,145,146,147,148,149,150],"spec","validate","validate spec","acceptance","work","never","max","done","arch","line","2025","spec-driven","closure",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":160,"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",[157],{"categoryNo":158,"categoryName":159,"taxonomyType":108,"taxonomyTypeDesc":109},"01JBSEEDCAT000000000000011","运维与部署",[161,162,163,116,164,165,36,114,166,32,29,167,168,144,169,170,148,171,128,172],"terragrunt","specialist","terragrunt specialist","orchestration","debugging","analysis","dependency","hooks","deep","dry","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":186,"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",[179,182,183],{"categoryNo":180,"categoryName":181,"taxonomyType":108,"taxonomyTypeDesc":109},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":158,"categoryName":159,"taxonomyType":108,"taxonomyTypeDesc":109},{"categoryNo":184,"categoryName":185,"taxonomyType":108,"taxonomyTypeDesc":109},"01JBSEEDCAT000000000000015","视觉设计",[187,188,162,81,189,116,190,191,192,165,114,32,29,120,193,194,169,195,148,128],"terraform","terraform specialist","design","workflows","architecture","architecture review","test coverage","workspaces","problem",{"skillNo":197,"name":138,"nameZh":6,"description":198,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":199,"categories":200,"keywords":205,"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",[201,202],{"categoryNo":184,"categoryName":185,"taxonomyType":108,"taxonomyTypeDesc":109},{"categoryNo":203,"categoryName":204,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000032","设计师",[138,189,206,191,20,207,208,28,209,210,211,212,25,213,214,98,215,216,217,218],"component","plan","projects","interactive","use","document","specification","opus","technical specification","trade-offs","technical plan","outputs","frontier"]