[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CMF63FJRQKQR5FMS2RH7EC":3,"skill-same:01M7CMF63FJRQKQR5FMS2RH7EC":100},{"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":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7CMF63FJRQKQR5FMS2RH7EC","Error Resolver",null,"Systematic error diagnosis and resolution using first-principle analysis. Use when encountering any error message, stack trace, or unexpected behavior. Supports replay functionality to record and reuse solutions.","Carchaloneo22\u002FClaude-Code-template","Carchaloneo22","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F159488757?v=4","01M7CK5MQXAFZE3W7SAP69KNYR","Carlos Chaparro","01M7CK5MRFE26CDPEQDN5RSQPK",2,"MIT","https:\u002F\u002Fgithub.com\u002FCarchaloneo22\u002FClaude-Code-template\u002Fblob\u002Fadd-x-twitter-scraper-skill\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ferror-resolver\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: Error Resolver\ndescription: Systematic error diagnosis and resolution using first-principle analysis. Use when encountering any error message, stack trace, or unexpected behavior. Supports replay functionality to record and reuse solutions.\n---\n\n# Error Resolver\n\nA first-principle approach to diagnosing and resolving errors across all languages and frameworks.\n\n## Core Philosophy\n\n**The 5-step Error Resolution Process:**\n\n```\n1. CLASSIFY  ->  2. PARSE  ->  3. MATCH  ->  4. ANALYZE  ->  5. RESOLVE\n     |              |             |             |              |\n  What type?    Extract key    Known       Root cause      Fix +\n               information    pattern?     analysis       Prevent\n```\n\n## Quick Start\n\nWhen you encounter an error:\n\n1. **Paste the full error** (including stack trace if available)\n2. **Provide context** (what were you trying to do?)\n3. **Share relevant code** (the file\u002Ffunction involved)\n\n## Error Classification Framework\n\n### Primary Categories\n\n| Category | Indicators | Common Causes |\n|----------|------------|---------------|\n| **Syntax** | Parse error, Unexpected token | Typos, missing brackets, invalid syntax |\n| **Type** | TypeError, type mismatch | Wrong data type, null\u002Fundefined access |\n| **Reference** | ReferenceError, NameError | Undefined variable, scope issues |\n| **Runtime** | RuntimeError, Exception | Logic errors, invalid operations |\n| **Network** | ECONNREFUSED, timeout, 4xx\u002F5xx | Connection issues, wrong URL, server down |\n| **Permission** | EACCES, PermissionError | File\u002Fdirectory access, sudo needed |\n| **Dependency** | ModuleNotFound, Cannot find module | Missing package, version mismatch |\n| **Configuration** | Config error, env missing | Wrong settings, missing env vars |\n| **Database** | Connection refused, query error | DB down, wrong credentials, bad query |\n| **Memory** | OOM, heap out of memory | Memory leak, large data processing |\n\n### Secondary Attributes\n\n- **Severity**: Fatal \u002F Error \u002F Warning \u002F Info\n- **Scope**: Build-time \u002F Runtime \u002F Test-time\n- **Origin**: User code \u002F Framework \u002F Third-party \u002F System\n\n## Analysis Workflow\n\n### Step 1: Classify\n\nIdentify the error category by examining:\n- Error name\u002Fcode (e.g., `ENOENT`, `TypeError`)\n- Error message keywords\n- Where it occurred (compile, runtime, test)\n\n### Step 2: Parse\n\nExtract key information:\n```\n- Error code: [specific code if any]\n- File path: [where the error originated]\n- Line number: [exact line if available]\n- Function\u002Fmethod: [context of the error]\n- Variable\u002Fvalue: [what was involved]\n- Stack trace depth: [how deep is the call stack]\n```\n\n### Step 3: Match Patterns\n\nCheck against known error patterns:\n- See `patterns\u002F` directory for language-specific patterns\n- Match error signatures to known solutions\n- Check replay history for previous solutions\n\n### Step 4: Root Cause Analysis\n\nApply the **5 Whys** technique:\n```\nError: Cannot read property 'name' of undefined\n  Why 1? -> user object is undefined\n  Why 2? -> API call returned null\n  Why 3? -> User ID doesn't exist in database\n  Why 4? -> ID was from stale cache\n  Why 5? -> Cache invalidation not implemented\n\nRoot Cause: Missing cache invalidation logic\n```\n\n### Step 5: Resolve\n\nGenerate actionable solution:\n1. **Immediate fix** - Get it working now\n2. **Proper fix** - The right way to solve it\n3. **Prevention** - How to avoid in the future\n\n## Output Format\n\nWhen resolving an error, provide:\n\n```\n## Error Diagnosis\n\n**Classification**: [Category] \u002F [Severity] \u002F [Scope]\n\n**Error Signature**:\n- Code: [error code]\n- Type: [error type]\n- Location: [file:line]\n\n## Root Cause\n\n[Explanation of why this error occurred]\n\n**Contributing Factors**:\n1. [Factor 1]\n2. [Factor 2]\n\n## Solution\n\n### Immediate Fix\n[Quick steps to resolve]\n\n### Code Change\n[Specific code to add\u002Fmodify]\n\n### Verification\n[How to verify the fix works]\n\n## Prevention\n\n[How to prevent this error in the future]\n\n## Replay Tag\n\n[Unique identifier for this solution - for future reference]\n```\n\n## Replay System\n\nThe replay system records successful solutions for future reference.\n\n### Recording a Solution\n\nAfter resolving an error, record it:\n\n```bash\n# Create solution record in project\nmkdir -p .claude\u002Ferror-solutions\n\n# Solution file format: [error-type]-[hash].yaml\n```\n\n### Solution Record Format\n\n```yaml\n# .claude\u002Ferror-solutions\u002F[error-signature].yaml\nid: \"nodejs-module-not-found-express\"\ncreated: \"2024-01-15T10:30:00Z\"\nupdated: \"2024-01-20T14:22:00Z\"\n\nerror:\n  type: \"dependency\"\n  category: \"ModuleNotFound\"\n  language: \"nodejs\"\n  pattern: \"Cannot find module 'express'\"\n  context: \"npm project, missing dependency\"\n\ndiagnosis:\n  root_cause: \"Package not installed or node_modules corrupted\"\n  factors:\n    - \"Missing npm install after git clone\"\n    - \"Corrupted node_modules directory\"\n    - \"Package not in package.json\"\n\nsolution:\n  immediate:\n    - \"Run: npm install express\"\n  proper:\n    - \"Check package.json has express listed\"\n    - \"Run: rm -rf node_modules && npm install\"\n  code_change: null\n\nverification:\n  - \"Run the application again\"\n  - \"Check express is in node_modules\"\n\nprevention:\n  - \"Add npm install to project setup docs\"\n  - \"Use npm ci in CI\u002FCD pipelines\"\n\nmetadata:\n  occurrences: 5\n  last_resolved: \"2024-01-20T14:22:00Z\"\n  success_rate: 1.0\n  tags: [\"nodejs\", \"npm\", \"dependency\"]\n```\n\n### Replay Lookup\n\nWhen encountering an error:\n1. Generate error signature from the error message\n2. Search `.claude\u002Ferror-solutions\u002F` for matching patterns\n3. If found, apply the recorded solution\n4. If new, proceed with full analysis and record the solution\n\n### Error Signature Generation\n\n```\nsignature = hash(\n  error_type +\n  error_code +\n  normalized_message +  # remove specific values\n  language +\n  framework\n)\n```\n\nExample transformations:\n- `Cannot find module 'express'` -> `Cannot find module '{module}'`\n- `TypeError: Cannot read property 'name' of undefined` -> `TypeError: Cannot read property '{prop}' of undefined`\n\n## Debug Commands\n\nUseful commands during debugging:\n\n### Node.js\n```bash\n# Verbose error output\nNODE_DEBUG=* node app.js\n\n# Memory debugging\nnode --inspect app.js\n\n# Check installed packages\nnpm ls [package-name]\n\n# Verify package.json\nnpm ls --depth=0\n```\n\n### Python\n```bash\n# Debug mode\npython -m pdb script.py\n\n# Check installed packages\npip show [package-name]\npip list\n```\n\n### General\n```bash\n# Check file permissions\nls -la [file]\n\n# Check port usage\nlsof -i :[port]\nnetstat -an | grep [port]\n\n# Check environment variables\nenv | grep [VAR_NAME]\nprintenv [VAR_NAME]\n\n# Check disk space\ndf -h\n\n# Check memory\nfree -m  # Linux\nvm_stat  # macOS\n```\n\n## Common Debugging Patterns\n\n### Pattern 1: Binary Search\nWhen the error location is unclear:\n1. Comment out half the code\n2. If error persists, it's in the remaining half\n3. Repeat until you find the exact line\n\n### Pattern 2: Minimal Reproduction\nCreate the smallest code that reproduces the error:\n1. Start with empty file\n2. Add code piece by piece\n3. Stop when error appears\n4. That's your minimal repro case\n\n### Pattern 3: Rubber Duck Debugging\nExplain the problem out loud (or to Claude):\n1. What should happen?\n2. What actually happens?\n3. What changed recently?\n4. What assumptions am I making?\n\n### Pattern 4: Git Bisect\nFind which commit introduced the bug:\n```bash\ngit bisect start\ngit bisect bad  # current commit is bad\ngit bisect good [last-known-good-commit]\n# Git will checkout commits for you to test\ngit bisect good\u002Fbad  # mark each as good or bad\ngit bisect reset  # when done\n```\n\n## Reference Files\n\n- **patterns\u002F** - Language-specific error patterns\n  - `nodejs.md` - Node.js common errors\n  - `python.md` - Python common errors\n  - `react.md` - React\u002FNext.js errors\n  - `database.md` - Database errors\n  - `docker.md` - Docker\u002Fcontainer errors\n  - `git.md` - Git errors\n  - `network.md` - Network\u002FAPI errors\n\n- **analysis\u002F** - Analysis methodologies\n  - `stack-trace.md` - Stack trace parsing guide\n  - `root-cause.md` - Root cause analysis techniques\n\n- **replay\u002F** - Replay system\n  - `solution-template.yaml` - Template for recording solutions\n","# Error Resolver\n\nA first-principle approach to diagnosing and resolving errors across all languages and frameworks.\n\n## Core Philosophy\n\n**The 5-step Error Resolution Process:**\n\n```\n1. CLASSIFY  ->  2. PARSE  ->  3. MATCH  ->  4. ANALYZE  ->  5. RESOLVE\n     |              |             |             |              |\n  What type?    Extract key    Known       Root cause      Fix +\n               information    pattern?     analysis       Prevent\n```\n\n## Quick Start\n\nWhen you encounter an error:\n\n1. **Paste the full error** (including stack trace if available)\n2. **Provide context** (what were you trying to do?)\n3. **Share relevant code** (the file\u002Ffunction involved)\n\n## Error Classification Framework\n\n### Primary Categories\n\n| Category | Indicators | Common Causes |\n|----------|------------|---------------|\n| **Syntax** | Parse error, Unexpected token | Typos, missing brackets, invalid syntax |\n| **Type** | TypeError, type mismatch | Wrong data type, null\u002Fundefined access |\n| **Reference** | ReferenceError, NameError | Undefined variable, scope issues |\n| **Runtime** | RuntimeError, Exception | Logic errors, invalid operations |\n| **Network** | ECONNREFUSED, timeout, 4xx\u002F5xx | Connection issues, wrong URL, server down |\n| **Permission** | EACCES, PermissionError | File\u002Fdirectory access, sudo needed |\n| **Dependency** | ModuleNotFound, Cannot find module | Missing package, version mismatch |\n| **Configuration** | Config error, env missing | Wrong settings, missing env vars |\n| **Database** | Connection refused, query error | DB down, wrong credentials, bad query |\n| **Memory** | OOM, heap out of memory | Memory leak, large data processing |\n\n### Secondary Attributes\n\n- **Severity**: Fatal \u002F Error \u002F Warning \u002F Info\n- **Scope**: Build-time \u002F Runtime \u002F Test-time\n- **Origin**: User code \u002F Framework \u002F Third-party \u002F System\n\n## Analysis Workflow\n\n### Step 1: Classify\n\nIdentify the error category by examining:\n- Error name\u002Fcode (e.g., `ENOENT`, `TypeError`)\n- Error message keywords\n- Where it occurred (compile, runtime, test)\n\n### Step 2: Parse\n\nExtract key information:\n```\n- Error code: [specific code if any]\n- File path: [where the error originated]\n- Line number: [exact line if available]\n- Function\u002Fmethod: [context of the error]\n- Variable\u002Fvalue: [what was involved]\n- Stack trace depth: [how deep is the call stack]\n```\n\n### Step 3: Match Patterns\n\nCheck against known error patterns:\n- See `patterns\u002F` directory for language-specific patterns\n- Match error signatures to known solutions\n- Check replay history for previous solutions\n\n### Step 4: Root Cause Analysis\n\nApply the **5 Whys** technique:\n```\nError: Cannot read property 'name' of undefined\n  Why 1? -> user object is undefined\n  Why 2? -> API call returned null\n  Why 3? -> User ID doesn't exist in database\n  Why 4? -> ID was from stale cache\n  Why 5? -> Cache invalidation not implemented\n\nRoot Cause: Missing cache invalidation logic\n```\n\n### Step 5: Resolve\n\nGenerate actionable solution:\n1. **Immediate fix** - Get it working now\n2. **Proper fix** - The right way to solve it\n3. **Prevention** - How to avoid in the future\n\n## Output Format\n\nWhen resolving an error, provide:\n\n```\n## Error Diagnosis\n\n**Classification**: [Category] \u002F [Severity] \u002F [Scope]\n\n**Error Signature**:\n- Code: [error code]\n- Type: [error type]\n- Location: [file:line]\n\n## Root Cause\n\n[Explanation of why this error occurred]\n\n**Contributing Factors**:\n1. [Factor 1]\n2. [Factor 2]\n\n## Solution\n\n### Immediate Fix\n[Quick steps to resolve]\n\n### Code Change\n[Specific code to add\u002Fmodify]\n\n### Verification\n[How to verify the fix works]\n\n## Prevention\n\n[How to prevent this error in the future]\n\n## Replay Tag\n\n[Unique identifier for this solution - for future reference]\n```\n\n## Replay System\n\nThe replay system records successful solutions for future reference.\n\n### Recording a Solution\n\nAfter resolving an error, record it:\n\n```bash\n# Create solution record in project\nmkdir -p .claude\u002Ferror-solutions\n\n# Solution file format: [error-type]-[hash].yaml\n```\n\n### Solution Record Format\n\n```yaml\n# .claude\u002Ferror-solutions\u002F[error-signature].yaml\nid: \"nodejs-module-not-found-express\"\ncreated: \"2024-01-15T10:30:00Z\"\nupdated: \"2024-01-20T14:22:00Z\"\n\nerror:\n  type: \"dependency\"\n  category: \"ModuleNotFound\"\n  language: \"nodejs\"\n  pattern: \"Cannot find module 'express'\"\n  context: \"npm project, missing dependency\"\n\ndiagnosis:\n  root_cause: \"Package not installed or node_modules corrupted\"\n  factors:\n    - \"Missing npm install after git clone\"\n    - \"Corrupted node_modules directory\"\n    - \"Package not in package.json\"\n\nsolution:\n  immediate:\n    - \"Run: npm install express\"\n  proper:\n    - \"Check package.json has express listed\"\n    - \"Run: rm -rf node_modules && npm install\"\n  code_change: null\n\nverification:\n  - \"Run the application again\"\n  - \"Check express is in node_modules\"\n\nprevention:\n  - \"Add npm install to project setup docs\"\n  - \"Use npm ci in CI\u002FCD pipelines\"\n\nmetadata:\n  occurrences: 5\n  last_resolved: \"2024-01-20T14:22:00Z\"\n  success_rate: 1.0\n  tags: [\"nodejs\", \"npm\", \"dependency\"]\n```\n\n### Replay Lookup\n\nWhen encountering an error:\n1. Generate error signature from the error message\n2. Search `.claude\u002Ferror-solutions\u002F` for matching patterns\n3. If found, apply the recorded solution\n4. If new, proceed with full analysis and record the solution\n\n### Error Signature Generation\n\n```\nsignature = hash(\n  error_type +\n  error_code +\n  normalized_message +  # remove specific values\n  language +\n  framework\n)\n```\n\nExample transformations:\n- `Cannot find module 'express'` -> `Cannot find module '{module}'`\n- `TypeError: Cannot read property 'name' of undefined` -> `TypeError: Cannot read property '{prop}' of undefined`\n\n## Debug Commands\n\nUseful commands during debugging:\n\n### Node.js\n```bash\n# Verbose error output\nNODE_DEBUG=* node app.js\n\n# Memory debugging\nnode --inspect app.js\n\n# Check installed packages\nnpm ls [package-name]\n\n# Verify package.json\nnpm ls --depth=0\n```\n\n### Python\n```bash\n# Debug mode\npython -m pdb script.py\n\n# Check installed packages\npip show [package-name]\npip list\n```\n\n### General\n```bash\n# Check file permissions\nls -la [file]\n\n# Check port usage\nlsof -i :[port]\nnetstat -an | grep [port]\n\n# Check environment variables\nenv | grep [VAR_NAME]\nprintenv [VAR_NAME]\n\n# Check disk space\ndf -h\n\n# Check memory\nfree -m  # Linux\nvm_stat  # macOS\n```\n\n## Common Debugging Patterns\n\n### Pattern 1: Binary Search\nWhen the error location is unclear:\n1. Comment out half the code\n2. If error persists, it's in the remaining half\n3. Repeat until you find the exact line\n\n### Pattern 2: Minimal Reproduction\nCreate the smallest code that reproduces the error:\n1. Start with empty file\n2. Add code piece by piece\n3. Stop when error appears\n4. That's your minimal repro case\n\n### Pattern 3: Rubber Duck Debugging\nExplain the problem out loud (or to Claude):\n1. What should happen?\n2. What actually happens?\n3. What changed recently?\n4. What assumptions am I making?\n\n### Pattern 4: Git Bisect\nFind which commit introduced the bug:\n```bash\ngit bisect start\ngit bisect bad  # current commit is bad\ngit bisect good [last-known-good-commit]\n# Git will checkout commits for you to test\ngit bisect good\u002Fbad  # mark each as good or bad\ngit bisect reset  # when done\n```\n\n## Reference Files\n\n- **patterns\u002F** - Language-specific error patterns\n  - `nodejs.md` - Node.js common errors\n  - `python.md` - Python common errors\n  - `react.md` - React\u002FNext.js errors\n  - `database.md` - Database errors\n  - `docker.md` - Docker\u002Fcontainer errors\n  - `git.md` - Git errors\n  - `network.md` - Network\u002FAPI errors\n\n- **analysis\u002F** - Analysis methodologies\n  - `stack-trace.md` - Stack trace parsing guide\n  - `root-cause.md` - Root cause analysis techniques\n\n- **replay\u002F** - Replay system\n  - `solution-template.yaml` - Template for recording solutions\n",{"name":5,"description":7},"add-x-twitter-scraper-skill","7bc347b2f7dc2dde2761a965585925e0d0171748","cli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ferror-resolver",0,"https:\u002F\u002Fgithub.com\u002FCarchaloneo22\u002FClaude-Code-template","https:\u002F\u002Fgithub.com\u002FCarchaloneo22","Ingeniero Informático | Ingeniero en Desarrollo de Software | Consultor TIC en Gestión Publica | Docente Análisis y Desarrollo de Software. ","2026-09-12 11:10:56",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Carchaloneo22\u002FClaude-Code-template --skill \"Error Resolver\"",{"tool":38,"command":39},"bunx","bunx skills add Carchaloneo22\u002FClaude-Code-template --skill \"Error Resolver\"",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Carchaloneo22\u002FClaude-Code-template --skill \"Error Resolver\"","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCarchaloneo22\u002FClaude-Code-template\u002Fblob\u002Fadd-x-twitter-scraper-skill\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ferror-resolver\u002FSKILL.md",true,[46,52,56,60,64,68,72,76,80,84,88,92,96],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"analysis\u002Froot-cause.md","REFERENCE","参考文档",7512,"https:\u002F\u002Fgithub.com\u002FCarchaloneo22\u002FClaude-Code-template\u002Fblob\u002Fadd-x-twitter-scraper-skill\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ferror-resolver\u002Fanalysis\u002Froot-cause.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"analysis\u002Fstack-trace.md",8158,"https:\u002F\u002Fgithub.com\u002FCarchaloneo22\u002FClaude-Code-template\u002Fblob\u002Fadd-x-twitter-scraper-skill\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ferror-resolver\u002Fanalysis\u002Fstack-trace.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"patterns\u002Fdatabase.md",10149,"https:\u002F\u002Fgithub.com\u002FCarchaloneo22\u002FClaude-Code-template\u002Fblob\u002Fadd-x-twitter-scraper-skill\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ferror-resolver\u002Fpatterns\u002Fdatabase.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"patterns\u002Fdocker.md",9294,"https:\u002F\u002Fgithub.com\u002FCarchaloneo22\u002FClaude-Code-template\u002Fblob\u002Fadd-x-twitter-scraper-skill\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ferror-resolver\u002Fpatterns\u002Fdocker.md",{"path":65,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":66,"sourceHtmlUrl":67},"patterns\u002Fgit.md",9158,"https:\u002F\u002Fgithub.com\u002FCarchaloneo22\u002FClaude-Code-template\u002Fblob\u002Fadd-x-twitter-scraper-skill\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ferror-resolver\u002Fpatterns\u002Fgit.md",{"path":69,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":70,"sourceHtmlUrl":71},"patterns\u002Fgo.md",9010,"https:\u002F\u002Fgithub.com\u002FCarchaloneo22\u002FClaude-Code-template\u002Fblob\u002Fadd-x-twitter-scraper-skill\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ferror-resolver\u002Fpatterns\u002Fgo.md",{"path":73,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":74,"sourceHtmlUrl":75},"patterns\u002Fnetwork.md",11835,"https:\u002F\u002Fgithub.com\u002FCarchaloneo22\u002FClaude-Code-template\u002Fblob\u002Fadd-x-twitter-scraper-skill\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ferror-resolver\u002Fpatterns\u002Fnetwork.md",{"path":77,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":78,"sourceHtmlUrl":79},"patterns\u002Fnodejs.md",10608,"https:\u002F\u002Fgithub.com\u002FCarchaloneo22\u002FClaude-Code-template\u002Fblob\u002Fadd-x-twitter-scraper-skill\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ferror-resolver\u002Fpatterns\u002Fnodejs.md",{"path":81,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":82,"sourceHtmlUrl":83},"patterns\u002Fpython.md",10768,"https:\u002F\u002Fgithub.com\u002FCarchaloneo22\u002FClaude-Code-template\u002Fblob\u002Fadd-x-twitter-scraper-skill\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ferror-resolver\u002Fpatterns\u002Fpython.md",{"path":85,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":86,"sourceHtmlUrl":87},"patterns\u002Freact.md",11410,"https:\u002F\u002Fgithub.com\u002FCarchaloneo22\u002FClaude-Code-template\u002Fblob\u002Fadd-x-twitter-scraper-skill\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ferror-resolver\u002Fpatterns\u002Freact.md",{"path":89,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":90,"sourceHtmlUrl":91},"patterns\u002Frust.md",10709,"https:\u002F\u002Fgithub.com\u002FCarchaloneo22\u002FClaude-Code-template\u002Fblob\u002Fadd-x-twitter-scraper-skill\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ferror-resolver\u002Fpatterns\u002Frust.md",{"path":93,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":94,"sourceHtmlUrl":95},"replay\u002FREADME.md",6710,"https:\u002F\u002Fgithub.com\u002FCarchaloneo22\u002FClaude-Code-template\u002Fblob\u002Fadd-x-twitter-scraper-skill\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ferror-resolver\u002Freplay\u002FREADME.md",{"path":97,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":98,"sourceHtmlUrl":99},"replay\u002Fsolution-template.yaml",2101,"https:\u002F\u002Fgithub.com\u002FCarchaloneo22\u002FClaude-Code-template\u002Fblob\u002Fadd-x-twitter-scraper-skill\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ferror-resolver\u002Freplay\u002Fsolution-template.yaml",[101,108,117,124,131,138],{"skillNo":102,"name":103,"nameZh":6,"description":104,"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":107,"publishedAt":19},"01M7CPQFVGKX7H3Q5Y9CN0XAZN","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.  This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power","https:\u002F\u002Fgithub.com\u002FCarchaloneo22\u002FClaude-Code-template\u002Fblob\u002Fadd-x-twitter-scraper-skill\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fzapier-make-patterns\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":112,"licenseFileUrl":113,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":19},"01M7CPQDR2HMKAYHAAY99EA4B2","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002FCarchaloneo22\u002FClaude-Code-template\u002Fblob\u002Fadd-x-twitter-scraper-skill\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FCarchaloneo22\u002FClaude-Code-template\u002Fblob\u002Fadd-x-twitter-scraper-skill\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":19},"01M7CPQ7K5MAQSXEB027HZFM2G","workflow-automation","Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, workflows resume exactly where they left off.  This skill covers the platforms (n8n, Temporal, Inngest) and patterns (sequential, parallel, orchestrator-worker) that turn brittle scripts into production-grade automation.  Key insight: The platforms make different tradeoffs. n8n optimizes for accessibility","https:\u002F\u002Fgithub.com\u002FCarchaloneo22\u002FClaude-Code-template\u002Fblob\u002Fadd-x-twitter-scraper-skill\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fworkflow-automation\u002FSKILL.md",[],[],{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":19},"01M7CPQ34F18JHMEM8NHQS1N7K","trigger-dev","Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. Use when: trigger.dev, trigger dev, background task, ai background job, long running task.","https:\u002F\u002Fgithub.com\u002FCarchaloneo22\u002FClaude-Code-template\u002Fblob\u002Fadd-x-twitter-scraper-skill\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Ftrigger-dev\u002FSKILL.md",[],[],{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":19},"01M7CPPZSXXDB1SAWT5N63ACZT","planning-with-files","Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.","https:\u002F\u002Fgithub.com\u002FCarchaloneo22\u002FClaude-Code-template\u002Fblob\u002Fadd-x-twitter-scraper-skill\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fplanning-with-files\u002FSKILL.md",[],[],{"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":144,"publishedAt":19},"01M7CPPTQSBVWSK0R10FJNMP0F","n8n-workflow-patterns","Proven workflow architectural patterns from real n8n workflows. Use when building new workflows, designing workflow structure, choosing workflow patterns, planning workflow architecture, or asking about webhook processing, HTTP API integration, database operations, AI agent workflows, or scheduled tasks.","https:\u002F\u002Fgithub.com\u002FCarchaloneo22\u002FClaude-Code-template\u002Fblob\u002Fadd-x-twitter-scraper-skill\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fn8n\u002Fn8n-workflow-patterns\u002FSKILL.md",[],[]]