[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77ASG5CHE8B3K7QHTDKT392":3,"skill-same:01M77ASG5CHE8B3K7QHTDKT392":47},{"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":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M77ASG5CHE8B3K7QHTDKT392","debug-methodology",null,"Systematic debugging and problem-solving methodology. Activate when encountering unexpected errors, service failures, regression bugs, deployment issues, or when a fix attempt has failed twice. Also activate when proposing ANY fix to verify it addresses root cause (not a workaround). Prevents patch-chaining, wrong-environment restarts, workaround addiction, and \"drunk man\" random fixes.","Lord1Egypt\u002Fawesome-skill-forge","Lord1Egypt","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99746359?v=4","01M7592YDNT0XK9WJ0T2MQVPDN","Mohamed Mounir Ali AL Keshita","01M75GRFNHC8VZNWEB8DKDE433",3,"MIT","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Fd\u002Fdebug-methodology\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: debug-methodology\ndescription: Systematic debugging and problem-solving methodology. Activate when encountering unexpected errors, service failures, regression bugs, deployment issues, or when a fix attempt has failed twice. Also activate when proposing ANY fix to verify it addresses root cause (not a workaround). Prevents patch-chaining, wrong-environment restarts, workaround addiction, and \"drunk man\" random fixes.\n---\n\n# Debug Methodology\n\nSystematic approach to debugging and problem-solving. Distilled from real production incidents and industry best practices.\n\n## ⚠️ The Root Cause Imperative\n\n**Every fix MUST target the root cause. Workarounds are forbidden unless explicitly approved.**\n\nBefore proposing ANY solution, pass the Root Cause Gate:\n\n```\n┌─────────────────────────────────────────────┐\n│            ROOT CAUSE GATE                  │\n│                                             │\n│  1. What is the ACTUAL problem?             │\n│  2. WHY does it happen? (not just WHAT)     │\n│  3. Does my fix eliminate the WHY?           │\n│     YES → proceed                           │\n│     NO  → this is a workaround → STOP       │\n│                                             │\n│  Workaround test:                           │\n│  \"If I remove my fix, does the bug return?\" │\n│     YES → workaround (fix the cause instead)│\n│     NO  → genuine fix ✅                    │\n└─────────────────────────────────────────────┘\n```\n\n### The 5 Whys — Mandatory for Non-Obvious Problems\n\n```\nProblem: API returns 524 timeout\n  Why? → Cloudflare cuts connections >100s\n  Why? → The API call takes >100s\n  Why? → Using non-streaming request, server holds connection silent\n  Why? → Code uses regular fetch, not streaming\n  Fix: → Use streaming (server sends data continuously, Cloudflare won't cut)\n\n  ❌ WRONG: Switch to faster model (workaround — avoids the timeout instead of fixing it)\n  ✅ RIGHT: Use streaming API (root cause — Cloudflare needs ongoing data)\n```\n\n### Common Workaround Traps\n\n| Problem | Workaround (❌) | Root Cause Fix (✅) |\n|---------|----------------|-------------------|\n| API timeout | Switch to faster model | Use streaming \u002F fix the slow query |\n| Data precision loss | Search by name instead of ID | Fix BigInt parsing |\n| Search returns nothing | Try different search strategy | Fix the search implementation |\n| Dependency conflict | Downgrade \u002F pin version | Use correct environment (venv) |\n| Feature doesn't work | Remove the feature | Debug why it fails |\n\n**Self-check question**: \"Am I solving the problem, or avoiding it?\"\n\n## Phase 1: STOP — Assess Before Acting\n\nBefore ANY fix attempt:\n\n```\n□ What is the EXACT symptom? (error message, behavior, screenshot)\n□ When did it last work? What changed since then?\n□ How is the service running? (process, env, startup command)\n```\n\nFor running services:\n```bash\nps -p \u003CPID> -o command=        # How was it started?\nls .venv\u002F venv\u002F env\u002F           # Virtual environment?\nwhich python3 && python3 --version\nwhich node && node --version\n```\n\n**NEVER restart a service without first recording its original startup command.**\n\n## Phase 2: Hypothesize — Form ONE Theory\n\nPriority order:\n1. **Did I change something?** → diff\u002Frevert first\n2. **Did the environment change?** → versions, deps, configs\n3. **Did external inputs change?** → API responses, data formats\n4. **Genuine new bug?** → only after ruling out 1-3\n\n## Phase 3: Test — One Change at a Time\n\n```\nChange X → Test → Works? → Done\n                → Fails? → REVERT X → new hypothesis\n```\n\n**Do NOT stack changes.**\n\n## Phase 4: Patch-Chain Detection\n\n**2 fix attempts failed → STOP. Revert ALL. Back to Phase 1.**\n\nYou are likely:\n- Fixing symptoms of a wrong fix\n- In the wrong environment entirely\n- Misunderstanding the architecture\n\n## Phase 5: Post-Fix Verification\n\nAfter any fix, verify:\n```\n□ Does it solve the ORIGINAL problem? (not just silence the error)\n□ Did I introduce new issues? (regression check)\n□ Would removing my fix bring the bug back? (confirms causality)\n□ Is the fix in the right layer? (not patching symptoms upstream)\n```\n\n## Anti-Patterns\n\n### 🚨 Workaround Addiction (NEW — Most Common!)\nBypassing the problem instead of fixing it. \"It's slower but works\" \u002F \"Use a different approach\".\n→ **Ask: \"Am I solving or avoiding?\"** If avoiding → find the real fix.\n→ Workarounds are ONLY acceptable when: (1) explicitly approved by user, (2) clearly labeled as temporary, (3) a TODO is created for the real fix.\n\n### 🚨 Drunk Man Anti-Pattern\nRandomly changing things until the problem disappears.\n→ Each change needs a hypothesis.\n\n### 🚨 Streetlight Anti-Pattern\nLooking where comfortable, not where the problem is.\n→ \"Is this where the bug IS, or where I KNOW HOW TO LOOK?\"\n\n### 🚨 Cargo Cult Fix\nCopying a fix without understanding why it works.\n→ Understand the mechanism first.\n\n### 🚨 Ignoring the User\nUser says \"it broke after you changed X\" → immediately diff X.\n→ User observations are the most valuable data.\n\n## Environment Checklist\n\n```\n□ Runtime: system or venv\u002Fnvm?\n□ Dependencies: match expected versions?\n□ Config: .env, config.json — recent changes?\n□ Process manager: PM2\u002Fsystemd — restart method?\n□ Logs: tail -f before reproducing\n□ Backup: snapshot before any change\n```\n\n## Deployment Safety (Hardened SCP Flow)\n\n**Iron Rule: NEVER edit files directly on the server. NEVER overwrite server files without backup.**\n\n```\nStandard deployment (every time, no exceptions):\n\n1. PULL    scp server:\u002Fopt\u002Fapps\u002F项目\u002F .\u002Flocal-项目\u002F\n           (pull the files you need + related files)\n\n2. EDIT    Make changes locally\n           (complex multi-line → write full file, never sed)\n\n3. VERIFY  node -c *.js                    # syntax check\n           node -e \"require('.\u002Ffile')\"     # module load check\n           (STOP if verification fails — do not proceed)\n\n4. BACKUP  ssh server \"cp file file.bak.$(date +%s)\"\n\n5. PUSH    scp .\u002Flocal-file server:\u002Fopt\u002Fapps\u002F项目\u002Ffile\n\n6. RESTART pm2 restart \u003Capp>\n           (use SAME method as original — check ps\u002Fpm2 show first)\n\n7. HEALTH  curl -s http:\u002F\u002Flocalhost:\u003Cport>\u002Fhealth\n           pm2 logs \u003Capp> --lines 5 --nostream\n           (if unhealthy → revert backup immediately)\n```\n\n### Pull Scope Rules\n```\nChanging 1 file    → pull that file + its imports\u002Fimporters\nChanging routes    → also pull server.js (check mount points)\nChanging frontend  → also pull index.html (check script tags)\nChanging config    → also pull code that reads the config\nUnsure what to pull → pull the whole project directory\n```\n\n### What NOT to Do\n```\n❌ sed -i for multi-line code on server\n❌ Skip node -c after editing .js\n❌ pm2 restart before syntax verification\n❌ Tell user to refresh before health check passes\n❌ Push without backup\n```\n\n## 🚨 Server Code Modification Rules\n\n**Every code change on a server MUST be syntax-verified before restart\u002Freload.**\n\n```\nAfter editing .js files:\n  □ node -c \u003Cfile>                          # Syntax check\n  □ node -e \"require('.\u002F\u003Cfile>')\"           # Module load check (for route files)\n  □ FAIL → DO NOT restart. DO NOT tell user to refresh. Fix first.\n\nAfter editing .html files:\n  □ Check critical tag closure (div\u002Fscript\u002Fstyle)\n  □ grep -c '\u003Cdiv' file && grep -c '\u003C\u002Fdiv' file   # Count match\n\nComplex multi-line changes:\n  □ Write complete file locally → scp upload\n  □ NEVER use sed for multi-line code insertion (newlines get swallowed)\n  □ If sed is unavoidable → verify with node -c immediately after\n\nRestart sequence:\n  □ node -c *.js passes → pm2 restart \u003Capp>\n  □ Check pm2 logs --lines 5 for startup errors\n  □ curl health endpoint to confirm service is up\n```\n\n**Why**: `sed -i` multi-line insertion silently corrupts JS (newlines become single line), causing syntax errors that break the entire page with no visible error to the user.\n\n## Decision Tree\n\n```\nProblem appears\n  ├─ I just edited something? → DIFF → REVERT if suspect\n  ├─ Service won't start? → CHECK startup command + env\n  ├─ New error after fix? → STOP (patch chain!) → Revert → Phase 1\n  ├─ User reports regression? → DIFF before\u002Fafter\n  ├─ Tempted to work around? → ROOT CAUSE GATE → fix the real issue\n  └─ Intermittent? → CHECK logs + external deps + timing\n```\n","# Debug Methodology\n\nSystematic approach to debugging and problem-solving. Distilled from real production incidents and industry best practices.\n\n## ⚠️ The Root Cause Imperative\n\n**Every fix MUST target the root cause. Workarounds are forbidden unless explicitly approved.**\n\nBefore proposing ANY solution, pass the Root Cause Gate:\n\n```\n┌─────────────────────────────────────────────┐\n│            ROOT CAUSE GATE                  │\n│                                             │\n│  1. What is the ACTUAL problem?             │\n│  2. WHY does it happen? (not just WHAT)     │\n│  3. Does my fix eliminate the WHY?           │\n│     YES → proceed                           │\n│     NO  → this is a workaround → STOP       │\n│                                             │\n│  Workaround test:                           │\n│  \"If I remove my fix, does the bug return?\" │\n│     YES → workaround (fix the cause instead)│\n│     NO  → genuine fix ✅                    │\n└─────────────────────────────────────────────┘\n```\n\n### The 5 Whys — Mandatory for Non-Obvious Problems\n\n```\nProblem: API returns 524 timeout\n  Why? → Cloudflare cuts connections >100s\n  Why? → The API call takes >100s\n  Why? → Using non-streaming request, server holds connection silent\n  Why? → Code uses regular fetch, not streaming\n  Fix: → Use streaming (server sends data continuously, Cloudflare won't cut)\n\n  ❌ WRONG: Switch to faster model (workaround — avoids the timeout instead of fixing it)\n  ✅ RIGHT: Use streaming API (root cause — Cloudflare needs ongoing data)\n```\n\n### Common Workaround Traps\n\n| Problem | Workaround (❌) | Root Cause Fix (✅) |\n|---------|----------------|-------------------|\n| API timeout | Switch to faster model | Use streaming \u002F fix the slow query |\n| Data precision loss | Search by name instead of ID | Fix BigInt parsing |\n| Search returns nothing | Try different search strategy | Fix the search implementation |\n| Dependency conflict | Downgrade \u002F pin version | Use correct environment (venv) |\n| Feature doesn't work | Remove the feature | Debug why it fails |\n\n**Self-check question**: \"Am I solving the problem, or avoiding it?\"\n\n## Phase 1: STOP — Assess Before Acting\n\nBefore ANY fix attempt:\n\n```\n□ What is the EXACT symptom? (error message, behavior, screenshot)\n□ When did it last work? What changed since then?\n□ How is the service running? (process, env, startup command)\n```\n\nFor running services:\n```bash\nps -p \u003CPID> -o command=        # How was it started?\nls .venv\u002F venv\u002F env\u002F           # Virtual environment?\nwhich python3 && python3 --version\nwhich node && node --version\n```\n\n**NEVER restart a service without first recording its original startup command.**\n\n## Phase 2: Hypothesize — Form ONE Theory\n\nPriority order:\n1. **Did I change something?** → diff\u002Frevert first\n2. **Did the environment change?** → versions, deps, configs\n3. **Did external inputs change?** → API responses, data formats\n4. **Genuine new bug?** → only after ruling out 1-3\n\n## Phase 3: Test — One Change at a Time\n\n```\nChange X → Test → Works? → Done\n                → Fails? → REVERT X → new hypothesis\n```\n\n**Do NOT stack changes.**\n\n## Phase 4: Patch-Chain Detection\n\n**2 fix attempts failed → STOP. Revert ALL. Back to Phase 1.**\n\nYou are likely:\n- Fixing symptoms of a wrong fix\n- In the wrong environment entirely\n- Misunderstanding the architecture\n\n## Phase 5: Post-Fix Verification\n\nAfter any fix, verify:\n```\n□ Does it solve the ORIGINAL problem? (not just silence the error)\n□ Did I introduce new issues? (regression check)\n□ Would removing my fix bring the bug back? (confirms causality)\n□ Is the fix in the right layer? (not patching symptoms upstream)\n```\n\n## Anti-Patterns\n\n### 🚨 Workaround Addiction (NEW — Most Common!)\nBypassing the problem instead of fixing it. \"It's slower but works\" \u002F \"Use a different approach\".\n→ **Ask: \"Am I solving or avoiding?\"** If avoiding → find the real fix.\n→ Workarounds are ONLY acceptable when: (1) explicitly approved by user, (2) clearly labeled as temporary, (3) a TODO is created for the real fix.\n\n### 🚨 Drunk Man Anti-Pattern\nRandomly changing things until the problem disappears.\n→ Each change needs a hypothesis.\n\n### 🚨 Streetlight Anti-Pattern\nLooking where comfortable, not where the problem is.\n→ \"Is this where the bug IS, or where I KNOW HOW TO LOOK?\"\n\n### 🚨 Cargo Cult Fix\nCopying a fix without understanding why it works.\n→ Understand the mechanism first.\n\n### 🚨 Ignoring the User\nUser says \"it broke after you changed X\" → immediately diff X.\n→ User observations are the most valuable data.\n\n## Environment Checklist\n\n```\n□ Runtime: system or venv\u002Fnvm?\n□ Dependencies: match expected versions?\n□ Config: .env, config.json — recent changes?\n□ Process manager: PM2\u002Fsystemd — restart method?\n□ Logs: tail -f before reproducing\n□ Backup: snapshot before any change\n```\n\n## Deployment Safety (Hardened SCP Flow)\n\n**Iron Rule: NEVER edit files directly on the server. NEVER overwrite server files without backup.**\n\n```\nStandard deployment (every time, no exceptions):\n\n1. PULL    scp server:\u002Fopt\u002Fapps\u002F项目\u002F .\u002Flocal-项目\u002F\n           (pull the files you need + related files)\n\n2. EDIT    Make changes locally\n           (complex multi-line → write full file, never sed)\n\n3. VERIFY  node -c *.js                    # syntax check\n           node -e \"require('.\u002Ffile')\"     # module load check\n           (STOP if verification fails — do not proceed)\n\n4. BACKUP  ssh server \"cp file file.bak.$(date +%s)\"\n\n5. PUSH    scp .\u002Flocal-file server:\u002Fopt\u002Fapps\u002F项目\u002Ffile\n\n6. RESTART pm2 restart \u003Capp>\n           (use SAME method as original — check ps\u002Fpm2 show first)\n\n7. HEALTH  curl -s http:\u002F\u002Flocalhost:\u003Cport>\u002Fhealth\n           pm2 logs \u003Capp> --lines 5 --nostream\n           (if unhealthy → revert backup immediately)\n```\n\n### Pull Scope Rules\n```\nChanging 1 file    → pull that file + its imports\u002Fimporters\nChanging routes    → also pull server.js (check mount points)\nChanging frontend  → also pull index.html (check script tags)\nChanging config    → also pull code that reads the config\nUnsure what to pull → pull the whole project directory\n```\n\n### What NOT to Do\n```\n❌ sed -i for multi-line code on server\n❌ Skip node -c after editing .js\n❌ pm2 restart before syntax verification\n❌ Tell user to refresh before health check passes\n❌ Push without backup\n```\n\n## 🚨 Server Code Modification Rules\n\n**Every code change on a server MUST be syntax-verified before restart\u002Freload.**\n\n```\nAfter editing .js files:\n  □ node -c \u003Cfile>                          # Syntax check\n  □ node -e \"require('.\u002F\u003Cfile>')\"           # Module load check (for route files)\n  □ FAIL → DO NOT restart. DO NOT tell user to refresh. Fix first.\n\nAfter editing .html files:\n  □ Check critical tag closure (div\u002Fscript\u002Fstyle)\n  □ grep -c '\u003Cdiv' file && grep -c '\u003C\u002Fdiv' file   # Count match\n\nComplex multi-line changes:\n  □ Write complete file locally → scp upload\n  □ NEVER use sed for multi-line code insertion (newlines get swallowed)\n  □ If sed is unavoidable → verify with node -c immediately after\n\nRestart sequence:\n  □ node -c *.js passes → pm2 restart \u003Capp>\n  □ Check pm2 logs --lines 5 for startup errors\n  □ curl health endpoint to confirm service is up\n```\n\n**Why**: `sed -i` multi-line insertion silently corrupts JS (newlines become single line), causing syntax errors that break the entire page with no visible error to the user.\n\n## Decision Tree\n\n```\nProblem appears\n  ├─ I just edited something? → DIFF → REVERT if suspect\n  ├─ Service won't start? → CHECK startup command + env\n  ├─ New error after fix? → STOP (patch chain!) → Revert → Phase 1\n  ├─ User reports regression? → DIFF before\u002Fafter\n  ├─ Tempted to work around? → ROOT CAUSE GATE → fix the real issue\n  └─ Intermittent? → CHECK logs + external deps + timing\n```\n",{"name":5,"description":7},"master","4aa004da461d820f4ea5499e58eb8d196cf99016","community\u002Fclawhub\u002Fd\u002Fdebug-methodology",0,"https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge","https:\u002F\u002Fskill-explorer-rho.vercel.app","https:\u002F\u002Fgithub.com\u002FLord1Egypt","Unbreakable. Unstoppable. Unmatched⚡.\r\n Speaker of machine tongues 🤖  | World-builder of decentralized dreams 🌐 | Defender of the digital realm🛡️.","2026-06-10 08:21:01",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Lord1Egypt\u002Fawesome-skill-forge --skill debug-methodology",{"tool":39,"command":40},"bunx","bunx skills add Lord1Egypt\u002Fawesome-skill-forge --skill debug-methodology",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Lord1Egypt\u002Fawesome-skill-forge --skill debug-methodology","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Fd\u002Fdebug-methodology\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M785WKJB99G3STR1NF9NRTJW","youtube-content","YouTube transcripts to summaries, threads, blogs.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fyoutube-content\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M785WEFHB0G2S9YA6EPR3H0E","xurl","X\u002FTwitter via xurl CLI: post, search, DM, media, v2 API.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fxurl\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M785W98EDN4EFJXJPMQEHCRC","touchdesigner-mcp","Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftouchdesigner-mcp\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M785W5S9FP3QBH2V191E025P","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M785W2AS08NSSH9YATCV6FJB","teams-meeting-pipeline","Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fteams-meeting-pipeline\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M785VXKW4T34BTP1SCHW1R7F","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",[],[]]