[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77JMMQMP7QMF6076SM2ER71":3,"skill-same:01M77JMMQMP7QMF6076SM2ER71":66},{"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":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M77JMMQMP7QMF6076SM2ER71","debug-like-expert",null,"Deep analysis debugging mode for complex issues. Activates methodical investigation protocol with evidence gathering, hypothesis testing, and rigorous verification. Use when standard troubleshooting fails or when issues require systematic root cause analysis.","Elad73\u002Fagentic-base-layer","Elad73","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F11886649?v=4","01M77JKHHH0GYX9ZBKNJ38QRAJ","EladRon","01M77JKHJNDTJ53993X2QNMHSG",0,"MIT","https:\u002F\u002Fgithub.com\u002FElad73\u002Fagentic-base-layer\u002Fblob\u002Fmain\u002Fglobal\u002Fskills\u002Fdebug-like-expert\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: debug-like-expert\ndescription: Deep analysis debugging mode for complex issues. Activates methodical investigation protocol with evidence gathering, hypothesis testing, and rigorous verification. Use when standard troubleshooting fails or when issues require systematic root cause analysis.\n---\n\n\u003Cobjective>\nDeep analysis debugging mode for complex issues. This skill activates methodical investigation protocols with evidence gathering, hypothesis testing, and rigorous verification when standard troubleshooting has failed.\n\nThe skill emphasizes treating code you wrote with MORE skepticism than unfamiliar code, as cognitive biases about \"how it should work\" can blind you to actual implementation errors. Use scientific method to systematically identify root causes rather than applying quick fixes.\n\u003C\u002Fobjective>\n\n\u003Ccontext_scan>\n**Run on every invocation to detect domain-specific debugging expertise:**\n\n```bash\n# What files are we debugging?\necho \"FILE_TYPES:\"\nfind . -maxdepth 2 -type f 2>\u002Fdev\u002Fnull | grep -E '\\.(py|js|jsx|ts|tsx|rs|swift|c|cpp|go|java)$' | head -10\n\n# Check for domain indicators\n[ -f \"package.json\" ] && echo \"DETECTED: JavaScript\u002FNode project\"\n[ -f \"Cargo.toml\" ] && echo \"DETECTED: Rust project\"\n[ -f \"setup.py\" ] || [ -f \"pyproject.toml\" ] && echo \"DETECTED: Python project\"\n[ -f \"*.xcodeproj\" ] || [ -f \"Package.swift\" ] && echo \"DETECTED: Swift\u002FmacOS project\"\n[ -f \"go.mod\" ] && echo \"DETECTED: Go project\"\n\n# Scan for any installed domain-expertise skills (optional)\necho \"DOMAIN_SKILLS:\"\nls ~\u002F.claude\u002Fskills\u002F 2>\u002Fdev\u002Fnull | head -10\n```\n\n**Present findings before starting investigation.**\n\u003C\u002Fcontext_scan>\n\n\u003Cdomain_expertise>\n**Optional: load a domain-expertise skill if one is installed.**\n\nIf you have a separate skill that bundles deep, domain-specific knowledge (debugging, testing, performance, common pitfalls for a particular stack), load it before investigation. This is a *soft* dependency — if no such skill is installed, proceed with the general debugging methodology below. Nothing here requires a domain skill to exist.\n\n\u003Cscan_domains>\nCheck whether any domain-expertise skill is available:\n```bash\nls ~\u002F.claude\u002Fskills\u002F 2>\u002Fdev\u002Fnull\n```\n\n**If no matching domain skill is found:** proceed without it (graceful degradation). This skill works fine with general debugging methodology alone.\n\u003C\u002Fscan_domains>\n\n\u003Cinference_rules>\nIf the user's description or codebase points at a specific stack (e.g. a Python game, a Rust systems program, a Swift app, a Next.js frontend, an Agent SDK project), and a matching domain-expertise skill happens to be installed, infer it and confirm:\n```\nDetected: [domain] issue → matching domain skill: [skill-name]\nLoad this debugging expertise? (Y \u002F proceed with general methodology)\n```\n\u003C\u002Finference_rules>\n\n\u003Cload_domain>\nIf a domain-expertise skill is installed and selected, read its references before investigating:\n```bash\ncat ~\u002F.claude\u002Fskills\u002F[domain-skill]\u002Freferences\u002F*.md 2>\u002Fdev\u002Fnull\n```\n\nThis loads comprehensive domain knowledge BEFORE investigation:\n- Common issues and error patterns\n- Domain-specific debugging tools and techniques\n- Testing and verification approaches\n- Performance profiling and optimization\n- Known pitfalls and anti-patterns\n- Platform-specific considerations\n\nAnnounce: \"Loaded [domain] expertise. Investigating with domain-specific context.\"\n\n**If no domain skill is installed:** proceed with the general methodology — do not block.\n\u003C\u002Fload_domain>\n\n\u003Cwhen_to_load>\nLoad domain expertise BEFORE investigation when the domain is known and a matching skill exists.\n\nDomain expertise is NOT needed for:\n- Pure logic bugs (domain-agnostic)\n- Generic algorithm issues\n- When the user explicitly says \"skip domain context\"\n\u003C\u002Fwhen_to_load>\n\u003C\u002Fdomain_expertise>\n\n\u003Ccontext>\nThis skill activates when standard troubleshooting has failed. The issue requires methodical investigation, not quick fixes. You are entering the mindset of a senior engineer who debugs with scientific rigor.\n\n**Important**: If you wrote or modified any of the code being debugged, you have cognitive biases about how it works. Your mental model of \"how it should work\" may be wrong. Treat code you wrote with MORE skepticism than unfamiliar code - you're blind to your own assumptions.\n\u003C\u002Fcontext>\n\n\u003Ccore_principle>\n**VERIFY, DON'T ASSUME.** Every hypothesis must be tested. Every \"fix\" must be validated. No solutions without evidence.\n\n**ESPECIALLY**: Code you designed or implemented is guilty until proven innocent. Your intent doesn't matter - only the code's actual behavior matters. Question your own design decisions as rigorously as you'd question anyone else's.\n\u003C\u002Fcore_principle>\n\n\u003Cquick_start>\n\n\u003Cevidence_gathering>\n\nBefore proposing any solution:\n\n**A. Document Current State**\n- What is the EXACT error message or unexpected behavior?\n- What are the EXACT steps to reproduce?\n- What is the ACTUAL output vs EXPECTED output?\n- When did this start working incorrectly (if known)?\n\n**B. Map the System**\n- Trace the execution path from entry point to failure point\n- Identify all components involved\n- Read relevant source files completely, not just scanning\n- Note dependencies, imports, configurations affecting this area\n\n**C. Gather External Knowledge (when needed)**\n- Use MCP servers for API documentation, library details, or domain knowledge\n- Use web search for error messages, framework-specific behaviors, or recent changes\n- Check official docs for intended behavior vs what you observe\n- Look for known issues, breaking changes, or version-specific quirks\n\nSee [references\u002Fwhen-to-research.md](references\u002Fwhen-to-research.md) for detailed guidance on research strategy.\n\n\u003C\u002Fevidence_gathering>\n\n\u003Croot_cause_analysis>\n\n**A. Form Hypotheses**\n\nBased on evidence, list possible causes:\n1. [Hypothesis 1] - because [specific evidence]\n2. [Hypothesis 2] - because [specific evidence]\n3. [Hypothesis 3] - because [specific evidence]\n\n**B. Test Each Hypothesis**\n\nFor each hypothesis:\n- What would prove this true?\n- What would prove this false?\n- Design a minimal test\n- Execute and document results\n\nSee [references\u002Fhypothesis-testing.md](references\u002Fhypothesis-testing.md) for scientific method application.\n\n**C. Eliminate or Confirm**\n\nDon't move forward until you can answer:\n- Which hypothesis is supported by evidence?\n- What evidence contradicts other hypotheses?\n- What additional information is needed?\n\n\u003C\u002Froot_cause_analysis>\n\n\u003Csolution_development>\n\n**Only after confirming root cause:**\n\n**A. Design Solution**\n- What is the MINIMAL change that addresses the root cause?\n- What are potential side effects?\n- What could this break?\n\n**B. Implement with Verification**\n- Make the change\n- Add logging\u002Fdebugging output if needed to verify behavior\n- Document why this change addresses the root cause\n\n**C. Test Thoroughly**\n- Does the original issue still occur?\n- Do the reproduction steps now work?\n- Run relevant tests if they exist\n- Check for regressions in related functionality\n\nSee [references\u002Fverification-patterns.md](references\u002Fverification-patterns.md) for comprehensive verification approaches.\n\n\u003C\u002Fsolution_development>\n\n\u003C\u002Fquick_start>\n\n\u003Ccritical_rules>\n\n1. **NO DRIVE-BY FIXES**: If you can't explain WHY a change works, don't make it\n2. **VERIFY EVERYTHING**: Test your assumptions. Read the actual code. Check the actual behavior\n3. **USE ALL TOOLS**:\n   - MCP servers for external knowledge\n   - Web search for error messages, docs, known issues\n   - Extended thinking (\"think deeply\") for complex reasoning\n   - File reading for complete context\n4. **THINK OUT LOUD**: Document your reasoning at each step\n5. **ONE VARIABLE**: Change one thing at a time, verify, then proceed\n6. **COMPLETE READS**: Don't skim code. Read entire relevant files\n7. **CHASE DEPENDENCIES**: If the issue involves libraries, configs, or external systems, investigate those too\n8. **QUESTION PREVIOUS WORK**: Maybe the earlier \"fix\" was wrong. Re-examine with fresh eyes\n\n\u003C\u002Fcritical_rules>\n\n\u003Csuccess_criteria>\n\nBefore starting:\n- [ ] Context scan executed to detect domain\n- [ ] Domain expertise loaded if available and relevant\n\nDuring investigation:\n- [ ] Do you understand WHY the issue occurred?\n- [ ] Have you verified the fix actually works?\n- [ ] Have you tested the original reproduction steps?\n- [ ] Have you checked for side effects?\n- [ ] Can you explain the solution to someone else?\n- [ ] Would this fix survive code review?\n\nIf you can't answer \"yes\" to all of these, keep investigating.\n\n**CRITICAL**: Do NOT mark debugging tasks as complete until this checklist passes.\n\n\u003C\u002Fsuccess_criteria>\n\n\u003Coutput_format>\n\n```markdown\n## Issue: [Problem Description]\n\n### Evidence\n[What you observed - exact errors, behaviors, outputs]\n\n### Investigation\n[What you checked, what you found, what you ruled out]\n\n### Root Cause\n[The actual underlying problem with evidence]\n\n### Solution\n[What you changed and WHY it addresses the root cause]\n\n### Verification\n[How you confirmed this works and doesn't break anything else]\n```\n\n\u003C\u002Foutput_format>\n\n\u003Cadvanced_topics>\n\nFor deeper topics, see reference files:\n\n**Debugging mindset**: [references\u002Fdebugging-mindset.md](references\u002Fdebugging-mindset.md)\n- First principles thinking applied to debugging\n- Cognitive biases that lead to bad fixes\n- The discipline of systematic investigation\n- When to stop and restart with fresh assumptions\n\n**Investigation techniques**: [references\u002Finvestigation-techniques.md](references\u002Finvestigation-techniques.md)\n- Binary search \u002F divide and conquer\n- Rubber duck debugging\n- Minimal reproduction\n- Working backwards from desired state\n- Adding observability before changing code\n\n**Hypothesis testing**: [references\u002Fhypothesis-testing.md](references\u002Fhypothesis-testing.md)\n- Forming falsifiable hypotheses\n- Designing experiments that prove\u002Fdisprove\n- What makes evidence strong vs weak\n- Recovering from wrong hypotheses gracefully\n\n**Verification patterns**: [references\u002Fverification-patterns.md](references\u002Fverification-patterns.md)\n- Definition of \"verified\" (not just \"it ran\")\n- Testing reproduction steps\n- Regression testing adjacent functionality\n- When to write tests before fixing\n\n**Research strategy**: [references\u002Fwhen-to-research.md](references\u002Fwhen-to-research.md)\n- Signals that you need external knowledge\n- What to search for vs what to reason about\n- Balancing research time vs experimentation\n\n\u003C\u002Fadvanced_topics>\n","\u003Cobjective>\nDeep analysis debugging mode for complex issues. This skill activates methodical investigation protocols with evidence gathering, hypothesis testing, and rigorous verification when standard troubleshooting has failed.\n\nThe skill emphasizes treating code you wrote with MORE skepticism than unfamiliar code, as cognitive biases about \"how it should work\" can blind you to actual implementation errors. Use scientific method to systematically identify root causes rather than applying quick fixes.\n\u003C\u002Fobjective>\n\n\u003Ccontext_scan>\n**Run on every invocation to detect domain-specific debugging expertise:**\n\n```bash\n# What files are we debugging?\necho \"FILE_TYPES:\"\nfind . -maxdepth 2 -type f 2>\u002Fdev\u002Fnull | grep -E '\\.(py|js|jsx|ts|tsx|rs|swift|c|cpp|go|java)$' | head -10\n\n# Check for domain indicators\n[ -f \"package.json\" ] && echo \"DETECTED: JavaScript\u002FNode project\"\n[ -f \"Cargo.toml\" ] && echo \"DETECTED: Rust project\"\n[ -f \"setup.py\" ] || [ -f \"pyproject.toml\" ] && echo \"DETECTED: Python project\"\n[ -f \"*.xcodeproj\" ] || [ -f \"Package.swift\" ] && echo \"DETECTED: Swift\u002FmacOS project\"\n[ -f \"go.mod\" ] && echo \"DETECTED: Go project\"\n\n# Scan for any installed domain-expertise skills (optional)\necho \"DOMAIN_SKILLS:\"\nls ~\u002F.claude\u002Fskills\u002F 2>\u002Fdev\u002Fnull | head -10\n```\n\n**Present findings before starting investigation.**\n\u003C\u002Fcontext_scan>\n\n\u003Cdomain_expertise>\n**Optional: load a domain-expertise skill if one is installed.**\n\nIf you have a separate skill that bundles deep, domain-specific knowledge (debugging, testing, performance, common pitfalls for a particular stack), load it before investigation. This is a *soft* dependency — if no such skill is installed, proceed with the general debugging methodology below. Nothing here requires a domain skill to exist.\n\n\u003Cscan_domains>\nCheck whether any domain-expertise skill is available:\n```bash\nls ~\u002F.claude\u002Fskills\u002F 2>\u002Fdev\u002Fnull\n```\n\n**If no matching domain skill is found:** proceed without it (graceful degradation). This skill works fine with general debugging methodology alone.\n\u003C\u002Fscan_domains>\n\n\u003Cinference_rules>\nIf the user's description or codebase points at a specific stack (e.g. a Python game, a Rust systems program, a Swift app, a Next.js frontend, an Agent SDK project), and a matching domain-expertise skill happens to be installed, infer it and confirm:\n```\nDetected: [domain] issue → matching domain skill: [skill-name]\nLoad this debugging expertise? (Y \u002F proceed with general methodology)\n```\n\u003C\u002Finference_rules>\n\n\u003Cload_domain>\nIf a domain-expertise skill is installed and selected, read its references before investigating:\n```bash\ncat ~\u002F.claude\u002Fskills\u002F[domain-skill]\u002Freferences\u002F*.md 2>\u002Fdev\u002Fnull\n```\n\nThis loads comprehensive domain knowledge BEFORE investigation:\n- Common issues and error patterns\n- Domain-specific debugging tools and techniques\n- Testing and verification approaches\n- Performance profiling and optimization\n- Known pitfalls and anti-patterns\n- Platform-specific considerations\n\nAnnounce: \"Loaded [domain] expertise. Investigating with domain-specific context.\"\n\n**If no domain skill is installed:** proceed with the general methodology — do not block.\n\u003C\u002Fload_domain>\n\n\u003Cwhen_to_load>\nLoad domain expertise BEFORE investigation when the domain is known and a matching skill exists.\n\nDomain expertise is NOT needed for:\n- Pure logic bugs (domain-agnostic)\n- Generic algorithm issues\n- When the user explicitly says \"skip domain context\"\n\u003C\u002Fwhen_to_load>\n\u003C\u002Fdomain_expertise>\n\n\u003Ccontext>\nThis skill activates when standard troubleshooting has failed. The issue requires methodical investigation, not quick fixes. You are entering the mindset of a senior engineer who debugs with scientific rigor.\n\n**Important**: If you wrote or modified any of the code being debugged, you have cognitive biases about how it works. Your mental model of \"how it should work\" may be wrong. Treat code you wrote with MORE skepticism than unfamiliar code - you're blind to your own assumptions.\n\u003C\u002Fcontext>\n\n\u003Ccore_principle>\n**VERIFY, DON'T ASSUME.** Every hypothesis must be tested. Every \"fix\" must be validated. No solutions without evidence.\n\n**ESPECIALLY**: Code you designed or implemented is guilty until proven innocent. Your intent doesn't matter - only the code's actual behavior matters. Question your own design decisions as rigorously as you'd question anyone else's.\n\u003C\u002Fcore_principle>\n\n\u003Cquick_start>\n\n\u003Cevidence_gathering>\n\nBefore proposing any solution:\n\n**A. Document Current State**\n- What is the EXACT error message or unexpected behavior?\n- What are the EXACT steps to reproduce?\n- What is the ACTUAL output vs EXPECTED output?\n- When did this start working incorrectly (if known)?\n\n**B. Map the System**\n- Trace the execution path from entry point to failure point\n- Identify all components involved\n- Read relevant source files completely, not just scanning\n- Note dependencies, imports, configurations affecting this area\n\n**C. Gather External Knowledge (when needed)**\n- Use MCP servers for API documentation, library details, or domain knowledge\n- Use web search for error messages, framework-specific behaviors, or recent changes\n- Check official docs for intended behavior vs what you observe\n- Look for known issues, breaking changes, or version-specific quirks\n\nSee [references\u002Fwhen-to-research.md](references\u002Fwhen-to-research.md) for detailed guidance on research strategy.\n\n\u003C\u002Fevidence_gathering>\n\n\u003Croot_cause_analysis>\n\n**A. Form Hypotheses**\n\nBased on evidence, list possible causes:\n1. [Hypothesis 1] - because [specific evidence]\n2. [Hypothesis 2] - because [specific evidence]\n3. [Hypothesis 3] - because [specific evidence]\n\n**B. Test Each Hypothesis**\n\nFor each hypothesis:\n- What would prove this true?\n- What would prove this false?\n- Design a minimal test\n- Execute and document results\n\nSee [references\u002Fhypothesis-testing.md](references\u002Fhypothesis-testing.md) for scientific method application.\n\n**C. Eliminate or Confirm**\n\nDon't move forward until you can answer:\n- Which hypothesis is supported by evidence?\n- What evidence contradicts other hypotheses?\n- What additional information is needed?\n\n\u003C\u002Froot_cause_analysis>\n\n\u003Csolution_development>\n\n**Only after confirming root cause:**\n\n**A. Design Solution**\n- What is the MINIMAL change that addresses the root cause?\n- What are potential side effects?\n- What could this break?\n\n**B. Implement with Verification**\n- Make the change\n- Add logging\u002Fdebugging output if needed to verify behavior\n- Document why this change addresses the root cause\n\n**C. Test Thoroughly**\n- Does the original issue still occur?\n- Do the reproduction steps now work?\n- Run relevant tests if they exist\n- Check for regressions in related functionality\n\nSee [references\u002Fverification-patterns.md](references\u002Fverification-patterns.md) for comprehensive verification approaches.\n\n\u003C\u002Fsolution_development>\n\n\u003C\u002Fquick_start>\n\n\u003Ccritical_rules>\n\n1. **NO DRIVE-BY FIXES**: If you can't explain WHY a change works, don't make it\n2. **VERIFY EVERYTHING**: Test your assumptions. Read the actual code. Check the actual behavior\n3. **USE ALL TOOLS**:\n   - MCP servers for external knowledge\n   - Web search for error messages, docs, known issues\n   - Extended thinking (\"think deeply\") for complex reasoning\n   - File reading for complete context\n4. **THINK OUT LOUD**: Document your reasoning at each step\n5. **ONE VARIABLE**: Change one thing at a time, verify, then proceed\n6. **COMPLETE READS**: Don't skim code. Read entire relevant files\n7. **CHASE DEPENDENCIES**: If the issue involves libraries, configs, or external systems, investigate those too\n8. **QUESTION PREVIOUS WORK**: Maybe the earlier \"fix\" was wrong. Re-examine with fresh eyes\n\n\u003C\u002Fcritical_rules>\n\n\u003Csuccess_criteria>\n\nBefore starting:\n- [ ] Context scan executed to detect domain\n- [ ] Domain expertise loaded if available and relevant\n\nDuring investigation:\n- [ ] Do you understand WHY the issue occurred?\n- [ ] Have you verified the fix actually works?\n- [ ] Have you tested the original reproduction steps?\n- [ ] Have you checked for side effects?\n- [ ] Can you explain the solution to someone else?\n- [ ] Would this fix survive code review?\n\nIf you can't answer \"yes\" to all of these, keep investigating.\n\n**CRITICAL**: Do NOT mark debugging tasks as complete until this checklist passes.\n\n\u003C\u002Fsuccess_criteria>\n\n\u003Coutput_format>\n\n```markdown\n## Issue: [Problem Description]\n\n### Evidence\n[What you observed - exact errors, behaviors, outputs]\n\n### Investigation\n[What you checked, what you found, what you ruled out]\n\n### Root Cause\n[The actual underlying problem with evidence]\n\n### Solution\n[What you changed and WHY it addresses the root cause]\n\n### Verification\n[How you confirmed this works and doesn't break anything else]\n```\n\n\u003C\u002Foutput_format>\n\n\u003Cadvanced_topics>\n\nFor deeper topics, see reference files:\n\n**Debugging mindset**: [references\u002Fdebugging-mindset.md](references\u002Fdebugging-mindset.md)\n- First principles thinking applied to debugging\n- Cognitive biases that lead to bad fixes\n- The discipline of systematic investigation\n- When to stop and restart with fresh assumptions\n\n**Investigation techniques**: [references\u002Finvestigation-techniques.md](references\u002Finvestigation-techniques.md)\n- Binary search \u002F divide and conquer\n- Rubber duck debugging\n- Minimal reproduction\n- Working backwards from desired state\n- Adding observability before changing code\n\n**Hypothesis testing**: [references\u002Fhypothesis-testing.md](references\u002Fhypothesis-testing.md)\n- Forming falsifiable hypotheses\n- Designing experiments that prove\u002Fdisprove\n- What makes evidence strong vs weak\n- Recovering from wrong hypotheses gracefully\n\n**Verification patterns**: [references\u002Fverification-patterns.md](references\u002Fverification-patterns.md)\n- Definition of \"verified\" (not just \"it ran\")\n- Testing reproduction steps\n- Regression testing adjacent functionality\n- When to write tests before fixing\n\n**Research strategy**: [references\u002Fwhen-to-research.md](references\u002Fwhen-to-research.md)\n- Signals that you need external knowledge\n- What to search for vs what to reason about\n- Balancing research time vs experimentation\n\n\u003C\u002Fadvanced_topics>\n",{"name":5,"description":7},"main","49131d07c65f27037f747a6e0ae748ff6f082fc1","global\u002Fskills\u002Fdebug-like-expert","https:\u002F\u002Fgithub.com\u002FElad73\u002Fagentic-base-layer","https:\u002F\u002Fgithub.com\u002FElad73","2026-06-23 00:00:33",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add Elad73\u002Fagentic-base-layer --skill debug-like-expert",{"tool":36,"command":37},"bunx","bunx skills add Elad73\u002Fagentic-base-layer --skill debug-like-expert",{"tool":39,"command":40},"pnpm","pnpm dlx skills add Elad73\u002Fagentic-base-layer --skill debug-like-expert","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FElad73\u002Fagentic-base-layer\u002Fblob\u002Fmain\u002Fglobal\u002Fskills\u002Fdebug-like-expert\u002FSKILL.md",true,[44,50,54,58,62],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"references\u002Fdebugging-mindset.md","REFERENCE","参考文档",8868,"https:\u002F\u002Fgithub.com\u002FElad73\u002Fagentic-base-layer\u002Fblob\u002Fmain\u002Fglobal\u002Fskills\u002Fdebug-like-expert\u002Freferences\u002Fdebugging-mindset.md",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fhypothesis-testing.md",12131,"https:\u002F\u002Fgithub.com\u002FElad73\u002Fagentic-base-layer\u002Fblob\u002Fmain\u002Fglobal\u002Fskills\u002Fdebug-like-expert\u002Freferences\u002Fhypothesis-testing.md",{"path":55,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Finvestigation-techniques.md",9909,"https:\u002F\u002Fgithub.com\u002FElad73\u002Fagentic-base-layer\u002Fblob\u002Fmain\u002Fglobal\u002Fskills\u002Fdebug-like-expert\u002Freferences\u002Finvestigation-techniques.md",{"path":59,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fverification-patterns.md",11204,"https:\u002F\u002Fgithub.com\u002FElad73\u002Fagentic-base-layer\u002Fblob\u002Fmain\u002Fglobal\u002Fskills\u002Fdebug-like-expert\u002Freferences\u002Fverification-patterns.md",{"path":63,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fwhen-to-research.md",10478,"https:\u002F\u002Fgithub.com\u002FElad73\u002Fagentic-base-layer\u002Fblob\u002Fmain\u002Fglobal\u002Fskills\u002Fdebug-like-expert\u002Freferences\u002Fwhen-to-research.md",[67,74,81,88,95,102],{"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},"01M77JNFJ3FH3RRX9PBVZKWDNG","wrap-up","Session-end safe closeout. Updates STATUS, verifies you are on a feature branch (never main), security-greps the diff for secrets, makes a conventional commit (no AI-tool mentions), then asks for approval before pushing and opening a PR. Use this to properly close a development session. Side-effecting and gated on explicit user approval; run explicitly.","https:\u002F\u002Fgithub.com\u002FElad73\u002Fagentic-base-layer\u002Fblob\u002Fmain\u002Fglobal\u002Fskills\u002Fwrap-up\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},"01M77JNBV46D0G35X0BPMQ69TY","wake-up","Session-start context sync. Reads project STATUS, git state, and runs a quick health check, then emits a short (\u003C15 line) announcement of where things stand and the single best next step. Use this at the beginning of a working session to re-establish context fast. Does NOT re-read CLAUDE.md (already in the system prompt). Read-only and fast.","https:\u002F\u002Fgithub.com\u002FElad73\u002Fagentic-base-layer\u002Fblob\u002Fmain\u002Fglobal\u002Fskills\u002Fwake-up\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},"01M77JN6N1R6M90B9BX5FAQGK7","station","End-of-session composition that chains retrospect → document → cleanup → wrap-up into one closeout pipeline. Use this to fully close a working session — capture learnings, sync docs, prune artifacts, then commit and open a PR — without forgetting a step. Side-effecting; honors each sub-skill's confirmation and approval gates. Run explicitly.","https:\u002F\u002Fgithub.com\u002FElad73\u002Fagentic-base-layer\u002Fblob\u002Fmain\u002Fglobal\u002Fskills\u002Fstation\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M77JN0GC9BTN7EZ68PSHRJHK","retrospect","Post-session learning capture. Mines the current conversation for reusable patterns, pitfalls, architecture decisions, performance and security insights, then appends them to the project knowledge registry. Use this at the end of a working session, after a bug is fixed, or after a non-obvious decision is made — so the next session starts smarter. Writes structured entries to .claude\u002Fknowledge\u002FREGISTRY.md.","https:\u002F\u002Fgithub.com\u002FElad73\u002Fagentic-base-layer\u002Fblob\u002Fmain\u002Fglobal\u002Fskills\u002Fretrospect\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M77JMWMCKNK9ZSK36X4T86V5","pre-ship","Mandatory pre-commit quality gates — type-check, lint, test, build — run in order and halting on the first failure. Use this BEFORE committing any change that touches application code, so failures are caught while context is still fresh instead of by CI. Surfaces the failing tool's verbatim error and refuses to proceed until gates pass.","https:\u002F\u002Fgithub.com\u002FElad73\u002Fagentic-base-layer\u002Fblob\u002Fmain\u002Fglobal\u002Fskills\u002Fpre-ship\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":19},"01M77JMQT8VRMA5H73X9887PJ4","document","Code-is-truth documentation sync. Detects drift between the codebase and project docs (STATUS.md, CLAUDE.md, README), then applies targeted edits so docs describe what the code actually is. Use this after shipping features, before a release, or when docs feel stale. Secret-scans every doc before writing. Makes small surgical edits, never wholesale rewrites.","https:\u002F\u002Fgithub.com\u002FElad73\u002Fagentic-base-layer\u002Fblob\u002Fmain\u002Fglobal\u002Fskills\u002Fdocument\u002FSKILL.md",[],[]]