[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XD1VMX09QCYC1XFW4MY2NN":3,"skill-same:01M6XD1VMX09QCYC1XFW4MY2NN":67},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":14,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":6,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M6XD1VMX09QCYC1XFW4MY2NN","create-assessment",null,"Create a structured assessment document grading a target on a 0-10 scale with a weighted rubric, saved to docs\u002Fassessments\u002F. Triggers on: \"grade\", \"rate\", \"score\", \"evaluate\", \"assess\".","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\u002Fcreate-assessment\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"assessment","create assessment","create","structured","docs","rate","evaluate","saved","with","assess","scale","triggers","grading","document","rubric","write","read","grep","Bash","2026-11-10 10:12:30",false,"---\n# dotbabel:generated projection=sha256:494b96fd2513ca486345857ea97f42b32f0daf89ce6662012f5cc172f6738510 source=skills\u002Fcreate-assessment\u002FSKILL.md — do not edit directly\nallowed-tools: Read Grep Glob Bash Write\nargument-hint: \"[target]\"\ndescription: |\n  Create a structured assessment document grading a target on a 0-10 scale with a weighted rubric, saved to docs\u002Fassessments\u002F. Triggers on: \"grade\", \"rate\", \"score\", \"evaluate\", \"assess\".\nname: create-assessment\n---\n\nCreate a structured assessment document that grades a target on a 0-10 scale using a weighted rubric and save it to the project's `docs\u002Fassessments\u002F` directory.\n\nTrigger: when the user asks to grade, rate, score, evaluate, or assess a specific target — a package, a project\u002Frepo, a source file, an architecture decision, a pull request, or a document. Also triggered directly via `\u002Fcreate-assessment`. This skill is about **producing a numeric grade**, not listing issues — for issue-triage with severity levels use `\u002Fcreate-audit`.\n\nArguments: `$ARGUMENTS` — a description of what to assess (e.g. \"the ingest pipeline package\", \"src\u002FApp.jsx\", \"the decision to self-host Fly Postgres\", \"PR #412\", \"docs\u002Fspecs\u002Flocal-dev.md\"). The user may also append `using dimensions: \u003Cname> \u003Cweight>, \u003Cname> \u003Cweight>, ...` to override the default rubric.\n\n## Steps\n\n1. **Parse the target** from `$ARGUMENTS`. If empty or vague, infer from recent conversation. If still unclear, ask the user what to assess and which dimensions matter most.\n\n2. **Classify the target** into exactly one type: `package` | `project` | `source-file` | `architecture-decision` | `pull-request` | `document` | `other`. State the classification explicitly in the output doc.\n\n3. **Select the rubric.** If the user provided dimensions+weights in `$ARGUMENTS`, use those verbatim. Otherwise use the built-in rubric for the classified type (see Rubrics below). For `other`, pick the closest rubric and note the adaptation.\n\n4. **Investigate each dimension.** Read relevant source files, configs, tests, CI logs, git history, external state (deployment status, dependency advisories, benchmarks) as needed. Every score must be backed by evidence: `file:line`, command output, metric, test result, or a specific historical event. Do not guess. If you cannot gather evidence for a dimension, score it 0 and explain why in the Evidence column.\n\n5. **Score each dimension 0-10** against the grade bands below. Compute the overall grade as `Σ(weight × score)`, rounded to 1 decimal.\n\n6. **Generate the assessment document** using the structure below.\n\n7. **Generate a filename** in the format: `\u003Ctarget-slug>-\u003CYYYY-MM-DD>.md`. Use lowercase kebab-case. If the target is a file path, slug is the basename without extension (`src\u002FApp.jsx` → `app-jsx`). If it's a PR, use `pr-\u003CN>`. If it's a decision, use a short kebab phrase.\n\n8. **Write the file** to `docs\u002Fassessments\u002F\u003Cfilename>`. Create the `docs\u002Fassessments\u002F` directory if it doesn't exist.\n\n9. **Report to the user**: show the file path, the overall grade and its band, and the top 1-2 highest-leverage improvements. Do not dump the full document into chat.\n\n## Grade bands\n\n| Grade    | Band      | Meaning                                      |\n| -------- | --------- | -------------------------------------------- |\n| 9.0-10.0 | Excellent | Ship\u002Fadopt without reservation               |\n| 7.0-8.9  | Solid     | Production-ready; minor polish               |\n| 5.0-6.9  | Passable  | Usable but has real gaps; fix before scaling |\n| 3.0-4.9  | Weak      | Significant problems; rework advised         |\n| 0.0-2.9  | Broken    | Do not ship\u002Fadopt                            |\n\n## Rubrics by target type\n\nWeights within each rubric sum to 1.00.\n\n### package\n\n| Dimension                                                          | Weight |\n| ------------------------------------------------------------------ | -----: |\n| Correctness (tests pass, matches spec)                             |   0.25 |\n| API design & ergonomics                                            |   0.15 |\n| Test coverage & quality                                            |   0.20 |\n| Documentation (README, examples, API docs)                         |   0.10 |\n| Maintenance signals (release cadence, open issues, responsiveness) |   0.10 |\n| Security & dependency health                                       |   0.20 |\n\n### project\n\n| Dimension                                   | Weight |\n| ------------------------------------------- | -----: |\n| Architecture clarity (boundaries, layering) |   0.20 |\n| Code quality & consistency                  |   0.15 |\n| Test coverage                               |   0.15 |\n| CI\u002FCD & automation                          |   0.10 |\n| Documentation (CLAUDE.md, README, runbooks) |   0.10 |\n| Security posture                            |   0.15 |\n| Observability (logs, metrics, alerting)     |   0.15 |\n\n### source-file\n\n| Dimension                  | Weight |\n| -------------------------- | -----: |\n| Correctness                |   0.30 |\n| Readability                |   0.20 |\n| Testability                |   0.15 |\n| Coupling & cohesion        |   0.15 |\n| Performance considerations |   0.10 |\n| Security                   |   0.10 |\n\n### architecture-decision\n\n| Dimension                           | Weight |\n| ----------------------------------- | -----: |\n| Problem framing                     |   0.20 |\n| Solution fit                        |   0.25 |\n| Alternatives considered             |   0.15 |\n| Trade-offs made explicit            |   0.15 |\n| Reversibility \u002F migration path      |   0.15 |\n| Operational impact (cost, ops load) |   0.10 |\n\n### pull-request\n\n| Dimension                            | Weight |\n| ------------------------------------ | -----: |\n| Scope focus (one thing, well-scoped) |   0.15 |\n| Diff clarity                         |   0.15 |\n| Test coverage of the change          |   0.25 |\n| Risk & rollback plan                 |   0.20 |\n| PR body quality (context, test plan) |   0.10 |\n| CI signal                            |   0.15 |\n\n### document\n\n| Dimension                                    | Weight |\n| -------------------------------------------- | -----: |\n| Clarity                                      |   0.25 |\n| Completeness                                 |   0.25 |\n| Evidence \u002F citations                         |   0.15 |\n| Actionability                                |   0.20 |\n| Maintenance hooks (owner, dates, versioning) |   0.15 |\n\n## Document structure\n\n```markdown\n# \u003CTarget Title> — Assessment — \u003CYYYY-MM-DD>\n\n\u003COne-line summary of what was assessed and why.>\n\n**Target type:** \u003Ctype>\n**Overall grade: X.X \u002F 10 — \u003CBand>**\n\n## Scope\n\nWhat was included and excluded from this assessment, and which rubric was applied (built-in for `\u003Ctype>`, or a user-provided custom rubric).\n\n## Rubric & scores\n\n| Dimension   |   Weight | Score | Weighted | Evidence               |\n| ----------- | -------: | ----: | -------: | ---------------------- |\n| ...         |     0.XX |  N\u002F10 |     N.NN | \u003Cfile:line, metric, …> |\n| **Overall** | **1.00** |     — |  **X.X** | —                      |\n\n## Dimension detail\n\n### \u003CDimension 1> — N\u002F10\n\nObservations with evidence. End with a short \"**To raise this score:**\" line listing concrete changes that would move the score up.\n\n### \u003CDimension 2> — N\u002F10\n\n...\n\n## Highest-leverage improvements\n\nRanked by estimated grade lift. Each item lists the action, the affected dimension(s), and the estimated lift.\n\n1. \u003CAction> — \u003Cdimension(s)> — estimated lift: +X.X\n2. \u003CAction> — \u003Cdimension(s)> — estimated lift: +X.X\n\n## Summary\n\n\u003C2-3 sentence verdict: overall grade in band context, the one dimension dragging the most, and the single recommended next action.>\n```\n\n## Rules\n\n- Every score must be backed by evidence in the Evidence column. No gut-feel numbers. If no evidence can be produced, score 0 and say so.\n- Use the built-in rubric weights exactly unless the user overrode them at invocation. Do not silently reweight.\n- Classify target type before scoring. State the type in the output doc.\n- Do not fix issues found. Report them in the Highest-leverage improvements section.\n- Do not commit the assessment file. Leave it untracked for the user to review.\n- Keep the document concise. Tables over prose where possible. No filler.\n- Round the overall grade to 1 decimal. Round weighted-column values to 2 decimals.\n- Never invent a target or expand scope beyond what was requested. If scope is unclear, ask.\n- If the user asks for a re-assessment of a previously graded target, read the prior file in `docs\u002Fassessments\u002F` and include a short \"Delta vs \u003Cprevious date>\" line under the overall grade.\n","Create a structured assessment document that grades a target on a 0-10 scale using a weighted rubric and save it to the project's `docs\u002Fassessments\u002F` directory.\n\nTrigger: when the user asks to grade, rate, score, evaluate, or assess a specific target — a package, a project\u002Frepo, a source file, an architecture decision, a pull request, or a document. Also triggered directly via `\u002Fcreate-assessment`. This skill is about **producing a numeric grade**, not listing issues — for issue-triage with severity levels use `\u002Fcreate-audit`.\n\nArguments: `$ARGUMENTS` — a description of what to assess (e.g. \"the ingest pipeline package\", \"src\u002FApp.jsx\", \"the decision to self-host Fly Postgres\", \"PR #412\", \"docs\u002Fspecs\u002Flocal-dev.md\"). The user may also append `using dimensions: \u003Cname> \u003Cweight>, \u003Cname> \u003Cweight>, ...` to override the default rubric.\n\n## Steps\n\n1. **Parse the target** from `$ARGUMENTS`. If empty or vague, infer from recent conversation. If still unclear, ask the user what to assess and which dimensions matter most.\n\n2. **Classify the target** into exactly one type: `package` | `project` | `source-file` | `architecture-decision` | `pull-request` | `document` | `other`. State the classification explicitly in the output doc.\n\n3. **Select the rubric.** If the user provided dimensions+weights in `$ARGUMENTS`, use those verbatim. Otherwise use the built-in rubric for the classified type (see Rubrics below). For `other`, pick the closest rubric and note the adaptation.\n\n4. **Investigate each dimension.** Read relevant source files, configs, tests, CI logs, git history, external state (deployment status, dependency advisories, benchmarks) as needed. Every score must be backed by evidence: `file:line`, command output, metric, test result, or a specific historical event. Do not guess. If you cannot gather evidence for a dimension, score it 0 and explain why in the Evidence column.\n\n5. **Score each dimension 0-10** against the grade bands below. Compute the overall grade as `Σ(weight × score)`, rounded to 1 decimal.\n\n6. **Generate the assessment document** using the structure below.\n\n7. **Generate a filename** in the format: `\u003Ctarget-slug>-\u003CYYYY-MM-DD>.md`. Use lowercase kebab-case. If the target is a file path, slug is the basename without extension (`src\u002FApp.jsx` → `app-jsx`). If it's a PR, use `pr-\u003CN>`. If it's a decision, use a short kebab phrase.\n\n8. **Write the file** to `docs\u002Fassessments\u002F\u003Cfilename>`. Create the `docs\u002Fassessments\u002F` directory if it doesn't exist.\n\n9. **Report to the user**: show the file path, the overall grade and its band, and the top 1-2 highest-leverage improvements. Do not dump the full document into chat.\n\n## Grade bands\n\n| Grade    | Band      | Meaning                                      |\n| -------- | --------- | -------------------------------------------- |\n| 9.0-10.0 | Excellent | Ship\u002Fadopt without reservation               |\n| 7.0-8.9  | Solid     | Production-ready; minor polish               |\n| 5.0-6.9  | Passable  | Usable but has real gaps; fix before scaling |\n| 3.0-4.9  | Weak      | Significant problems; rework advised         |\n| 0.0-2.9  | Broken    | Do not ship\u002Fadopt                            |\n\n## Rubrics by target type\n\nWeights within each rubric sum to 1.00.\n\n### package\n\n| Dimension                                                          | Weight |\n| ------------------------------------------------------------------ | -----: |\n| Correctness (tests pass, matches spec)                             |   0.25 |\n| API design & ergonomics                                            |   0.15 |\n| Test coverage & quality                                            |   0.20 |\n| Documentation (README, examples, API docs)                         |   0.10 |\n| Maintenance signals (release cadence, open issues, responsiveness) |   0.10 |\n| Security & dependency health                                       |   0.20 |\n\n### project\n\n| Dimension                                   | Weight |\n| ------------------------------------------- | -----: |\n| Architecture clarity (boundaries, layering) |   0.20 |\n| Code quality & consistency                  |   0.15 |\n| Test coverage                               |   0.15 |\n| CI\u002FCD & automation                          |   0.10 |\n| Documentation (CLAUDE.md, README, runbooks) |   0.10 |\n| Security posture                            |   0.15 |\n| Observability (logs, metrics, alerting)     |   0.15 |\n\n### source-file\n\n| Dimension                  | Weight |\n| -------------------------- | -----: |\n| Correctness                |   0.30 |\n| Readability                |   0.20 |\n| Testability                |   0.15 |\n| Coupling & cohesion        |   0.15 |\n| Performance considerations |   0.10 |\n| Security                   |   0.10 |\n\n### architecture-decision\n\n| Dimension                           | Weight |\n| ----------------------------------- | -----: |\n| Problem framing                     |   0.20 |\n| Solution fit                        |   0.25 |\n| Alternatives considered             |   0.15 |\n| Trade-offs made explicit            |   0.15 |\n| Reversibility \u002F migration path      |   0.15 |\n| Operational impact (cost, ops load) |   0.10 |\n\n### pull-request\n\n| Dimension                            | Weight |\n| ------------------------------------ | -----: |\n| Scope focus (one thing, well-scoped) |   0.15 |\n| Diff clarity                         |   0.15 |\n| Test coverage of the change          |   0.25 |\n| Risk & rollback plan                 |   0.20 |\n| PR body quality (context, test plan) |   0.10 |\n| CI signal                            |   0.15 |\n\n### document\n\n| Dimension                                    | Weight |\n| -------------------------------------------- | -----: |\n| Clarity                                      |   0.25 |\n| Completeness                                 |   0.25 |\n| Evidence \u002F citations                         |   0.15 |\n| Actionability                                |   0.20 |\n| Maintenance hooks (owner, dates, versioning) |   0.15 |\n\n## Document structure\n\n```markdown\n# \u003CTarget Title> — Assessment — \u003CYYYY-MM-DD>\n\n\u003COne-line summary of what was assessed and why.>\n\n**Target type:** \u003Ctype>\n**Overall grade: X.X \u002F 10 — \u003CBand>**\n\n## Scope\n\nWhat was included and excluded from this assessment, and which rubric was applied (built-in for `\u003Ctype>`, or a user-provided custom rubric).\n\n## Rubric & scores\n\n| Dimension   |   Weight | Score | Weighted | Evidence               |\n| ----------- | -------: | ----: | -------: | ---------------------- |\n| ...         |     0.XX |  N\u002F10 |     N.NN | \u003Cfile:line, metric, …> |\n| **Overall** | **1.00** |     — |  **X.X** | —                      |\n\n## Dimension detail\n\n### \u003CDimension 1> — N\u002F10\n\nObservations with evidence. End with a short \"**To raise this score:**\" line listing concrete changes that would move the score up.\n\n### \u003CDimension 2> — N\u002F10\n\n...\n\n## Highest-leverage improvements\n\nRanked by estimated grade lift. Each item lists the action, the affected dimension(s), and the estimated lift.\n\n1. \u003CAction> — \u003Cdimension(s)> — estimated lift: +X.X\n2. \u003CAction> — \u003Cdimension(s)> — estimated lift: +X.X\n\n## Summary\n\n\u003C2-3 sentence verdict: overall grade in band context, the one dimension dragging the most, and the single recommended next action.>\n```\n\n## Rules\n\n- Every score must be backed by evidence in the Evidence column. No gut-feel numbers. If no evidence can be produced, score 0 and say so.\n- Use the built-in rubric weights exactly unless the user overrode them at invocation. Do not silently reweight.\n- Classify target type before scoring. State the type in the output doc.\n- Do not fix issues found. Report them in the Highest-leverage improvements section.\n- Do not commit the assessment file. Leave it untracked for the user to review.\n- Keep the document concise. Tables over prose where possible. No filler.\n- Round the overall grade to 1 decimal. Round weighted-column values to 2 decimals.\n- Never invent a target or expand scope beyond what was requested. If scope is unclear, ask.\n- If the user asks for a re-assessment of a previously graded target, read the prior file in `docs\u002Fassessments\u002F` and include a short \"Delta vs \u003Cprevious date>\" line under the overall grade.\n",{"name":5,"description":43,"allowed-tools":44,"argument-hint":45},"Create a structured assessment document grading a target on a 0-10 scale with a weighted rubric, saved to docs\u002Fassessments\u002F. Triggers on: \"grade\", \"rate\", \"score\", \"evaluate\", \"assess\".\n","Read Grep Glob Bash Write","[target]","main","91c337164997b99943fbcc64e8e362577b67bc81","examples\u002Fminimal-consumer\u002F.claude\u002Fskills\u002Fcreate-assessment","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":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add kaiohenricunha\u002Fdotbabel --skill create-assessment",{"tool":59,"command":60},"bunx","bunx skills add kaiohenricunha\u002Fdotbabel --skill create-assessment",{"tool":62,"command":63},"pnpm","pnpm dlx skills add kaiohenricunha\u002Fdotbabel --skill create-assessment","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fexamples\u002Fminimal-consumer\u002F.claude\u002Fskills\u002Fcreate-assessment\u002FSKILL.md",true,[],[68,99,132,153,175,198],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":79,"publishedAt":38},"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",[74],{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[70,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98],"testing","merge","code","start","access","session","ops","autonomy","releases","permission","full","runtime","scope","devex","hook","true","action","for","scoped",{"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":38},"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":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000037","律师与法务",[114,115,80,116,117,118,37,119,120,121,122,123,124,125,126,127,128,129,130,131],"audit","veracity audit","review","data pipeline","pipeline","math","coverage","only","engineer","formula","scoring","time","project","worker","end","at","invoke","when",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":38},"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",[],[139,140,141,80,116,142,143,114,37,144,35,145,121,146,147,148,149,150,151,152],"spec","validate","validate spec","run","acceptance","work","never","max","done","arch","line","2025","spec-driven","closure",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":162,"publishedAt":38},"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",[159],{"categoryNo":160,"categoryName":161,"taxonomyType":108,"taxonomyTypeDesc":109},"01JBSEEDCAT000000000000011","运维与部署",[163,164,165,116,166,167,142,114,168,37,35,169,170,146,171,172,150,173,129,174],"terragrunt","specialist","terragrunt specialist","orchestration","debugging","analysis","dependency","hooks","deep","dry","remote","hierarchy",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":188,"publishedAt":38},"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",[181,184,185],{"categoryNo":182,"categoryName":183,"taxonomyType":108,"taxonomyTypeDesc":109},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":160,"categoryName":161,"taxonomyType":108,"taxonomyTypeDesc":109},{"categoryNo":186,"categoryName":187,"taxonomyType":108,"taxonomyTypeDesc":109},"01JBSEEDCAT000000000000015","视觉设计",[189,190,164,80,191,116,192,193,194,167,114,37,35,120,195,196,171,197,150,129],"terraform","terraform specialist","design","workflows","architecture","architecture review","test coverage","workspaces","problem",{"skillNo":199,"name":139,"nameZh":6,"description":200,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":201,"categories":202,"keywords":207,"publishedAt":38},"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",[203,204],{"categoryNo":186,"categoryName":187,"taxonomyType":108,"taxonomyTypeDesc":109},{"categoryNo":205,"categoryName":206,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000032","设计师",[139,191,208,193,21,209,210,34,211,212,32,213,30,214,215,97,216,217,218,219],"component","plan","projects","interactive","use","specification","opus","technical specification","trade-offs","technical plan","outputs","frontier"]