[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7578BN8DDAQCAD8SE8RAW0M":3,"skill-same:01M7578BN8DDAQCAD8SE8RAW0M":136},{"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":45,"commitSha":46,"skillDirectory":47,"forksCount":14,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":6,"updatedAt":51,"install":52,"resources":65},"01M7578BN8DDAQCAD8SE8RAW0M","systematic-debugging",null,"Systematic root-cause debugging in 7 step files (0–6) covering TypeScript\u002FNode, Python, and Rust: read errors and build a red-capable feedback loop, trace data flow, analyze patterns, form ranked falsifiable hypotheses, implement one fix via TDD (RED-GREEN-REFACTOR), verify, and guard against rationalizations. Includes language-variant debugger\u002Fverify steps (3a\u002F3b\u002F3c, 5a\u002F5b\u002F5c). Observed phrasing: \u002Fsystematic-debugging, fix this bug, test is failing, performance regression.","rakaarwaky\u002Fagents-arwaky","rakaarwaky","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F245127434?v=4","01M7574QFJB21S6PPNCK78WX68","Raka Arwaky","01M7574QG54PRT44Q4KMQFXY6B",0,"MIT","https:\u002F\u002Fgithub.com\u002Frakaarwaky\u002Fagents-arwaky\u002Fblob\u002Fmain\u002Fskills\u002Fcode-quality\u002Fsystematic-debugging\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: systematic-debugging\ndescription: \"Systematic root-cause debugging in 7 step files (0–6) covering TypeScript\u002FNode, Python, and Rust: read errors and build a red-capable feedback loop, trace data flow, analyze patterns, form ranked falsifiable hypotheses, implement one fix via TDD (RED-GREEN-REFACTOR), verify, and guard against rationalizations. Includes language-variant debugger\u002Fverify steps (3a\u002F3b\u002F3c, 5a\u002F5b\u002F5c). Observed phrasing: \u002Fsystematic-debugging, fix this bug, test is failing, performance regression.\"\nwhen-to-use: \"Use for any technical issue — test failures, production bugs, build or performance problems, integration issues. Also for Python (pdb, debugpy), TypeScript\u002FNode (node inspect, CDP, heap\u002FCPU profiles), and Rust (dbg!, RUST_BACKTRACE, rust-gdb\u002Flldb) debugging. Invoke directly as \u002Fsystematic-debugging. Do not skip when the issue seems simple, you are in a hurry, or someone wants it fixed NOW — rushing guarantees rework.\"\nargument-hint: \"\u003Cissue-or-error> [--phase \u003C1|2|3|4>] [--lang \u003Cpython|typescript|rust|node>] [--repro \u003Ccommand>]\"\nmetadata:\n  tags:\n    - debugging\n    - troubleshooting\n    - problem-solving\n    - root-cause\n    - investigation\n    - tdd\n    - python\n    - typescript\n    - node\n    - rust\n    - pdb\n    - debugpy\n    - cdp\n  related_skills:\n    - pr-babysit\n    - issue-worker\n    - deep-clean\n---\n\n# Systematic Debugging\n\nFor any technical issue — test failures, production bugs, build or performance problems — find the root cause before touching a fix. This file is the lane identification step only; the working method lives in `references\u002Fhermes\u002F` and `references\u002Fgrok\u002F`.\n\n## Global Rules\n\nThe lane is determined from a physical signal, not by self-identification. Each agent's launcher stamps a fixed attribution env var into every command it runs; the model cannot set these.\n\n```bash\nif [[ -n \"${HERMES_AGENT:-}\" ]]; then echo HERMES\nelif [[ -n \"${GROK_AGENT:-}\" ]]; then echo GROK\nelse echo UNSET; fi\n```\n\n- `HERMES` → **Hermes lane.** Read `references\u002Fhermes\u002F`. Stop.\n- `GROK` → **Grok lane.** Read `references\u002Fgrok\u002F`. Stop.\n- `UNSET` → stop and report. Do not guess the lane.\n\nMarker provenance:\n\n- **Hermes** re-exports `AI_AGENT=hermes-agent` and `HERMES_AGENT=true` on every command.\n- **Grok Build** runs with `GROK_AGENT=1`.\n\nRead only the winning lane's references. Do not read the other lane's.\n\n## Routing\n\n### Hermes lane (Steps 0–3)\n\n| Step | Reference                                                                              | Purpose                                                                                                  |\n| ----: | -------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------ |\n| 0    | [`references\u002Fhermes\u002Fstep-0-plan-and-spawn.md`](references\u002Fhermes\u002Fstep-0-plan-and-spawn.md) | Detect lang; plan the brief (symptom, repro, phase, constraints, acceptance criteria); create the Orca worktree with `--agent grok`; drop `\u002Fsystematic-debugging \u003Cissue-or-error>` |\n| 1    | [`references\u002Fhermes\u002Fstep-1-wait-grok.md`](references\u002Fhermes\u002Fstep-1-wait-grok.md)         | Wait for Grok to finish the pipeline; read its debug summary and commit                                 |\n| 2    | [`references\u002Fhermes\u002Fstep-2-verify-and-ship.md`](references\u002Fhermes\u002Fstep-2-verify-and-ship.md) | Verify the iron law (regression test present), re-run the gate on the clean tree; commit\u002Fpush\u002FPR as appropriate |\n| 3    | [`references\u002Fhermes\u002Fstep-3-final-report.md`](references\u002Fhermes\u002Fstep-3-final-report.md) | Final report to the user (root cause, fix, verification, open decisions, commit\u002FPR, worktree teardown) |\n\n### Grok lane (Steps 0–6, run by Grok Build)\n\n| Step | Reference | Purpose |\n| ---- | --------- | ------- |\n| 0. Intake | [`references\u002Fgrok\u002Fstep-0-intake.md`](references\u002Fgrok\u002Fstep-0-intake.md) | Symptom statement, target lang, repro command, run state; iron-law gate; invocation. |\n| 1. Investigate | [`references\u002Fgrok\u002Fstep-1-investigate.md`](references\u002Fgrok\u002Fstep-1-investigate.md) | Read errors, build a tight red-capable loop, check recent changes, gather multi-component evidence, trace data flow. |\n| 2. Pattern | [`references\u002Fgrok\u002Fstep-2-pattern.md`](references\u002Fgrok\u002Fstep-2-pattern.md) | Minimize the repro, find working examples, compare against references, identify differences, understand dependencies. |\n| 3. Hypothesis | [`references\u002Fgrok\u002Fstep-3-hypothesis.md`](references\u002Fgrok\u002Fstep-3-hypothesis.md) | Form 3–5 ranked falsifiable hypotheses; test minimally, one variable at a time; pick the language debugger variant. |\n| 3a\u002F3b\u002F3c. Language debugger | [`step-3a-python-debugger.md`](references\u002Fgrok\u002Fstep-3a-python-debugger.md), [`step-3b-node-debugger.md`](references\u002Fgrok\u002Fstep-3b-node-debugger.md), [`step-3c-rust-debugger.md`](references\u002Fgrok\u002Fstep-3c-rust-debugger.md) | Python (pdb + debugpy), Node\u002FTS (node inspect + CDP, profiles), Rust (dbg!, RUST_BACKTRACE, rust-gdb\u002Flldb). |\n| 4. Implement | [`references\u002Fgrok\u002Fstep-4-implement.md`](references\u002Fgrok\u002Fstep-4-implement.md) | TDD cycle: RED failing test, GREEN single fix, per-language verify, REFACTOR; rule of three; question architecture at 3+ failures. |\n| 5. Verify & finish | [`references\u002Fgrok\u002Fstep-5-verify.md`](references\u002Fgrok\u002Fstep-5-verify.md) | Verification checklist, language cleanup pass (delegates to 5a\u002F5b\u002F5c), guardrails final pass, reporting format. |\n| 5a\u002F5b\u002F5c. Language verify | [`step-5a-python-verify.md`](references\u002Fgrok\u002Fstep-5a-python-verify.md), [`step-5b-node-verify.md`](references\u002Fgrok\u002Fstep-5b-node-verify.md), [`step-5c-rust-verify.md`](references\u002Fgrok\u002Fstep-5c-rust-verify.md) | Per-language verification + cleanup grep. |\n| 6. Guardrails | [`references\u002Fgrok\u002Fstep-6-guardrails.md`](references\u002Fgrok\u002Fstep-6-guardrails.md) | Red-flags list, common-rationalizations table, TDD rationale, TDD cycle detail; cross-cutting rules applied before reporting done. |\n","# Systematic Debugging\n\nFor any technical issue — test failures, production bugs, build or performance problems — find the root cause before touching a fix. This file is the lane identification step only; the working method lives in `references\u002Fhermes\u002F` and `references\u002Fgrok\u002F`.\n\n## Global Rules\n\nThe lane is determined from a physical signal, not by self-identification. Each agent's launcher stamps a fixed attribution env var into every command it runs; the model cannot set these.\n\n```bash\nif [[ -n \"${HERMES_AGENT:-}\" ]]; then echo HERMES\nelif [[ -n \"${GROK_AGENT:-}\" ]]; then echo GROK\nelse echo UNSET; fi\n```\n\n- `HERMES` → **Hermes lane.** Read `references\u002Fhermes\u002F`. Stop.\n- `GROK` → **Grok lane.** Read `references\u002Fgrok\u002F`. Stop.\n- `UNSET` → stop and report. Do not guess the lane.\n\nMarker provenance:\n\n- **Hermes** re-exports `AI_AGENT=hermes-agent` and `HERMES_AGENT=true` on every command.\n- **Grok Build** runs with `GROK_AGENT=1`.\n\nRead only the winning lane's references. Do not read the other lane's.\n\n## Routing\n\n### Hermes lane (Steps 0–3)\n\n| Step | Reference                                                                              | Purpose                                                                                                  |\n| ----: | -------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------ |\n| 0    | [`references\u002Fhermes\u002Fstep-0-plan-and-spawn.md`](references\u002Fhermes\u002Fstep-0-plan-and-spawn.md) | Detect lang; plan the brief (symptom, repro, phase, constraints, acceptance criteria); create the Orca worktree with `--agent grok`; drop `\u002Fsystematic-debugging \u003Cissue-or-error>` |\n| 1    | [`references\u002Fhermes\u002Fstep-1-wait-grok.md`](references\u002Fhermes\u002Fstep-1-wait-grok.md)         | Wait for Grok to finish the pipeline; read its debug summary and commit                                 |\n| 2    | [`references\u002Fhermes\u002Fstep-2-verify-and-ship.md`](references\u002Fhermes\u002Fstep-2-verify-and-ship.md) | Verify the iron law (regression test present), re-run the gate on the clean tree; commit\u002Fpush\u002FPR as appropriate |\n| 3    | [`references\u002Fhermes\u002Fstep-3-final-report.md`](references\u002Fhermes\u002Fstep-3-final-report.md) | Final report to the user (root cause, fix, verification, open decisions, commit\u002FPR, worktree teardown) |\n\n### Grok lane (Steps 0–6, run by Grok Build)\n\n| Step | Reference | Purpose |\n| ---- | --------- | ------- |\n| 0. Intake | [`references\u002Fgrok\u002Fstep-0-intake.md`](references\u002Fgrok\u002Fstep-0-intake.md) | Symptom statement, target lang, repro command, run state; iron-law gate; invocation. |\n| 1. Investigate | [`references\u002Fgrok\u002Fstep-1-investigate.md`](references\u002Fgrok\u002Fstep-1-investigate.md) | Read errors, build a tight red-capable loop, check recent changes, gather multi-component evidence, trace data flow. |\n| 2. Pattern | [`references\u002Fgrok\u002Fstep-2-pattern.md`](references\u002Fgrok\u002Fstep-2-pattern.md) | Minimize the repro, find working examples, compare against references, identify differences, understand dependencies. |\n| 3. Hypothesis | [`references\u002Fgrok\u002Fstep-3-hypothesis.md`](references\u002Fgrok\u002Fstep-3-hypothesis.md) | Form 3–5 ranked falsifiable hypotheses; test minimally, one variable at a time; pick the language debugger variant. |\n| 3a\u002F3b\u002F3c. Language debugger | [`step-3a-python-debugger.md`](references\u002Fgrok\u002Fstep-3a-python-debugger.md), [`step-3b-node-debugger.md`](references\u002Fgrok\u002Fstep-3b-node-debugger.md), [`step-3c-rust-debugger.md`](references\u002Fgrok\u002Fstep-3c-rust-debugger.md) | Python (pdb + debugpy), Node\u002FTS (node inspect + CDP, profiles), Rust (dbg!, RUST_BACKTRACE, rust-gdb\u002Flldb). |\n| 4. Implement | [`references\u002Fgrok\u002Fstep-4-implement.md`](references\u002Fgrok\u002Fstep-4-implement.md) | TDD cycle: RED failing test, GREEN single fix, per-language verify, REFACTOR; rule of three; question architecture at 3+ failures. |\n| 5. Verify & finish | [`references\u002Fgrok\u002Fstep-5-verify.md`](references\u002Fgrok\u002Fstep-5-verify.md) | Verification checklist, language cleanup pass (delegates to 5a\u002F5b\u002F5c), guardrails final pass, reporting format. |\n| 5a\u002F5b\u002F5c. Language verify | [`step-5a-python-verify.md`](references\u002Fgrok\u002Fstep-5a-python-verify.md), [`step-5b-node-verify.md`](references\u002Fgrok\u002Fstep-5b-node-verify.md), [`step-5c-rust-verify.md`](references\u002Fgrok\u002Fstep-5c-rust-verify.md) | Per-language verification + cleanup grep. |\n| 6. Guardrails | [`references\u002Fgrok\u002Fstep-6-guardrails.md`](references\u002Fgrok\u002Fstep-6-guardrails.md) | Red-flags list, common-rationalizations table, TDD rationale, TDD cycle detail; cross-cutting rules applied before reporting done. |\n",{"name":5,"metadata":24,"description":7,"when-to-use":43,"argument-hint":44},{"tags":25,"related_skills":39},[26,27,28,29,30,31,32,33,34,35,36,37,38],"debugging","troubleshooting","problem-solving","root-cause","investigation","tdd","python","typescript","node","rust","pdb","debugpy","cdp",[40,41,42],"pr-babysit","issue-worker","deep-clean","Use for any technical issue — test failures, production bugs, build or performance problems, integration issues. Also for Python (pdb, debugpy), TypeScript\u002FNode (node inspect, CDP, heap\u002FCPU profiles), and Rust (dbg!, RUST_BACKTRACE, rust-gdb\u002Flldb) debugging. Invoke directly as \u002Fsystematic-debugging. Do not skip when the issue seems simple, you are in a hurry, or someone wants it fixed NOW — rushing guarantees rework.","\u003Cissue-or-error> [--phase \u003C1|2|3|4>] [--lang \u003Cpython|typescript|rust|node>] [--repro \u003Ccommand>]","main","e0708985ab2d620bc6e8fe741eaa4ec1960269e3","skills\u002Fcode-quality\u002Fsystematic-debugging","https:\u002F\u002Fgithub.com\u002Frakaarwaky\u002Fagents-arwaky","https:\u002F\u002Fgithub.com\u002Frakaarwaky","https:\u002F\u002Fbuymeacoffee.com\u002Frakaarwaky","2026-11-15 04:28:37",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add rakaarwaky\u002Fagents-arwaky --skill systematic-debugging",{"tool":58,"command":59},"bunx","bunx skills add rakaarwaky\u002Fagents-arwaky --skill systematic-debugging",{"tool":61,"command":62},"pnpm","pnpm dlx skills add rakaarwaky\u002Fagents-arwaky --skill systematic-debugging","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frakaarwaky\u002Fagents-arwaky\u002Fblob\u002Fmain\u002Fskills\u002Fcode-quality\u002Fsystematic-debugging\u002FSKILL.md",true,[66,72,76,80,84,88,92,96,100,104,108,112,116,120,124,128,132],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fgrok\u002Fstep-0-intake.md","REFERENCE","参考文档",2003,"https:\u002F\u002Fgithub.com\u002Frakaarwaky\u002Fagents-arwaky\u002Fblob\u002Fmain\u002Fskills\u002Fcode-quality\u002Fsystematic-debugging\u002Freferences\u002Fgrok\u002Fstep-0-intake.md",{"path":73,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fgrok\u002Fstep-1-investigate.md",5879,"https:\u002F\u002Fgithub.com\u002Frakaarwaky\u002Fagents-arwaky\u002Fblob\u002Fmain\u002Fskills\u002Fcode-quality\u002Fsystematic-debugging\u002Freferences\u002Fgrok\u002Fstep-1-investigate.md",{"path":77,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fgrok\u002Fstep-2-pattern.md",1327,"https:\u002F\u002Fgithub.com\u002Frakaarwaky\u002Fagents-arwaky\u002Fblob\u002Fmain\u002Fskills\u002Fcode-quality\u002Fsystematic-debugging\u002Freferences\u002Fgrok\u002Fstep-2-pattern.md",{"path":81,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fgrok\u002Fstep-3-hypothesis.md",2093,"https:\u002F\u002Fgithub.com\u002Frakaarwaky\u002Fagents-arwaky\u002Fblob\u002Fmain\u002Fskills\u002Fcode-quality\u002Fsystematic-debugging\u002Freferences\u002Fgrok\u002Fstep-3-hypothesis.md",{"path":85,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fgrok\u002Fstep-3a-python-debugger.md",12913,"https:\u002F\u002Fgithub.com\u002Frakaarwaky\u002Fagents-arwaky\u002Fblob\u002Fmain\u002Fskills\u002Fcode-quality\u002Fsystematic-debugging\u002Freferences\u002Fgrok\u002Fstep-3a-python-debugger.md",{"path":89,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fgrok\u002Fstep-3b-node-debugger.md",11005,"https:\u002F\u002Fgithub.com\u002Frakaarwaky\u002Fagents-arwaky\u002Fblob\u002Fmain\u002Fskills\u002Fcode-quality\u002Fsystematic-debugging\u002Freferences\u002Fgrok\u002Fstep-3b-node-debugger.md",{"path":93,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fgrok\u002Fstep-3c-rust-debugger.md",3986,"https:\u002F\u002Fgithub.com\u002Frakaarwaky\u002Fagents-arwaky\u002Fblob\u002Fmain\u002Fskills\u002Fcode-quality\u002Fsystematic-debugging\u002Freferences\u002Fgrok\u002Fstep-3c-rust-debugger.md",{"path":97,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Fgrok\u002Fstep-4-implement.md",3067,"https:\u002F\u002Fgithub.com\u002Frakaarwaky\u002Fagents-arwaky\u002Fblob\u002Fmain\u002Fskills\u002Fcode-quality\u002Fsystematic-debugging\u002Freferences\u002Fgrok\u002Fstep-4-implement.md",{"path":101,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":102,"sourceHtmlUrl":103},"references\u002Fgrok\u002Fstep-5-verify.md",2443,"https:\u002F\u002Fgithub.com\u002Frakaarwaky\u002Fagents-arwaky\u002Fblob\u002Fmain\u002Fskills\u002Fcode-quality\u002Fsystematic-debugging\u002Freferences\u002Fgrok\u002Fstep-5-verify.md",{"path":105,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":106,"sourceHtmlUrl":107},"references\u002Fgrok\u002Fstep-5a-python-verify.md",940,"https:\u002F\u002Fgithub.com\u002Frakaarwaky\u002Fagents-arwaky\u002Fblob\u002Fmain\u002Fskills\u002Fcode-quality\u002Fsystematic-debugging\u002Freferences\u002Fgrok\u002Fstep-5a-python-verify.md",{"path":109,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":110,"sourceHtmlUrl":111},"references\u002Fgrok\u002Fstep-5b-node-verify.md",1078,"https:\u002F\u002Fgithub.com\u002Frakaarwaky\u002Fagents-arwaky\u002Fblob\u002Fmain\u002Fskills\u002Fcode-quality\u002Fsystematic-debugging\u002Freferences\u002Fgrok\u002Fstep-5b-node-verify.md",{"path":113,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":114,"sourceHtmlUrl":115},"references\u002Fgrok\u002Fstep-5c-rust-verify.md",748,"https:\u002F\u002Fgithub.com\u002Frakaarwaky\u002Fagents-arwaky\u002Fblob\u002Fmain\u002Fskills\u002Fcode-quality\u002Fsystematic-debugging\u002Freferences\u002Fgrok\u002Fstep-5c-rust-verify.md",{"path":117,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":118,"sourceHtmlUrl":119},"references\u002Fgrok\u002Fstep-6-guardrails.md",7256,"https:\u002F\u002Fgithub.com\u002Frakaarwaky\u002Fagents-arwaky\u002Fblob\u002Fmain\u002Fskills\u002Fcode-quality\u002Fsystematic-debugging\u002Freferences\u002Fgrok\u002Fstep-6-guardrails.md",{"path":121,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":122,"sourceHtmlUrl":123},"references\u002Fhermes\u002Fstep-0-plan-and-spawn.md",3610,"https:\u002F\u002Fgithub.com\u002Frakaarwaky\u002Fagents-arwaky\u002Fblob\u002Fmain\u002Fskills\u002Fcode-quality\u002Fsystematic-debugging\u002Freferences\u002Fhermes\u002Fstep-0-plan-and-spawn.md",{"path":125,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":126,"sourceHtmlUrl":127},"references\u002Fhermes\u002Fstep-1-wait-grok.md",1668,"https:\u002F\u002Fgithub.com\u002Frakaarwaky\u002Fagents-arwaky\u002Fblob\u002Fmain\u002Fskills\u002Fcode-quality\u002Fsystematic-debugging\u002Freferences\u002Fhermes\u002Fstep-1-wait-grok.md",{"path":129,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":130,"sourceHtmlUrl":131},"references\u002Fhermes\u002Fstep-2-verify-and-ship.md",2534,"https:\u002F\u002Fgithub.com\u002Frakaarwaky\u002Fagents-arwaky\u002Fblob\u002Fmain\u002Fskills\u002Fcode-quality\u002Fsystematic-debugging\u002Freferences\u002Fhermes\u002Fstep-2-verify-and-ship.md",{"path":133,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":134,"sourceHtmlUrl":135},"references\u002Fhermes\u002Fstep-3-final-report.md",790,"https:\u002F\u002Fgithub.com\u002Frakaarwaky\u002Fagents-arwaky\u002Fblob\u002Fmain\u002Fskills\u002Fcode-quality\u002Fsystematic-debugging\u002Freferences\u002Fhermes\u002Fstep-3-final-report.md",[137,145,152,159,166,173],{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":143,"publishedAt":144},"01M78SFXSH86CW16Z5FEXMSJXH","github-workflow","Umbrella for GitHub auth, repo management, issues, PRs, Mergify, and releases. Subsumes github-auth and repo-manager.","https:\u002F\u002Fgithub.com\u002Frakaarwaky\u002Fagents-arwaky\u002Fblob\u002Fmain\u002Fskills\u002Fgit\u002Fgithub-workflow\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":151,"publishedAt":144},"01M78SF81R7NVSCXAT8YQ255HM","brave-automation","baa CLI: Brave profiles, Google sessions, credentials.","https:\u002F\u002Fgithub.com\u002Frakaarwaky\u002Fagents-arwaky\u002Fblob\u002Fmain\u002Fskills\u002Fbrave-automation\u002Fbrave-automation\u002FSKILL.md",[],[],{"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":158,"publishedAt":144},"01M78SEY7TS908JM8KVPBM6HBN","aes","AES docs, layers, rule fixes, and legacy migration.","https:\u002F\u002Fgithub.com\u002Frakaarwaky\u002Fagents-arwaky\u002Fblob\u002Fmain\u002Fskills\u002Farchitechture\u002Faes\u002FSKILL.md",[],[],{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":165,"publishedAt":19},"01M757HBGFCMTJTQB45JQFXCC0","pretext","Build creative browser demos with DOM-free text layout.","https:\u002F\u002Fgithub.com\u002Frakaarwaky\u002Fagents-arwaky\u002Fblob\u002Fmain\u002Fskills\u002Fweb-design\u002Fpretext\u002FSKILL.md",[],[],{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":172,"publishedAt":19},"01M757H8K38ETN8F4ANBBRWY4G","popular-web-designs","54 real design systems (Stripe, Linear, Vercel) as HTML\u002FCSS.","https:\u002F\u002Fgithub.com\u002Frakaarwaky\u002Fagents-arwaky\u002Fblob\u002Fmain\u002Fskills\u002Fweb-design\u002Fpopular-web-designs\u002FSKILL.md",[],[],{"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":179,"publishedAt":19},"01M757H5DM7QPN9H391572NH5B","p5js","p5.js sketches: gen art, shaders, interactive, 3D.","https:\u002F\u002Fgithub.com\u002Frakaarwaky\u002Fagents-arwaky\u002Fblob\u002Fmain\u002Fskills\u002Fweb-design\u002Fp5js\u002FSKILL.md",[],[]]