[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75JEXPV2MXHTAFCWB458KYR":3,"skill-same:01M75JEXPV2MXHTAFCWB458KYR":45},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M75JEXPV2MXHTAFCWB458KYR","diagnosing-bugs",null,"Diagnosis loop for hard bugs and performance regressions. Use when the user says \"diagnose\", \"debug this\", \"debugge das\", \"finde den Fehler\", or reports something broken, throwing, failing, or slow (\"kaputt\", \"geht nicht\", \"Fehler\", \"langsam\").","colenet-gmbh\u002Fcolenet-claude-code-plugin","colenet-gmbh","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F27774717?v=4","01M75JEMA67P2CEDJC0GZCWZDV","Colenet GmbH","01M75JEMASFM02PQP38B77BBN5",0,"MIT","https:\u002F\u002Fgithub.com\u002Fcolenet-gmbh\u002Fcolenet-claude-code-plugin\u002Fblob\u002Fmain\u002Fskills_source\u002Fengineering\u002Fdiagnosing-bugs\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: diagnosing-bugs\ndescription: Diagnosis loop for hard bugs and performance regressions. Use when the user says \"diagnose\", \"debug this\", \"debugge das\", \"finde den Fehler\", or reports something broken, throwing, failing, or slow (\"kaputt\", \"geht nicht\", \"Fehler\", \"langsam\").\n---\n\n# Diagnosing Bugs\n\nA discipline for hard bugs. Skip phases only when explicitly justified.\n\nWhen exploring the codebase, read `CONTEXT.md` (if it exists) for a clear mental model of\nthe relevant modules, and check the ADRs in the area you're touching.\n\n## Phase 1 — Build a feedback loop\n\n**This is the skill.** Everything else is mechanical. If you have a **tight** pass\u002Ffail\nsignal for the bug — one that goes red on _this_ bug — you will find the cause; bisection,\nhypothesis-testing, and instrumentation all just consume it. If you don't have one, no\namount of staring at code will save you.\n\nSpend disproportionate effort here. **Be aggressive. Be creative. Refuse to give up.**\n\n### Ways to construct one — try them in roughly this order\n\n1. **Failing test** at whatever seam reaches the bug — unit, integration, e2e.\n2. **Curl \u002F HTTP script** against a running dev server.\n3. **CLI invocation** with a fixture input, diffing stdout against a known-good snapshot.\n4. **Headless browser script** (Playwright \u002F Puppeteer) — drives the UI, asserts on DOM\u002Fconsole\u002Fnetwork.\n5. **Replay a captured trace.** Save a real network request \u002F payload \u002F event log to disk; replay it through the code path in isolation.\n6. **Throwaway harness.** Spin up a minimal subset of the system (one service, mocked deps) that exercises the bug code path with a single function call.\n7. **Property \u002F fuzz loop.** If the bug is \"sometimes wrong output\", run 1000 random inputs and look for the failure mode.\n8. **Bisection harness.** If the bug appeared between two known states (commit, dataset, version), automate \"boot at state X, check, repeat\" so you can `git bisect run` it.\n9. **Differential loop.** Run the same input through old-version vs new-version (or two configs) and diff outputs.\n10. **HITL loop.** Last resort. If a human must click, drive _them_ with a structured\n    human-in-the-loop script — the human performs the step, its captured output feeds back\n    to you — so the loop stays repeatable instead of ad-hoc.\n\nBuild the right feedback loop, and the bug is 90% fixed.\n\n### Tighten the loop\n\nTreat the loop as a product. Once you have _a_ loop, **tighten** it:\n\n- Can I make it faster? (Cache setup, skip unrelated init, narrow the test scope.)\n- Can I make the signal sharper? (Assert on the specific symptom, not \"didn't crash\".)\n- Can I make it more deterministic? (Pin time, seed RNG, isolate filesystem, freeze network.)\n\nA 30-second flaky loop is barely better than no loop; a 2-second deterministic one is\ntight — a debugging superpower.\n\n### Non-deterministic bugs\n\nThe goal is not a clean repro but a **higher reproduction rate**. Loop the trigger 100×,\nparallelise, add stress, narrow timing windows, inject sleeps. A 50%-flake bug is\ndebuggable; 1% is not — keep raising the rate until it's debuggable.\n\n### When you genuinely cannot build a loop\n\nStop and say so explicitly. List what you tried. Ask the user for: (a) access to whatever\nenvironment reproduces it, (b) a captured artifact (HAR file, log dump, core dump, screen\nrecording with timestamps), or (c) permission to add temporary production instrumentation.\nDo **not** proceed to hypothesise without a loop.\n\n### Completion criterion — a tight loop that goes red\n\nPhase 1 is done when the loop is **tight** and **red-capable**: you can name **one\ncommand** — a script path, a test invocation, a curl — that you have **already run at\nleast once** (paste the invocation and its output), and that is:\n\n- [ ] **Red-capable** — it drives the actual bug code path and asserts the **user's exact symptom**, so it can go red on this bug and green once fixed. Not \"runs without erroring\" — it must _catch this specific bug_.\n- [ ] **Deterministic** — same verdict every run (flaky bugs: a pinned, high reproduction rate, per above).\n- [ ] **Fast** — seconds, not minutes.\n- [ ] **Agent-runnable** — you can run it unattended; a human in the loop only via a structured HITL script.\n\nIf you catch yourself reading code to build a theory before this command exists, **stop —\njumping straight to a hypothesis is the exact failure this skill prevents.** No red-capable\ncommand, no Phase 2.\n\n## Phase 2 — Reproduce + minimise\n\nRun the loop. Watch it go red — the bug appears.\n\nConfirm:\n\n- [ ] The loop produces the failure mode the **user** described — not a different failure that happens to be nearby. Wrong bug = wrong fix.\n- [ ] The failure is reproducible across multiple runs (or, for non-deterministic bugs, at a high enough rate to debug against).\n- [ ] You have captured the exact symptom (error message, wrong output, slow timing) so later phases can verify the fix.\n\n### Minimise\n\nOnce it's red, shrink the repro to the **smallest scenario that still goes red**. Cut\ninputs, callers, config, data, and steps **one at a time**, re-running the loop after each\ncut — keep only what's load-bearing for the failure.\n\nWhy bother: a minimal repro shrinks the hypothesis space in Phase 3 (fewer moving parts to\nsuspect) and becomes the clean regression test in Phase 5.\n\nDone when **every remaining element is load-bearing** — removing any one makes the loop go\ngreen. Do not proceed until you have reproduced **and** minimised.\n\n## Phase 3 — Hypothesise\n\nGenerate **3–5 ranked hypotheses** before testing any of them. Single-hypothesis\ngeneration anchors on the first plausible idea.\n\nEach hypothesis must be **falsifiable**: state the prediction it makes.\n\n> Format: \"If `X` is the cause, then changing `Y` will make the bug disappear \u002F changing `Z` will make it worse.\"\n\nIf you cannot state the prediction, the hypothesis is a vibe — discard or sharpen it.\n\n**Show the ranked list to the user before testing.** They often have domain knowledge that\nre-ranks instantly (\"we just deployed a change to #3\") or know hypotheses they've already\nruled out. Cheap checkpoint, big time saver. Don't block on it — proceed with your ranking\nif the user is AFK.\n\n## Phase 4 — Instrument\n\nEach probe must map to a specific prediction from Phase 3. **Change one variable at a time.**\n\nTool preference:\n\n1. **Debugger \u002F REPL inspection** if the env supports it. One breakpoint beats ten logs.\n2. **Targeted logs** at the boundaries that distinguish hypotheses.\n3. Never \"log everything and grep\".\n\n**Tag every debug log** with a unique prefix, e.g. `[DEBUG-a4f2]`. Cleanup at the end\nbecomes a single grep. Untagged logs survive; tagged logs die.\n\n**Perf branch.** For performance regressions, logs are usually wrong. Instead: establish a\nbaseline measurement (timing harness, `performance.now()`, profiler, query plan), then\nbisect. Measure first, fix second.\n\n## Phase 5 — Fix + regression test\n\nWrite the regression test **before the fix** — but only if there is a **correct seam** for\nit. A correct seam exercises the **real bug pattern** as it occurs at the call site. If the\nonly available seam is too shallow (a single-caller test when the bug needs multiple\ncallers, a unit test that can't replicate the triggering chain), a test there gives false\nconfidence.\n\n**If no correct seam exists, that itself is the finding.** Note it — the architecture is\npreventing the bug from being locked down. Flag it for the next phase.\n\nIf a correct seam exists:\n\n1. Turn the minimised repro into a failing test at that seam.\n2. Watch it fail.\n3. Apply the fix.\n4. Watch it pass.\n5. Re-run the Phase 1 loop against the original (un-minimised) scenario.\n\n## Phase 6 — Cleanup + post-mortem\n\nRequired before declaring done:\n\n- [ ] Original repro no longer reproduces (re-run the Phase 1 loop)\n- [ ] Regression test passes (or absence of seam is documented)\n- [ ] All `[DEBUG-...]` instrumentation removed (`grep` the prefix)\n- [ ] Throwaway prototypes deleted (or moved to a clearly-marked debug location)\n- [ ] The hypothesis that turned out correct is stated in the commit \u002F PR message — so the next debugger learns\n\n**Then ask: what would have prevented this bug?** If the answer involves architectural\nchange (no good test seam, tangled callers, hidden coupling), hand off to `cape:architect` with\nthe specifics. Make the recommendation **after** the fix is in, not before — you have more\ninformation now than when you started.\n","# Diagnosing Bugs\n\nA discipline for hard bugs. Skip phases only when explicitly justified.\n\nWhen exploring the codebase, read `CONTEXT.md` (if it exists) for a clear mental model of\nthe relevant modules, and check the ADRs in the area you're touching.\n\n## Phase 1 — Build a feedback loop\n\n**This is the skill.** Everything else is mechanical. If you have a **tight** pass\u002Ffail\nsignal for the bug — one that goes red on _this_ bug — you will find the cause; bisection,\nhypothesis-testing, and instrumentation all just consume it. If you don't have one, no\namount of staring at code will save you.\n\nSpend disproportionate effort here. **Be aggressive. Be creative. Refuse to give up.**\n\n### Ways to construct one — try them in roughly this order\n\n1. **Failing test** at whatever seam reaches the bug — unit, integration, e2e.\n2. **Curl \u002F HTTP script** against a running dev server.\n3. **CLI invocation** with a fixture input, diffing stdout against a known-good snapshot.\n4. **Headless browser script** (Playwright \u002F Puppeteer) — drives the UI, asserts on DOM\u002Fconsole\u002Fnetwork.\n5. **Replay a captured trace.** Save a real network request \u002F payload \u002F event log to disk; replay it through the code path in isolation.\n6. **Throwaway harness.** Spin up a minimal subset of the system (one service, mocked deps) that exercises the bug code path with a single function call.\n7. **Property \u002F fuzz loop.** If the bug is \"sometimes wrong output\", run 1000 random inputs and look for the failure mode.\n8. **Bisection harness.** If the bug appeared between two known states (commit, dataset, version), automate \"boot at state X, check, repeat\" so you can `git bisect run` it.\n9. **Differential loop.** Run the same input through old-version vs new-version (or two configs) and diff outputs.\n10. **HITL loop.** Last resort. If a human must click, drive _them_ with a structured\n    human-in-the-loop script — the human performs the step, its captured output feeds back\n    to you — so the loop stays repeatable instead of ad-hoc.\n\nBuild the right feedback loop, and the bug is 90% fixed.\n\n### Tighten the loop\n\nTreat the loop as a product. Once you have _a_ loop, **tighten** it:\n\n- Can I make it faster? (Cache setup, skip unrelated init, narrow the test scope.)\n- Can I make the signal sharper? (Assert on the specific symptom, not \"didn't crash\".)\n- Can I make it more deterministic? (Pin time, seed RNG, isolate filesystem, freeze network.)\n\nA 30-second flaky loop is barely better than no loop; a 2-second deterministic one is\ntight — a debugging superpower.\n\n### Non-deterministic bugs\n\nThe goal is not a clean repro but a **higher reproduction rate**. Loop the trigger 100×,\nparallelise, add stress, narrow timing windows, inject sleeps. A 50%-flake bug is\ndebuggable; 1% is not — keep raising the rate until it's debuggable.\n\n### When you genuinely cannot build a loop\n\nStop and say so explicitly. List what you tried. Ask the user for: (a) access to whatever\nenvironment reproduces it, (b) a captured artifact (HAR file, log dump, core dump, screen\nrecording with timestamps), or (c) permission to add temporary production instrumentation.\nDo **not** proceed to hypothesise without a loop.\n\n### Completion criterion — a tight loop that goes red\n\nPhase 1 is done when the loop is **tight** and **red-capable**: you can name **one\ncommand** — a script path, a test invocation, a curl — that you have **already run at\nleast once** (paste the invocation and its output), and that is:\n\n- [ ] **Red-capable** — it drives the actual bug code path and asserts the **user's exact symptom**, so it can go red on this bug and green once fixed. Not \"runs without erroring\" — it must _catch this specific bug_.\n- [ ] **Deterministic** — same verdict every run (flaky bugs: a pinned, high reproduction rate, per above).\n- [ ] **Fast** — seconds, not minutes.\n- [ ] **Agent-runnable** — you can run it unattended; a human in the loop only via a structured HITL script.\n\nIf you catch yourself reading code to build a theory before this command exists, **stop —\njumping straight to a hypothesis is the exact failure this skill prevents.** No red-capable\ncommand, no Phase 2.\n\n## Phase 2 — Reproduce + minimise\n\nRun the loop. Watch it go red — the bug appears.\n\nConfirm:\n\n- [ ] The loop produces the failure mode the **user** described — not a different failure that happens to be nearby. Wrong bug = wrong fix.\n- [ ] The failure is reproducible across multiple runs (or, for non-deterministic bugs, at a high enough rate to debug against).\n- [ ] You have captured the exact symptom (error message, wrong output, slow timing) so later phases can verify the fix.\n\n### Minimise\n\nOnce it's red, shrink the repro to the **smallest scenario that still goes red**. Cut\ninputs, callers, config, data, and steps **one at a time**, re-running the loop after each\ncut — keep only what's load-bearing for the failure.\n\nWhy bother: a minimal repro shrinks the hypothesis space in Phase 3 (fewer moving parts to\nsuspect) and becomes the clean regression test in Phase 5.\n\nDone when **every remaining element is load-bearing** — removing any one makes the loop go\ngreen. Do not proceed until you have reproduced **and** minimised.\n\n## Phase 3 — Hypothesise\n\nGenerate **3–5 ranked hypotheses** before testing any of them. Single-hypothesis\ngeneration anchors on the first plausible idea.\n\nEach hypothesis must be **falsifiable**: state the prediction it makes.\n\n> Format: \"If `X` is the cause, then changing `Y` will make the bug disappear \u002F changing `Z` will make it worse.\"\n\nIf you cannot state the prediction, the hypothesis is a vibe — discard or sharpen it.\n\n**Show the ranked list to the user before testing.** They often have domain knowledge that\nre-ranks instantly (\"we just deployed a change to #3\") or know hypotheses they've already\nruled out. Cheap checkpoint, big time saver. Don't block on it — proceed with your ranking\nif the user is AFK.\n\n## Phase 4 — Instrument\n\nEach probe must map to a specific prediction from Phase 3. **Change one variable at a time.**\n\nTool preference:\n\n1. **Debugger \u002F REPL inspection** if the env supports it. One breakpoint beats ten logs.\n2. **Targeted logs** at the boundaries that distinguish hypotheses.\n3. Never \"log everything and grep\".\n\n**Tag every debug log** with a unique prefix, e.g. `[DEBUG-a4f2]`. Cleanup at the end\nbecomes a single grep. Untagged logs survive; tagged logs die.\n\n**Perf branch.** For performance regressions, logs are usually wrong. Instead: establish a\nbaseline measurement (timing harness, `performance.now()`, profiler, query plan), then\nbisect. Measure first, fix second.\n\n## Phase 5 — Fix + regression test\n\nWrite the regression test **before the fix** — but only if there is a **correct seam** for\nit. A correct seam exercises the **real bug pattern** as it occurs at the call site. If the\nonly available seam is too shallow (a single-caller test when the bug needs multiple\ncallers, a unit test that can't replicate the triggering chain), a test there gives false\nconfidence.\n\n**If no correct seam exists, that itself is the finding.** Note it — the architecture is\npreventing the bug from being locked down. Flag it for the next phase.\n\nIf a correct seam exists:\n\n1. Turn the minimised repro into a failing test at that seam.\n2. Watch it fail.\n3. Apply the fix.\n4. Watch it pass.\n5. Re-run the Phase 1 loop against the original (un-minimised) scenario.\n\n## Phase 6 — Cleanup + post-mortem\n\nRequired before declaring done:\n\n- [ ] Original repro no longer reproduces (re-run the Phase 1 loop)\n- [ ] Regression test passes (or absence of seam is documented)\n- [ ] All `[DEBUG-...]` instrumentation removed (`grep` the prefix)\n- [ ] Throwaway prototypes deleted (or moved to a clearly-marked debug location)\n- [ ] The hypothesis that turned out correct is stated in the commit \u002F PR message — so the next debugger learns\n\n**Then ask: what would have prevented this bug?** If the answer involves architectural\nchange (no good test seam, tangled callers, hidden coupling), hand off to `cape:architect` with\nthe specifics. Make the recommendation **after** the fix is in, not before — you have more\ninformation now than when you started.\n",{"name":5,"description":7},"main","47dbd725f1dd37f2c0deed3f223249b2cdcbb5a8","skills_source\u002Fengineering\u002Fdiagnosing-bugs","https:\u002F\u002Fgithub.com\u002Fcolenet-gmbh\u002Fcolenet-claude-code-plugin","https:\u002F\u002Fgithub.com\u002Fcolenet-gmbh","https:\u002F\u002Fwww.colenet.de","2026-10-05 07:40:40",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add colenet-gmbh\u002Fcolenet-claude-code-plugin --skill diagnosing-bugs",{"tool":37,"command":38},"bunx","bunx skills add colenet-gmbh\u002Fcolenet-claude-code-plugin --skill diagnosing-bugs",{"tool":40,"command":41},"pnpm","pnpm dlx skills add colenet-gmbh\u002Fcolenet-claude-code-plugin --skill diagnosing-bugs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcolenet-gmbh\u002Fcolenet-claude-code-plugin\u002Fblob\u002Fmain\u002Fskills_source\u002Fengineering\u002Fdiagnosing-bugs\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M75JGH2BKSPNHEFPK7GGWWX9","triage","Backlog management — move not-yet-worked-up items through triage roles into agent-ready briefs, whatever their origin. Use when the user wants to sort or work up a backlog of bug reports, feature requests, or ideas, mentions \"triage\", \"triagieren\", \"Backlog sichten\", \"Backlog pflegen\", \"sort the backlog\", \"manage the backlog\", or points at an untriaged item in docs\u002Fwork\u002F01-backlog.","https:\u002F\u002Fgithub.com\u002Fcolenet-gmbh\u002Fcolenet-claude-code-plugin\u002Fblob\u002Fmain\u002Fskills_source\u002Futility\u002Ftriage\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M75JGDZC06KVV60HW33NKMZV","teach","Teach the user a new skill or concept over multiple sessions, turning the current directory into a stateful teaching workspace grounded in a mission, trusted resources, and beautiful lessons. Use when the user wants to learn or be taught something, or says \"teach me\", \"bring mir bei\", \"lehre mich\", \"ich will X lernen\", \"mach mich fit in\", \"onboard me on\", \"help me learn\".","https:\u002F\u002Fgithub.com\u002Fcolenet-gmbh\u002Fcolenet-claude-code-plugin\u002Fblob\u002Fmain\u002Fskills_source\u002Futility\u002Fteach\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M75JG9EF7354J71JQRZVQ82X","research","Delegate reading legwork to a background agent — investigate a question against high-trust primary sources (official docs, source code, specs, first-party APIs) and leave the findings as a cited Markdown note in the repo. Use when engineering work needs docs, API, or codebase facts gathered before building, or the user says \"recherchiere das\", \"schau in den Docs nach\", \"lies dich in X ein\", \"research this\", \"gather the facts on\", \"read up on\". For a broad, multi-source web report with adversarial fact-checking, reach for deep-research instead; cape:research is the lighter, repo-bound feeder that leaves a note behind.","https:\u002F\u002Fgithub.com\u002Fcolenet-gmbh\u002Fcolenet-claude-code-plugin\u002Fblob\u002Fmain\u002Fskills_source\u002Futility\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M75JG5R86XRG8B6EYX3JB06H","prototype","Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.","https:\u002F\u002Fgithub.com\u002Fcolenet-gmbh\u002Fcolenet-claude-code-plugin\u002Fblob\u002Fmain\u002Fskills_source\u002Futility\u002Fprototype\u002FSKILL.md",[],[],{"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":80,"publishedAt":19},"01M75JG46T7P54KKF80X22HF4Z","handoff","Compact the current conversation into a handoff document for another agent to pick up.","https:\u002F\u002Fgithub.com\u002Fcolenet-gmbh\u002Fcolenet-claude-code-plugin\u002Fblob\u002Fmain\u002Fskills_source\u002Futility\u002Fhandoff\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M75JG2EM4XSXC32SRRN37VRA","grilling","Interview the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.","https:\u002F\u002Fgithub.com\u002Fcolenet-gmbh\u002Fcolenet-claude-code-plugin\u002Fblob\u002Fmain\u002Fskills_source\u002Futility\u002Fgrilling\u002FSKILL.md",[],[]]