[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6P5AWC1D7S2CGZRY2XCAAVZ":3,"skill-same:01M6P5AWC1D7S2CGZRY2XCAAVZ":101},{"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":31,"publishedAt":51,"linkOnly":52,"markdownContent":53,"markdownBody":54,"frontMatter":55,"refName":80,"commitSha":81,"skillDirectory":82,"forksCount":83,"repositoryHtmlUrl":84,"repositoryHomepageUrl":6,"ownerHtmlUrl":85,"ownerBlogUrl":86,"ownerDescription":6,"updatedAt":87,"install":88,"resources":100},"01M6P5AWC1D7S2CGZRY2XCAAVZ","debugging",null,"Produces a Debug Report documenting root cause, fix applied, and lessons learned through systematic hypothesis testing. Use when: 'debug this error', 'why is this failing', 'investigate the issue', 'find the root cause', 'fix this bug systematically'.","DojoGenesis\u002Fgateway","DojoGenesis","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F273886418?v=4","01M6P54RXMD3TZ2082Z3Z4JMQP","Cruz Morales (TresPies)","01M6P54S269YR0ZZZ96WGQM439",2,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FDojoGenesis\u002Fgateway\u002Fblob\u002Fmain\u002Fplugins\u002Fcontinuous-learning\u002Fskills\u002Fdebugging\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[5,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50],"context","lessons","sonnet","learned","systematic","issue","bug","use","fix","behavior","testing","system","stack","learning","why","investigate","logs","file","debug","2026-11-10 10:12:30",false,"---\nname: debugging\nmodel: sonnet\ndescription: \"Produces a Debug Report documenting root cause, fix applied, and lessons learned through systematic hypothesis testing. Use when: 'debug this error', 'why is this failing', 'investigate the issue', 'find the root cause', 'fix this bug systematically'.\"\ncategory: continuous-learning\ntriggers:\n  - \"debug this error\"\n  - \"why is this failing\"\n  - \"investigate the issue\"\n  - \"find the root cause\"\n  - \"fix this bug systematically\"\ntier: 1\nagents:\n  - \"primary\"\ntool_dependencies:\n  - \"file_system\"\n\ninputs:\n  - name: error_description\n    type: string\n    description: Description of the error or failing behavior to debug\n    required: true\n  - name: context\n    type: string\n    description: Additional context — stack traces, logs, reproduction steps\n    required: false\noutputs:\n  - name: debug_report\n    type: string\n    description: Debug Report documenting root cause, fix applied, and lessons learned\n---\n\n# Debugging & Troubleshooting Skills\n\n**Version:** 1.0\n**Created:** 2026-02-02\n**Author:** Cipher\n**Purpose:** Systematic debugging and troubleshooting for code, systems, and workflows\n\n---\n\n## Overview\n\nThis skill encodes best practices for **debugging and troubleshooting**—isolating problems, identifying root causes, and implementing fixes methodically. It provides patterns for reading logs, reproducing issues, testing hypotheses, and verifying solutions.\n\n**Philosophy:** Debugging is systematic investigation, not random guessing. One change at a time, test, observe, learn.\n\n---\n\n## When to Use This Skill\n\n- Code behaves unexpectedly (errors, crashes, wrong output)\n- Performance degradation (slow queries, long build times)\n- Data inconsistency (database state out of sync)\n- Integration failure (API returns errors, sync breaks)\n- Feature not working as expected (UI bug, logic error)\n\n---\n\n## Core Principles\n\n### 1. Debugging is Systematic, Not Random\n\n**Don't:** Change 5 things at once, guess without evidence, apply fixes blindly, skip testing after fixing.\n\n**Do:** Formulate hypothesis (\"X causes Y\"), test hypothesis, fix based on confirmed cause, re-test to verify.\n\n### 2. Observe, Don't Assume\n\n**Observe:** Error messages (exact text, stack traces), logs (timestamps, context, sequence), system state, user behavior.\n\n**Don't assume:** \"It's probably a caching issue\" \u002F \"The user must have done X wrong\" \u002F \"This library is broken\" (without evidence).\n\n### 3. Isolate Variables\n\nWhen you have multiple factors, test them independently:\n\n| Factor | Result |\n|--------|--------|\n| Database query | FAIL — Timeout (4s) |\n| Network request | PASS — Works |\n| Frontend render | PASS — Works |\n\n**Conclusion:** Database query is bottleneck. Optimize query or increase timeout.\n\n### 4. Reproduce Consistently\n\nBefore debugging: identify exact steps to reproduce, run 3+ times, note if intermittent, identify patterns if so.\n\n**Why:** You can't fix what you can't reproduce.\n\n---\n\n## Debugging Workflow\n\n### Step 1: Gather Information (5-10 minutes)\n\n**Collect:** Error messages (exact text, stack traces, error codes), logs, context (what changed recently?), expected vs. actual behavior, environment (OS, versions, dependencies).\n\n**Template:**\n\n```markdown\n## Debug: [Issue Title]\n\n**Error Message:** [Exact error text]\n**Stack Trace:** [Copy relevant portion]\n**Logs:** [Key log lines with timestamps]\n**Context:** What triggered the issue \u002F Recent changes \u002F Environment (Node, DB, OS)\n**Expected Behavior:** [What should happen]\n**Actual Behavior:** [What actually happened]\n```\n\n### Step 2: Formulate Hypothesis (2-5 minutes)\n\nAsk: What could cause this? What's most likely? What evidence supports it?\n\n**Examples:**\n- \"Database query timeout caused by missing index\"\n- \"404 error caused by wrong file path in env var\"\n- \"Sync fails because file encoding is wrong\"\n\n**Prioritize:** Most likely (70%) → Second most likely (30%) → Edge cases (10%)\n\n### Step 3: Test Hypothesis (5-15 minutes)\n\n1. **Verify directly** — Add logging to confirm cause; run minimal reproduction case\n2. **Isolate variables** — Remove dependencies, simplify data, change environment\n3. **Confirm fix** — Apply targeted fix, re-run reproduction steps, verify resolved\n\n**Document results:**\n```\nHypothesis: [Description]\nTest Method: [How tested]\nResult: Confirmed \u002F Rejected\nEvidence: [What proved\u002Fdisproved hypothesis]\n```\n\n### Step 4: Implement Fix\n\n**If confirmed:** Implement minimal fix, add error handling, add logging for future detection.  \n**If rejected:** Move to next hypothesis, re-gather information, consider broader systemic causes.\n\n### Step 5: Verify & Document (5-10 minutes)\n\n**Verify:** Original reproduction steps no longer fail, edge cases work, no regressions.\n\n**Document:**\n```markdown\n## Fix: [Issue Title]\n\n**Root Cause:** [What actually caused issue]\n**Solution:** [What was fixed]\n**Code Changes:** [File, function, or module changed]\n**Testing:**\n- Original issue: Resolved\n- Edge cases: Tested\n- Regression check: No regressions\n**Lessons Learned:** [What to do differently in future]\n```\n\n---\n\n## Common Debugging Patterns\n\n### Pattern 1: Read Logs Strategically\n\nDon't read entire log files. Search for error codes or keywords, extract lines around error timestamp (±5 min), look for recurring patterns.\n\n```bash\ngrep -i \"error\" app.log | tail -20\ngrep \"2026-02-02T14:00\" app.log -A 5 -B 5\ngrep -A 10 \"Error:\" app.log\n```\n\n### Pattern 2: Use Logging to Verify\n\n| Point | Log What | Why |\n|--------|-----------|-----|\n| Before database query | Query string, parameters | See what's being executed |\n| After database query | Rows returned, time taken | Performance check |\n| Before API call | Request payload | Verify what's sent |\n| After API call | Response status, body | Verify what's received |\n| Before file write | File path, content | Verify what's written |\n\n**When in doubt, add a log. You can always remove later.**\n\n### Pattern 3: Binary Search for Root Cause\n\nNarrow down variables systematically. For a slow query: test with 10 rows (rules out table size), then run EXPLAIN (reveals missing index), then add index and confirm fix. One variable at a time.\n\n### Pattern 4: Reproduce in Isolated Environment\n\nWhen issue only happens in production: create minimal reproduction in dev, simplify data, mock external dependencies, test against same environment versions. Goal: isolate whether issue is data, code, or environment.\n\n### Pattern 5: Use Version Control for Time Travel\n\n```bash\ngit log --oneline -10\ngit log --oneline --since=\"2026-02-02T13:00\"\ngit bisect start\ngit bisect bad HEAD\ngit bisect good \u003Clast-working-commit>\n```\n\n---\n\n## Troubleshooting Categories\n\n### 1. Code Errors (Runtime, Compile, Type)\n\n**Causes:** Null\u002Fundefined access, async timing issues, type mismatches, module not found  \n**Approach:** Read error carefully, check stack trace for file\u002Fline, search error code, isolate the function\n\n### 2. Performance Issues\n\n**Causes:** N+1 queries, slow renders, memory leaks, network latency  \n**Approach:** Profile the slow operation, identify bottleneck (database\u002FCPU\u002FI\u002FO\u002Fnetwork), optimize the bottleneck, measure before\u002Fafter\n\n### 3. Data Inconsistency\n\n**Causes:** Database out of sync, cache invalidation, race conditions, migration not applied  \n**Approach:** Compare DB state vs. expected, check last sync timestamp, verify integrity, re-run sync or migration\n\n### 4. Integration Failures\n\n**Causes:** API contract mismatch, auth failures, network connectivity, service downtime  \n**Approach:** Verify request format, check credentials, test API directly (curl\u002FPostman), check service status\n\n### 5. Environment-Specific Issues\n\n**Causes:** Missing\u002Fwrong env vars, path differences (Win\u002FMac\u002FLinux), dependency version conflicts, file permissions  \n**Approach:** Compare working vs. broken env, check env vars, verify dependency versions, check paths and permissions\n\n---\n\n## Quality Checklist\n\nBefore considering debugging complete:\n\n- [ ] Root cause identified (not just symptom fixed)\n- [ ] Hypothesis tested with evidence\n- [ ] Fix is minimal (don't over-engineer)\n- [ ] Original issue reproduced before fix\n- [ ] Fix resolves issue (not just hides it)\n- [ ] Edge cases tested\n- [ ] No regressions (other features still work)\n- [ ] Root cause, solution, and lessons learned documented\n\n---\n\n## Common Pitfalls to Avoid\n\n- **Shotgun debugging** — Change everything — one change, test, observe\n- **Ignoring error messages** — \"Probably network\" — read exact error, search it\n- **Fixing without testing** — Apply change, assume it works — reproduce, fix, re-test\n- **Assuming environment** — \"Works on my machine\" — verify in actual environment\n- **Blaming external deps** — \"Library is broken\" — verify your usage first\n\n---\n\n## Output\n\n- A Debug Report markdown file saved to the project's working directory or `docs\u002Fdebug\u002F`\n- Named: `[date]_[issue-slug]_debug.md`\n- Sections: Error Message, Stack Trace, Root Cause, Solution, Code Changes, Test Results, Lessons Learned\n\n---\n\n## Examples\n\n**Scenario 1:** \"Debug this error: TypeError: Cannot read property 'id' of undefined\" → Debug Report with hypothesis (null user object), test method (added logging), root cause confirmed, fix applied (null check), regression test documented\n\n**Scenario 2:** \"Why is this database query taking 8 seconds?\" → Debug Report using binary search on query complexity, EXPLAIN output showing missing index, index added, before\u002Fafter timing documented\n\n---\n\n## Edge Cases\n\n- **Error is intermittent (not reproducible):** Add logging around the suspected area, capture the next occurrence, treat the log as the reproduction case\n- **Issue only happens in production:** Create a minimal reproduction in dev using production-equivalent data and environment vars; document the environment delta\n- **Multiple simultaneous errors:** Prioritize by severity — fix the error that is blocking other fixes first; do not debug all at once\n\n---\n\n## Anti-Patterns\n\n- Changing multiple things at once before testing — makes it impossible to identify which change resolved the issue\n- Searching for the error message online before reading the stack trace — the stack trace almost always locates the cause; search is for when the trace is unhelpful\n- Marking a bug as fixed when tests pass but root cause was not confirmed — symptom masking produces the same bug later under different conditions\n- Writing a fix that hides the error (empty catch, fallback default) instead of addressing the cause\n\n---\n\n**Related Skills:**\n- `workspace-navigation` — When debugging collaborative workspaces\n- `repo-context-sync` — When debugging git integration issues\n- `web-research` — When searching error codes or similar issues online\n- `research-modes` — Deep investigation techniques\n\n---\n\n**Last Updated:** 2026-04-08\n**Maintained By:** Cipher\n**Status:** Active\n","# Debugging & Troubleshooting Skills\n\n**Version:** 1.0\n**Created:** 2026-02-02\n**Author:** Cipher\n**Purpose:** Systematic debugging and troubleshooting for code, systems, and workflows\n\n---\n\n## Overview\n\nThis skill encodes best practices for **debugging and troubleshooting**—isolating problems, identifying root causes, and implementing fixes methodically. It provides patterns for reading logs, reproducing issues, testing hypotheses, and verifying solutions.\n\n**Philosophy:** Debugging is systematic investigation, not random guessing. One change at a time, test, observe, learn.\n\n---\n\n## When to Use This Skill\n\n- Code behaves unexpectedly (errors, crashes, wrong output)\n- Performance degradation (slow queries, long build times)\n- Data inconsistency (database state out of sync)\n- Integration failure (API returns errors, sync breaks)\n- Feature not working as expected (UI bug, logic error)\n\n---\n\n## Core Principles\n\n### 1. Debugging is Systematic, Not Random\n\n**Don't:** Change 5 things at once, guess without evidence, apply fixes blindly, skip testing after fixing.\n\n**Do:** Formulate hypothesis (\"X causes Y\"), test hypothesis, fix based on confirmed cause, re-test to verify.\n\n### 2. Observe, Don't Assume\n\n**Observe:** Error messages (exact text, stack traces), logs (timestamps, context, sequence), system state, user behavior.\n\n**Don't assume:** \"It's probably a caching issue\" \u002F \"The user must have done X wrong\" \u002F \"This library is broken\" (without evidence).\n\n### 3. Isolate Variables\n\nWhen you have multiple factors, test them independently:\n\n| Factor | Result |\n|--------|--------|\n| Database query | FAIL — Timeout (4s) |\n| Network request | PASS — Works |\n| Frontend render | PASS — Works |\n\n**Conclusion:** Database query is bottleneck. Optimize query or increase timeout.\n\n### 4. Reproduce Consistently\n\nBefore debugging: identify exact steps to reproduce, run 3+ times, note if intermittent, identify patterns if so.\n\n**Why:** You can't fix what you can't reproduce.\n\n---\n\n## Debugging Workflow\n\n### Step 1: Gather Information (5-10 minutes)\n\n**Collect:** Error messages (exact text, stack traces, error codes), logs, context (what changed recently?), expected vs. actual behavior, environment (OS, versions, dependencies).\n\n**Template:**\n\n```markdown\n## Debug: [Issue Title]\n\n**Error Message:** [Exact error text]\n**Stack Trace:** [Copy relevant portion]\n**Logs:** [Key log lines with timestamps]\n**Context:** What triggered the issue \u002F Recent changes \u002F Environment (Node, DB, OS)\n**Expected Behavior:** [What should happen]\n**Actual Behavior:** [What actually happened]\n```\n\n### Step 2: Formulate Hypothesis (2-5 minutes)\n\nAsk: What could cause this? What's most likely? What evidence supports it?\n\n**Examples:**\n- \"Database query timeout caused by missing index\"\n- \"404 error caused by wrong file path in env var\"\n- \"Sync fails because file encoding is wrong\"\n\n**Prioritize:** Most likely (70%) → Second most likely (30%) → Edge cases (10%)\n\n### Step 3: Test Hypothesis (5-15 minutes)\n\n1. **Verify directly** — Add logging to confirm cause; run minimal reproduction case\n2. **Isolate variables** — Remove dependencies, simplify data, change environment\n3. **Confirm fix** — Apply targeted fix, re-run reproduction steps, verify resolved\n\n**Document results:**\n```\nHypothesis: [Description]\nTest Method: [How tested]\nResult: Confirmed \u002F Rejected\nEvidence: [What proved\u002Fdisproved hypothesis]\n```\n\n### Step 4: Implement Fix\n\n**If confirmed:** Implement minimal fix, add error handling, add logging for future detection.  \n**If rejected:** Move to next hypothesis, re-gather information, consider broader systemic causes.\n\n### Step 5: Verify & Document (5-10 minutes)\n\n**Verify:** Original reproduction steps no longer fail, edge cases work, no regressions.\n\n**Document:**\n```markdown\n## Fix: [Issue Title]\n\n**Root Cause:** [What actually caused issue]\n**Solution:** [What was fixed]\n**Code Changes:** [File, function, or module changed]\n**Testing:**\n- Original issue: Resolved\n- Edge cases: Tested\n- Regression check: No regressions\n**Lessons Learned:** [What to do differently in future]\n```\n\n---\n\n## Common Debugging Patterns\n\n### Pattern 1: Read Logs Strategically\n\nDon't read entire log files. Search for error codes or keywords, extract lines around error timestamp (±5 min), look for recurring patterns.\n\n```bash\ngrep -i \"error\" app.log | tail -20\ngrep \"2026-02-02T14:00\" app.log -A 5 -B 5\ngrep -A 10 \"Error:\" app.log\n```\n\n### Pattern 2: Use Logging to Verify\n\n| Point | Log What | Why |\n|--------|-----------|-----|\n| Before database query | Query string, parameters | See what's being executed |\n| After database query | Rows returned, time taken | Performance check |\n| Before API call | Request payload | Verify what's sent |\n| After API call | Response status, body | Verify what's received |\n| Before file write | File path, content | Verify what's written |\n\n**When in doubt, add a log. You can always remove later.**\n\n### Pattern 3: Binary Search for Root Cause\n\nNarrow down variables systematically. For a slow query: test with 10 rows (rules out table size), then run EXPLAIN (reveals missing index), then add index and confirm fix. One variable at a time.\n\n### Pattern 4: Reproduce in Isolated Environment\n\nWhen issue only happens in production: create minimal reproduction in dev, simplify data, mock external dependencies, test against same environment versions. Goal: isolate whether issue is data, code, or environment.\n\n### Pattern 5: Use Version Control for Time Travel\n\n```bash\ngit log --oneline -10\ngit log --oneline --since=\"2026-02-02T13:00\"\ngit bisect start\ngit bisect bad HEAD\ngit bisect good \u003Clast-working-commit>\n```\n\n---\n\n## Troubleshooting Categories\n\n### 1. Code Errors (Runtime, Compile, Type)\n\n**Causes:** Null\u002Fundefined access, async timing issues, type mismatches, module not found  \n**Approach:** Read error carefully, check stack trace for file\u002Fline, search error code, isolate the function\n\n### 2. Performance Issues\n\n**Causes:** N+1 queries, slow renders, memory leaks, network latency  \n**Approach:** Profile the slow operation, identify bottleneck (database\u002FCPU\u002FI\u002FO\u002Fnetwork), optimize the bottleneck, measure before\u002Fafter\n\n### 3. Data Inconsistency\n\n**Causes:** Database out of sync, cache invalidation, race conditions, migration not applied  \n**Approach:** Compare DB state vs. expected, check last sync timestamp, verify integrity, re-run sync or migration\n\n### 4. Integration Failures\n\n**Causes:** API contract mismatch, auth failures, network connectivity, service downtime  \n**Approach:** Verify request format, check credentials, test API directly (curl\u002FPostman), check service status\n\n### 5. Environment-Specific Issues\n\n**Causes:** Missing\u002Fwrong env vars, path differences (Win\u002FMac\u002FLinux), dependency version conflicts, file permissions  \n**Approach:** Compare working vs. broken env, check env vars, verify dependency versions, check paths and permissions\n\n---\n\n## Quality Checklist\n\nBefore considering debugging complete:\n\n- [ ] Root cause identified (not just symptom fixed)\n- [ ] Hypothesis tested with evidence\n- [ ] Fix is minimal (don't over-engineer)\n- [ ] Original issue reproduced before fix\n- [ ] Fix resolves issue (not just hides it)\n- [ ] Edge cases tested\n- [ ] No regressions (other features still work)\n- [ ] Root cause, solution, and lessons learned documented\n\n---\n\n## Common Pitfalls to Avoid\n\n- **Shotgun debugging** — Change everything — one change, test, observe\n- **Ignoring error messages** — \"Probably network\" — read exact error, search it\n- **Fixing without testing** — Apply change, assume it works — reproduce, fix, re-test\n- **Assuming environment** — \"Works on my machine\" — verify in actual environment\n- **Blaming external deps** — \"Library is broken\" — verify your usage first\n\n---\n\n## Output\n\n- A Debug Report markdown file saved to the project's working directory or `docs\u002Fdebug\u002F`\n- Named: `[date]_[issue-slug]_debug.md`\n- Sections: Error Message, Stack Trace, Root Cause, Solution, Code Changes, Test Results, Lessons Learned\n\n---\n\n## Examples\n\n**Scenario 1:** \"Debug this error: TypeError: Cannot read property 'id' of undefined\" → Debug Report with hypothesis (null user object), test method (added logging), root cause confirmed, fix applied (null check), regression test documented\n\n**Scenario 2:** \"Why is this database query taking 8 seconds?\" → Debug Report using binary search on query complexity, EXPLAIN output showing missing index, index added, before\u002Fafter timing documented\n\n---\n\n## Edge Cases\n\n- **Error is intermittent (not reproducible):** Add logging around the suspected area, capture the next occurrence, treat the log as the reproduction case\n- **Issue only happens in production:** Create a minimal reproduction in dev using production-equivalent data and environment vars; document the environment delta\n- **Multiple simultaneous errors:** Prioritize by severity — fix the error that is blocking other fixes first; do not debug all at once\n\n---\n\n## Anti-Patterns\n\n- Changing multiple things at once before testing — makes it impossible to identify which change resolved the issue\n- Searching for the error message online before reading the stack trace — the stack trace almost always locates the cause; search is for when the trace is unhelpful\n- Marking a bug as fixed when tests pass but root cause was not confirmed — symptom masking produces the same bug later under different conditions\n- Writing a fix that hides the error (empty catch, fallback default) instead of addressing the cause\n\n---\n\n**Related Skills:**\n- `workspace-navigation` — When debugging collaborative workspaces\n- `repo-context-sync` — When debugging git integration issues\n- `web-research` — When searching error codes or similar issues online\n- `research-modes` — Deep investigation techniques\n\n---\n\n**Last Updated:** 2026-04-08\n**Maintained By:** Cipher\n**Status:** Active\n",{"name":5,"tier":56,"model":34,"agents":57,"inputs":59,"outputs":67,"category":71,"triggers":72,"description":7,"tool_dependencies":78},1,[58],"primary",[60,65],{"name":61,"type":62,"required":63,"description":64},"error_description","string",true,"Description of the error or failing behavior to debug",{"name":32,"type":62,"required":52,"description":66},"Additional context — stack traces, logs, reproduction steps",[68],{"name":69,"type":62,"description":70},"debug_report","Debug Report documenting root cause, fix applied, and lessons learned","continuous-learning",[73,74,75,76,77],"debug this error","why is this failing","investigate the issue","find the root cause","fix this bug systematically",[79],"file_system","main","ff07df5fd8f75762c2a131e6e26d297e8ae403ee","plugins\u002Fcontinuous-learning\u002Fskills\u002Fdebugging",0,"https:\u002F\u002Fgithub.com\u002FDojoGenesis\u002Fgateway","https:\u002F\u002Fgithub.com\u002FDojoGenesis","dojogenesis.com","2026-10-25 22:59:58",{"source":8,"skillName":5,"commands":89,"prompt":99,"zipAvailable":63},[90,93,96],{"tool":91,"command":92},"npx","npx skills add DojoGenesis\u002Fgateway --skill debugging",{"tool":94,"command":95},"bunx","bunx skills add DojoGenesis\u002Fgateway --skill debugging",{"tool":97,"command":98},"pnpm","pnpm dlx skills add DojoGenesis\u002Fgateway --skill debugging","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDojoGenesis\u002Fgateway\u002Fblob\u002Fmain\u002Fplugins\u002Fcontinuous-learning\u002Fskills\u002Fdebugging\u002FSKILL.md",[],[102,119,130,138,177,202],{"skillNo":103,"name":104,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":108,"publishedAt":51},"01M6P6J0WYSD1MTGA3ZX6MGGZ5","kata-test-echo","https:\u002F\u002Fgithub.com\u002FDojoGenesis\u002Fgateway\u002Fblob\u002Fmain\u002Fserver\u002Ftestdata\u002Fkata\u002Fskills\u002Fkata-test-echo\u002FSKILL.md",[107],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[109,110,111,112,113,114,115,116,117,118],"kata test echo","Echo","test","json","v1","output","input","structured","contracts","schema",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":126,"publishedAt":51},"01M6P6HQJNGG4WPZW0DEWMAY2N","kata-plain","An ordinary prose skill; not dispatchable.","https:\u002F\u002Fgithub.com\u002FDojoGenesis\u002Fgateway\u002Fblob\u002Fmain\u002Fserver\u002Ftestdata\u002Fkata\u002Fskills\u002Fkata-plain\u002FSKILL.md",[125],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[127,128,129],"kata plain","prose skill","prose",{"skillNo":131,"name":132,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":51},"01M6P6HH6Y7K8K6606MF7VZ1HB","kata-broken","https:\u002F\u002Fgithub.com\u002FDojoGenesis\u002Fgateway\u002Fblob\u002Fmain\u002Fserver\u002Ftestdata\u002Fkata\u002Fskills\u002Fkata-broken\u002FSKILL.md",[],[136,137,116,117,110,118,112,111,115,113,114],"kata broken","broken",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":156,"publishedAt":51},"01M6P6GW520QJ03A6K7Y5PWJ52","voice-before-structure","Read the project's design language and philosophy before writing structural artifacts. Ground manifests, READMEs, and descriptions in the project's voice, not boilerplate. Use when creating manifests or READMEs for established projects, writing ecosystem-level documentation, building plugin descriptions or marketplace metadata, or authoring metadata that carries a project's identity. Trigger phrases: 'write the manifest', 'create a README', 'describe this plugin', 'ground yourself in the philosophy', 'ecosystem-level work'.","https:\u002F\u002Fgithub.com\u002FDojoGenesis\u002Fgateway\u002Fblob\u002Fmain\u002Fplugins\u002Fwisdom-garden\u002Fskills\u002Fvoice-before-structure\u002FSKILL.md",[144,147,150,153],{"categoryNo":145,"categoryName":146,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":148,"categoryName":149,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":151,"categoryName":152,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000032","设计师",{"categoryNo":154,"categoryName":155,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000036","内容创作者",[157,158,159,160,161,162,163,164,165,166,167,168,169,170,171,172,173,174,175,176],"voice before structure","structure","voice","manifests","ecosystem","false","authoring","structural","project","artifact","philosophy","design","writing","identity","documentation","create","projects","work","read","write",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":184,"publishedAt":51},"01M6P6GMNA4HJ4D5RRM3BQZ73M","system-prompt-archaeology","Produces a named ADA disposition preset (YAML) and a layered behavioral analysis (structural decomposition + evidence-cited classifications) from a system prompt. Use when: \"analyze this system prompt\", \"extract disposition from prompt\", \"reverse-engineer agent behavior\", \"what patterns does this prompt use\", \"build a preset from this prompt\".","https:\u002F\u002Fgithub.com\u002FDojoGenesis\u002Fgateway\u002Fblob\u002Fmain\u002Fplugins\u002Fwisdom-garden\u002Fskills\u002Fsystem-prompt-archaeology\u002FSKILL.md",[183],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[185,186,187,43,188,189,164,190,191,192,193,194,195,196,197,198,199,34,200,201],"system prompt archaeology","system prompt","prompt","behavioral","classify","decomposition","wisdom","patterns","engineer","decompose","evidence","ada","analyze","analysis","STRING","true","reverse",{"skillNo":203,"name":204,"nameZh":6,"description":205,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":206,"categories":207,"keywords":209,"publishedAt":51},"01M6P6G2D70T9R00HX6K154X5Y","session-lifecycle-automation","Designs and configures all three loops of solo-operator session automation — session bookends, background maintenance agents, and a delegation flywheel. Use when setting up a new workspace, recovering from the 44% zero-artifact session leak, or preparing to scale delegation across multiple concurrent agents.","https:\u002F\u002Fgithub.com\u002FDojoGenesis\u002Fgateway\u002Fblob\u002Fmain\u002Fplugins\u002Fwisdom-garden\u002Fskills\u002Fsession-lifecycle-automation\u002FSKILL.md",[208],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[210,211,212,213,214,215,216,217,218,219,220,221,222,166,223,224,225,226,227,228],"automation","session lifecycle automation","session lifecycle","lifecycle","session","markdown","configure","directory","config","delegation","audit","SET","files","solo","across","scheduled","loops","up","template"]