[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CMBX4NFTF7XCJ245P94GA3":3,"skill-same:01M7CMBX4NFTF7XCJ245P94GA3":48},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7CMBX4NFTF7XCJ245P94GA3","clean-code",null,"Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments","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\u002Fclean-code\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: clean-code\ndescription: Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments\nallowed-tools: Read, Write, Edit\nversion: 2.0\npriority: CRITICAL\n---\n\n# Clean Code - Pragmatic AI Coding Standards\n\n> **CRITICAL SKILL** - Be **concise, direct, and solution-focused**.\n\n---\n\n## Core Principles\n\n| Principle | Rule |\n|-----------|------|\n| **SRP** | Single Responsibility - each function\u002Fclass does ONE thing |\n| **DRY** | Don't Repeat Yourself - extract duplicates, reuse |\n| **KISS** | Keep It Simple - simplest solution that works |\n| **YAGNI** | You Aren't Gonna Need It - don't build unused features |\n| **Boy Scout** | Leave code cleaner than you found it |\n\n---\n\n## Naming Rules\n\n| Element | Convention |\n|---------|------------|\n| **Variables** | Reveal intent: `userCount` not `n` |\n| **Functions** | Verb + noun: `getUserById()` not `user()` |\n| **Booleans** | Question form: `isActive`, `hasPermission`, `canEdit` |\n| **Constants** | SCREAMING_SNAKE: `MAX_RETRY_COUNT` |\n\n> **Rule:** If you need a comment to explain a name, rename it.\n\n---\n\n## Function Rules\n\n| Rule | Description |\n|------|-------------|\n| **Small** | Max 20 lines, ideally 5-10 |\n| **One Thing** | Does one thing, does it well |\n| **One Level** | One level of abstraction per function |\n| **Few Args** | Max 3 arguments, prefer 0-2 |\n| **No Side Effects** | Don't mutate inputs unexpectedly |\n\n---\n\n## Code Structure\n\n| Pattern | Apply |\n|---------|-------|\n| **Guard Clauses** | Early returns for edge cases |\n| **Flat > Nested** | Avoid deep nesting (max 2 levels) |\n| **Composition** | Small functions composed together |\n| **Colocation** | Keep related code close |\n\n---\n\n## AI Coding Style\n\n| Situation | Action |\n|-----------|--------|\n| User asks for feature | Write it directly |\n| User reports bug | Fix it, don't explain |\n| No clear requirement | Ask, don't assume |\n\n---\n\n## Anti-Patterns (DON'T)\n\n| ❌ Pattern | ✅ Fix |\n|-----------|-------|\n| Comment every line | Delete obvious comments |\n| Helper for one-liner | Inline the code |\n| Factory for 2 objects | Direct instantiation |\n| utils.ts with 1 function | Put code where used |\n| \"First we import...\" | Just write code |\n| Deep nesting | Guard clauses |\n| Magic numbers | Named constants |\n| God functions | Split by responsibility |\n\n---\n\n## 🔴 Before Editing ANY File (THINK FIRST!)\n\n**Before changing a file, ask yourself:**\n\n| Question | Why |\n|----------|-----|\n| **What imports this file?** | They might break |\n| **What does this file import?** | Interface changes |\n| **What tests cover this?** | Tests might fail |\n| **Is this a shared component?** | Multiple places affected |\n\n**Quick Check:**\n```\nFile to edit: UserService.ts\n└── Who imports this? → UserController.ts, AuthController.ts\n└── Do they need changes too? → Check function signatures\n```\n\n> 🔴 **Rule:** Edit the file + all dependent files in the SAME task.\n> 🔴 **Never leave broken imports or missing updates.**\n\n---\n\n## Summary\n\n| Do | Don't |\n|----|-------|\n| Write code directly | Write tutorials |\n| Let code self-document | Add obvious comments |\n| Fix bugs immediately | Explain the fix first |\n| Inline small things | Create unnecessary files |\n| Name things clearly | Use abbreviations |\n| Keep functions small | Write 100+ line functions |\n\n> **Remember: The user wants working code, not a programming lesson.**\n\n---\n\n## 🔴 Self-Check Before Completing (MANDATORY)\n\n**Before saying \"task complete\", verify:**\n\n| Check | Question |\n|-------|----------|\n| ✅ **Goal met?** | Did I do exactly what user asked? |\n| ✅ **Files edited?** | Did I modify all necessary files? |\n| ✅ **Code works?** | Did I test\u002Fverify the change? |\n| ✅ **No errors?** | Lint and TypeScript pass? |\n| ✅ **Nothing forgotten?** | Any edge cases missed? |\n\n> 🔴 **Rule:** If ANY check fails, fix it before completing.\n\n---\n\n## Verification Scripts (MANDATORY)\n\n> 🔴 **CRITICAL:** Each agent runs ONLY their own skill's scripts after completing work.\n\n### Agent → Script Mapping\n\n| Agent | Script | Command |\n|-------|--------|---------|\n| **frontend-specialist** | UX Audit | `python ~\u002F.claude\u002Fskills\u002Ffrontend-design\u002Fscripts\u002Fux_audit.py .` |\n| **frontend-specialist** | A11y Check | `python ~\u002F.claude\u002Fskills\u002Ffrontend-design\u002Fscripts\u002Faccessibility_checker.py .` |\n| **backend-specialist** | API Validator | `python ~\u002F.claude\u002Fskills\u002Fapi-patterns\u002Fscripts\u002Fapi_validator.py .` |\n| **mobile-developer** | Mobile Audit | `python ~\u002F.claude\u002Fskills\u002Fmobile-design\u002Fscripts\u002Fmobile_audit.py .` |\n| **database-architect** | Schema Validate | `python ~\u002F.claude\u002Fskills\u002Fdatabase-design\u002Fscripts\u002Fschema_validator.py .` |\n| **security-auditor** | Security Scan | `python ~\u002F.claude\u002Fskills\u002Fvulnerability-scanner\u002Fscripts\u002Fsecurity_scan.py .` |\n| **seo-specialist** | SEO Check | `python ~\u002F.claude\u002Fskills\u002Fseo-fundamentals\u002Fscripts\u002Fseo_checker.py .` |\n| **seo-specialist** | GEO Check | `python ~\u002F.claude\u002Fskills\u002Fgeo-fundamentals\u002Fscripts\u002Fgeo_checker.py .` |\n| **performance-optimizer** | Lighthouse | `python ~\u002F.claude\u002Fskills\u002Fperformance-profiling\u002Fscripts\u002Flighthouse_audit.py \u003Curl>` |\n| **test-engineer** | Test Runner | `python ~\u002F.claude\u002Fskills\u002Ftesting-patterns\u002Fscripts\u002Ftest_runner.py .` |\n| **test-engineer** | Playwright | `python ~\u002F.claude\u002Fskills\u002Fwebapp-testing\u002Fscripts\u002Fplaywright_runner.py \u003Curl>` |\n| **Any agent** | Lint Check | `python ~\u002F.claude\u002Fskills\u002Flint-and-validate\u002Fscripts\u002Flint_runner.py .` |\n| **Any agent** | Type Coverage | `python ~\u002F.claude\u002Fskills\u002Flint-and-validate\u002Fscripts\u002Ftype_coverage.py .` |\n| **Any agent** | i18n Check | `python ~\u002F.claude\u002Fskills\u002Fi18n-localization\u002Fscripts\u002Fi18n_checker.py .` |\n\n> ❌ **WRONG:** `test-engineer` running `ux_audit.py`\n> ✅ **CORRECT:** `frontend-specialist` running `ux_audit.py`\n\n---\n\n### 🔴 Script Output Handling (READ → SUMMARIZE → ASK)\n\n**When running a validation script, you MUST:**\n\n1. **Run the script** and capture ALL output\n2. **Parse the output** - identify errors, warnings, and passes\n3. **Summarize to user** in this format:\n\n```markdown\n## Script Results: [script_name.py]\n\n### ❌ Errors Found (X items)\n- [File:Line] Error description 1\n- [File:Line] Error description 2\n\n### ⚠️ Warnings (Y items)\n- [File:Line] Warning description\n\n### ✅ Passed (Z items)\n- Check 1 passed\n- Check 2 passed\n\n**Should I fix the X errors?**\n```\n\n4. **Wait for user confirmation** before fixing\n5. **After fixing** → Re-run script to confirm\n\n> 🔴 **VIOLATION:** Running script and ignoring output = FAILED task.\n> 🔴 **VIOLATION:** Auto-fixing without asking = Not allowed.\n> 🔴 **Rule:** Always READ output → SUMMARIZE → ASK → then fix.\n\n","# Clean Code - Pragmatic AI Coding Standards\n\n> **CRITICAL SKILL** - Be **concise, direct, and solution-focused**.\n\n---\n\n## Core Principles\n\n| Principle | Rule |\n|-----------|------|\n| **SRP** | Single Responsibility - each function\u002Fclass does ONE thing |\n| **DRY** | Don't Repeat Yourself - extract duplicates, reuse |\n| **KISS** | Keep It Simple - simplest solution that works |\n| **YAGNI** | You Aren't Gonna Need It - don't build unused features |\n| **Boy Scout** | Leave code cleaner than you found it |\n\n---\n\n## Naming Rules\n\n| Element | Convention |\n|---------|------------|\n| **Variables** | Reveal intent: `userCount` not `n` |\n| **Functions** | Verb + noun: `getUserById()` not `user()` |\n| **Booleans** | Question form: `isActive`, `hasPermission`, `canEdit` |\n| **Constants** | SCREAMING_SNAKE: `MAX_RETRY_COUNT` |\n\n> **Rule:** If you need a comment to explain a name, rename it.\n\n---\n\n## Function Rules\n\n| Rule | Description |\n|------|-------------|\n| **Small** | Max 20 lines, ideally 5-10 |\n| **One Thing** | Does one thing, does it well |\n| **One Level** | One level of abstraction per function |\n| **Few Args** | Max 3 arguments, prefer 0-2 |\n| **No Side Effects** | Don't mutate inputs unexpectedly |\n\n---\n\n## Code Structure\n\n| Pattern | Apply |\n|---------|-------|\n| **Guard Clauses** | Early returns for edge cases |\n| **Flat > Nested** | Avoid deep nesting (max 2 levels) |\n| **Composition** | Small functions composed together |\n| **Colocation** | Keep related code close |\n\n---\n\n## AI Coding Style\n\n| Situation | Action |\n|-----------|--------|\n| User asks for feature | Write it directly |\n| User reports bug | Fix it, don't explain |\n| No clear requirement | Ask, don't assume |\n\n---\n\n## Anti-Patterns (DON'T)\n\n| ❌ Pattern | ✅ Fix |\n|-----------|-------|\n| Comment every line | Delete obvious comments |\n| Helper for one-liner | Inline the code |\n| Factory for 2 objects | Direct instantiation |\n| utils.ts with 1 function | Put code where used |\n| \"First we import...\" | Just write code |\n| Deep nesting | Guard clauses |\n| Magic numbers | Named constants |\n| God functions | Split by responsibility |\n\n---\n\n## 🔴 Before Editing ANY File (THINK FIRST!)\n\n**Before changing a file, ask yourself:**\n\n| Question | Why |\n|----------|-----|\n| **What imports this file?** | They might break |\n| **What does this file import?** | Interface changes |\n| **What tests cover this?** | Tests might fail |\n| **Is this a shared component?** | Multiple places affected |\n\n**Quick Check:**\n```\nFile to edit: UserService.ts\n└── Who imports this? → UserController.ts, AuthController.ts\n└── Do they need changes too? → Check function signatures\n```\n\n> 🔴 **Rule:** Edit the file + all dependent files in the SAME task.\n> 🔴 **Never leave broken imports or missing updates.**\n\n---\n\n## Summary\n\n| Do | Don't |\n|----|-------|\n| Write code directly | Write tutorials |\n| Let code self-document | Add obvious comments |\n| Fix bugs immediately | Explain the fix first |\n| Inline small things | Create unnecessary files |\n| Name things clearly | Use abbreviations |\n| Keep functions small | Write 100+ line functions |\n\n> **Remember: The user wants working code, not a programming lesson.**\n\n---\n\n## 🔴 Self-Check Before Completing (MANDATORY)\n\n**Before saying \"task complete\", verify:**\n\n| Check | Question |\n|-------|----------|\n| ✅ **Goal met?** | Did I do exactly what user asked? |\n| ✅ **Files edited?** | Did I modify all necessary files? |\n| ✅ **Code works?** | Did I test\u002Fverify the change? |\n| ✅ **No errors?** | Lint and TypeScript pass? |\n| ✅ **Nothing forgotten?** | Any edge cases missed? |\n\n> 🔴 **Rule:** If ANY check fails, fix it before completing.\n\n---\n\n## Verification Scripts (MANDATORY)\n\n> 🔴 **CRITICAL:** Each agent runs ONLY their own skill's scripts after completing work.\n\n### Agent → Script Mapping\n\n| Agent | Script | Command |\n|-------|--------|---------|\n| **frontend-specialist** | UX Audit | `python ~\u002F.claude\u002Fskills\u002Ffrontend-design\u002Fscripts\u002Fux_audit.py .` |\n| **frontend-specialist** | A11y Check | `python ~\u002F.claude\u002Fskills\u002Ffrontend-design\u002Fscripts\u002Faccessibility_checker.py .` |\n| **backend-specialist** | API Validator | `python ~\u002F.claude\u002Fskills\u002Fapi-patterns\u002Fscripts\u002Fapi_validator.py .` |\n| **mobile-developer** | Mobile Audit | `python ~\u002F.claude\u002Fskills\u002Fmobile-design\u002Fscripts\u002Fmobile_audit.py .` |\n| **database-architect** | Schema Validate | `python ~\u002F.claude\u002Fskills\u002Fdatabase-design\u002Fscripts\u002Fschema_validator.py .` |\n| **security-auditor** | Security Scan | `python ~\u002F.claude\u002Fskills\u002Fvulnerability-scanner\u002Fscripts\u002Fsecurity_scan.py .` |\n| **seo-specialist** | SEO Check | `python ~\u002F.claude\u002Fskills\u002Fseo-fundamentals\u002Fscripts\u002Fseo_checker.py .` |\n| **seo-specialist** | GEO Check | `python ~\u002F.claude\u002Fskills\u002Fgeo-fundamentals\u002Fscripts\u002Fgeo_checker.py .` |\n| **performance-optimizer** | Lighthouse | `python ~\u002F.claude\u002Fskills\u002Fperformance-profiling\u002Fscripts\u002Flighthouse_audit.py \u003Curl>` |\n| **test-engineer** | Test Runner | `python ~\u002F.claude\u002Fskills\u002Ftesting-patterns\u002Fscripts\u002Ftest_runner.py .` |\n| **test-engineer** | Playwright | `python ~\u002F.claude\u002Fskills\u002Fwebapp-testing\u002Fscripts\u002Fplaywright_runner.py \u003Curl>` |\n| **Any agent** | Lint Check | `python ~\u002F.claude\u002Fskills\u002Flint-and-validate\u002Fscripts\u002Flint_runner.py .` |\n| **Any agent** | Type Coverage | `python ~\u002F.claude\u002Fskills\u002Flint-and-validate\u002Fscripts\u002Ftype_coverage.py .` |\n| **Any agent** | i18n Check | `python ~\u002F.claude\u002Fskills\u002Fi18n-localization\u002Fscripts\u002Fi18n_checker.py .` |\n\n> ❌ **WRONG:** `test-engineer` running `ux_audit.py`\n> ✅ **CORRECT:** `frontend-specialist` running `ux_audit.py`\n\n---\n\n### 🔴 Script Output Handling (READ → SUMMARIZE → ASK)\n\n**When running a validation script, you MUST:**\n\n1. **Run the script** and capture ALL output\n2. **Parse the output** - identify errors, warnings, and passes\n3. **Summarize to user** in this format:\n\n```markdown\n## Script Results: [script_name.py]\n\n### ❌ Errors Found (X items)\n- [File:Line] Error description 1\n- [File:Line] Error description 2\n\n### ⚠️ Warnings (Y items)\n- [File:Line] Warning description\n\n### ✅ Passed (Z items)\n- Check 1 passed\n- Check 2 passed\n\n**Should I fix the X errors?**\n```\n\n4. **Wait for user confirmation** before fixing\n5. **After fixing** → Re-run script to confirm\n\n> 🔴 **VIOLATION:** Running script and ignoring output = FAILED task.\n> 🔴 **VIOLATION:** Auto-fixing without asking = Not allowed.\n> 🔴 **Rule:** Always READ output → SUMMARIZE → ASK → then fix.\n\n",{"name":5,"version":14,"priority":24,"description":7,"allowed-tools":25},"CRITICAL","Read, Write, Edit","add-x-twitter-scraper-skill","7bc347b2f7dc2dde2761a965585925e0d0171748","cli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fclean-code",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":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Carchaloneo22\u002FClaude-Code-template --skill clean-code",{"tool":40,"command":41},"bunx","bunx skills add Carchaloneo22\u002FClaude-Code-template --skill clean-code",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Carchaloneo22\u002FClaude-Code-template --skill clean-code","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCarchaloneo22\u002FClaude-Code-template\u002Fblob\u002Fadd-x-twitter-scraper-skill\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fclean-code\u002FSKILL.md",true,[],[49,56,65,72,79,86],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"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":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":60,"licenseFileUrl":61,"sourceHtmlUrl":62,"categories":63,"keywords":64,"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":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"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":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"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":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"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",[],[]]