[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CM8GWJVTXDFWN97S5T0YCE":3,"skill-same:01M7CM8GWJVTXDFWN97S5T0YCE":52},{"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},"01M7CM8GWJVTXDFWN97S5T0YCE","agent-md-refactor",null,"Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.","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\u002Fagent-md-refactor\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: agent-md-refactor\ndescription: Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.\nlicense: MIT\n---\n\n# Agent MD Refactor\n\nRefactor bloated agent instruction files (AGENTS.md, CLAUDE.md, COPILOT.md, etc.) to follow **progressive disclosure principles** - keeping essentials at root and organizing the rest into linked, categorized files.\n\n---\n\n## Triggers\n\nUse this skill when:\n- \"refactor my AGENTS.md\" \u002F \"refactor my CLAUDE.md\"\n- \"split my agent instructions\"\n- \"organize my CLAUDE.md file\"\n- \"my AGENTS.md is too long\"\n- \"progressive disclosure for my instructions\"\n- \"clean up my agent config\"\n\n---\n\n## Quick Reference\n\n| Phase | Action | Output |\n|-------|--------|--------|\n| 1. Analyze | Find contradictions | List of conflicts to resolve |\n| 2. Extract | Identify essentials | Core instructions for root file |\n| 3. Categorize | Group remaining instructions | Logical categories |\n| 4. Structure | Create file hierarchy | Root + linked files |\n| 5. Prune | Flag for deletion | Redundant\u002Fvague instructions |\n\n---\n\n## Process\n\n### Phase 1: Find Contradictions\n\nIdentify any instructions that conflict with each other.\n\n**Look for:**\n- Contradictory style guidelines (e.g., \"use semicolons\" vs \"no semicolons\")\n- Conflicting workflow instructions\n- Incompatible tool preferences\n- Mutually exclusive patterns\n\n**For each contradiction found:**\n```markdown\n## Contradiction Found\n\n**Instruction A:** [quote]\n**Instruction B:** [quote]\n\n**Question:** Which should take precedence, or should both be conditional?\n```\n\nAsk the user to resolve before proceeding.\n\n---\n\n### Phase 2: Identify the Essentials\n\nExtract ONLY what belongs in the root agent file. The root should be minimal - information that applies to **every single task**.\n\n**Essential content (keep in root):**\n| Category | Example |\n|----------|---------|\n| Project description | One sentence: \"A React dashboard for analytics\" |\n| Package manager | Only if not npm (e.g., \"Uses pnpm\") |\n| Non-standard commands | Custom build\u002Ftest\u002Ftypecheck commands |\n| Critical overrides | Things that MUST override defaults |\n| Universal rules | Applies to 100% of tasks |\n\n**NOT essential (move to linked files):**\n- Language-specific conventions\n- Testing guidelines\n- Code style details\n- Framework patterns\n- Documentation standards\n- Git workflow details\n\n---\n\n### Phase 3: Group the Rest\n\nOrganize remaining instructions into logical categories.\n\n**Common categories:**\n| Category | Contents |\n|----------|----------|\n| `typescript.md` | TS conventions, type patterns, strict mode rules |\n| `testing.md` | Test frameworks, coverage, mocking patterns |\n| `code-style.md` | Formatting, naming, comments, structure |\n| `git-workflow.md` | Commits, branches, PRs, reviews |\n| `architecture.md` | Patterns, folder structure, dependencies |\n| `api-design.md` | REST\u002FGraphQL conventions, error handling |\n| `security.md` | Auth patterns, input validation, secrets |\n| `performance.md` | Optimization rules, caching, lazy loading |\n\n**Grouping rules:**\n1. Each file should be self-contained for its topic\n2. Aim for 3-8 files (not too granular, not too broad)\n3. Name files clearly: `{topic}.md`\n4. Include only actionable instructions\n\n---\n\n### Phase 4: Create the File Structure\n\n**Output structure:**\n```\nproject-root\u002F\n├── CLAUDE.md (or AGENTS.md)     # Minimal root with links\n└── .claude\u002F                      # Or docs\u002Fagent-instructions\u002F\n    ├── typescript.md\n    ├── testing.md\n    ├── code-style.md\n    ├── git-workflow.md\n    └── architecture.md\n```\n\n**Root file template:**\n```markdown\n# Project Name\n\nOne-sentence description of the project.\n\n## Quick Reference\n\n- **Package Manager:** pnpm\n- **Build:** `pnpm build`\n- **Test:** `pnpm test`\n- **Typecheck:** `pnpm typecheck`\n\n## Detailed Instructions\n\nFor specific guidelines, see:\n- [TypeScript Conventions](.claude\u002Ftypescript.md)\n- [Testing Guidelines](.claude\u002Ftesting.md)\n- [Code Style](.claude\u002Fcode-style.md)\n- [Git Workflow](.claude\u002Fgit-workflow.md)\n- [Architecture Patterns](.claude\u002Farchitecture.md)\n```\n\n**Each linked file template:**\n```markdown\n# {Topic} Guidelines\n\n## Overview\nBrief context for when these guidelines apply.\n\n## Rules\n\n### Rule Category 1\n- Specific, actionable instruction\n- Another specific instruction\n\n### Rule Category 2\n- Specific, actionable instruction\n\n## Examples\n\n### Good\n\\`\\`\\`typescript\n\u002F\u002F Example of correct pattern\n\\`\\`\\`\n\n### Avoid\n\\`\\`\\`typescript\n\u002F\u002F Example of what not to do\n\\`\\`\\`\n```\n\n---\n\n### Phase 5: Flag for Deletion\n\nIdentify instructions that should be removed entirely.\n\n**Delete if:**\n| Criterion | Example | Why Delete |\n|-----------|---------|------------|\n| Redundant | \"Use TypeScript\" (in a .ts project) | Agent already knows |\n| Too vague | \"Write clean code\" | Not actionable |\n| Overly obvious | \"Don't introduce bugs\" | Wastes context |\n| Default behavior | \"Use descriptive variable names\" | Standard practice |\n| Outdated | References deprecated APIs | No longer applies |\n\n**Output format:**\n```markdown\n## Flagged for Deletion\n\n| Instruction | Reason |\n|-------------|--------|\n| \"Write clean, maintainable code\" | Too vague to be actionable |\n| \"Use TypeScript\" | Redundant - project is already TS |\n| \"Don't commit secrets\" | Agent already knows this |\n| \"Follow best practices\" | Meaningless without specifics |\n```\n\n---\n\n## Execution Checklist\n\n```\n[ ] Phase 1: All contradictions identified and resolved\n[ ] Phase 2: Root file contains ONLY essentials\n[ ] Phase 3: All remaining instructions categorized\n[ ] Phase 4: File structure created with proper links\n[ ] Phase 5: Redundant\u002Fvague instructions removed\n[ ] Verify: Each linked file is self-contained\n[ ] Verify: Root file is under 50 lines\n[ ] Verify: All links work correctly\n```\n\n---\n\n## Anti-Patterns\n\n| Avoid | Why | Instead |\n|-------|-----|---------|\n| Keeping everything in root | Bloated, hard to maintain | Split into linked files |\n| Too many categories | Fragmentation | Consolidate related topics |\n| Vague instructions | Wastes tokens, no value | Be specific or delete |\n| Duplicating defaults | Agent already knows | Only override when needed |\n| Deep nesting | Hard to navigate | Flat structure with links |\n\n---\n\n## Examples\n\n### Before (Bloated Root)\n```markdown\n# CLAUDE.md\n\nThis is a React project.\n\n## Code Style\n- Use 2 spaces\n- Use semicolons\n- Prefer const over let\n- Use arrow functions\n... (200 more lines)\n\n## Testing\n- Use Jest\n- Coverage > 80%\n... (100 more lines)\n\n## TypeScript\n- Enable strict mode\n... (150 more lines)\n```\n\n### After (Progressive Disclosure)\n```markdown\n# CLAUDE.md\n\nReact dashboard for real-time analytics visualization.\n\n## Commands\n- `pnpm dev` - Start development server\n- `pnpm test` - Run tests with coverage\n- `pnpm build` - Production build\n\n## Guidelines\n- [Code Style](.claude\u002Fcode-style.md)\n- [Testing](.claude\u002Ftesting.md)\n- [TypeScript](.claude\u002Ftypescript.md)\n```\n\n---\n\n## Verification\n\nAfter refactoring, verify:\n\n1. **Root file is minimal** - Under 50 lines, only universal info\n2. **Links work** - All referenced files exist\n3. **No contradictions** - Instructions are consistent\n4. **Actionable content** - Every instruction is specific\n5. **Complete coverage** - No instructions were lost (unless flagged for deletion)\n6. **Self-contained files** - Each linked file stands alone\n\n---\n","# Agent MD Refactor\n\nRefactor bloated agent instruction files (AGENTS.md, CLAUDE.md, COPILOT.md, etc.) to follow **progressive disclosure principles** - keeping essentials at root and organizing the rest into linked, categorized files.\n\n---\n\n## Triggers\n\nUse this skill when:\n- \"refactor my AGENTS.md\" \u002F \"refactor my CLAUDE.md\"\n- \"split my agent instructions\"\n- \"organize my CLAUDE.md file\"\n- \"my AGENTS.md is too long\"\n- \"progressive disclosure for my instructions\"\n- \"clean up my agent config\"\n\n---\n\n## Quick Reference\n\n| Phase | Action | Output |\n|-------|--------|--------|\n| 1. Analyze | Find contradictions | List of conflicts to resolve |\n| 2. Extract | Identify essentials | Core instructions for root file |\n| 3. Categorize | Group remaining instructions | Logical categories |\n| 4. Structure | Create file hierarchy | Root + linked files |\n| 5. Prune | Flag for deletion | Redundant\u002Fvague instructions |\n\n---\n\n## Process\n\n### Phase 1: Find Contradictions\n\nIdentify any instructions that conflict with each other.\n\n**Look for:**\n- Contradictory style guidelines (e.g., \"use semicolons\" vs \"no semicolons\")\n- Conflicting workflow instructions\n- Incompatible tool preferences\n- Mutually exclusive patterns\n\n**For each contradiction found:**\n```markdown\n## Contradiction Found\n\n**Instruction A:** [quote]\n**Instruction B:** [quote]\n\n**Question:** Which should take precedence, or should both be conditional?\n```\n\nAsk the user to resolve before proceeding.\n\n---\n\n### Phase 2: Identify the Essentials\n\nExtract ONLY what belongs in the root agent file. The root should be minimal - information that applies to **every single task**.\n\n**Essential content (keep in root):**\n| Category | Example |\n|----------|---------|\n| Project description | One sentence: \"A React dashboard for analytics\" |\n| Package manager | Only if not npm (e.g., \"Uses pnpm\") |\n| Non-standard commands | Custom build\u002Ftest\u002Ftypecheck commands |\n| Critical overrides | Things that MUST override defaults |\n| Universal rules | Applies to 100% of tasks |\n\n**NOT essential (move to linked files):**\n- Language-specific conventions\n- Testing guidelines\n- Code style details\n- Framework patterns\n- Documentation standards\n- Git workflow details\n\n---\n\n### Phase 3: Group the Rest\n\nOrganize remaining instructions into logical categories.\n\n**Common categories:**\n| Category | Contents |\n|----------|----------|\n| `typescript.md` | TS conventions, type patterns, strict mode rules |\n| `testing.md` | Test frameworks, coverage, mocking patterns |\n| `code-style.md` | Formatting, naming, comments, structure |\n| `git-workflow.md` | Commits, branches, PRs, reviews |\n| `architecture.md` | Patterns, folder structure, dependencies |\n| `api-design.md` | REST\u002FGraphQL conventions, error handling |\n| `security.md` | Auth patterns, input validation, secrets |\n| `performance.md` | Optimization rules, caching, lazy loading |\n\n**Grouping rules:**\n1. Each file should be self-contained for its topic\n2. Aim for 3-8 files (not too granular, not too broad)\n3. Name files clearly: `{topic}.md`\n4. Include only actionable instructions\n\n---\n\n### Phase 4: Create the File Structure\n\n**Output structure:**\n```\nproject-root\u002F\n├── CLAUDE.md (or AGENTS.md)     # Minimal root with links\n└── .claude\u002F                      # Or docs\u002Fagent-instructions\u002F\n    ├── typescript.md\n    ├── testing.md\n    ├── code-style.md\n    ├── git-workflow.md\n    └── architecture.md\n```\n\n**Root file template:**\n```markdown\n# Project Name\n\nOne-sentence description of the project.\n\n## Quick Reference\n\n- **Package Manager:** pnpm\n- **Build:** `pnpm build`\n- **Test:** `pnpm test`\n- **Typecheck:** `pnpm typecheck`\n\n## Detailed Instructions\n\nFor specific guidelines, see:\n- [TypeScript Conventions](.claude\u002Ftypescript.md)\n- [Testing Guidelines](.claude\u002Ftesting.md)\n- [Code Style](.claude\u002Fcode-style.md)\n- [Git Workflow](.claude\u002Fgit-workflow.md)\n- [Architecture Patterns](.claude\u002Farchitecture.md)\n```\n\n**Each linked file template:**\n```markdown\n# {Topic} Guidelines\n\n## Overview\nBrief context for when these guidelines apply.\n\n## Rules\n\n### Rule Category 1\n- Specific, actionable instruction\n- Another specific instruction\n\n### Rule Category 2\n- Specific, actionable instruction\n\n## Examples\n\n### Good\n\\`\\`\\`typescript\n\u002F\u002F Example of correct pattern\n\\`\\`\\`\n\n### Avoid\n\\`\\`\\`typescript\n\u002F\u002F Example of what not to do\n\\`\\`\\`\n```\n\n---\n\n### Phase 5: Flag for Deletion\n\nIdentify instructions that should be removed entirely.\n\n**Delete if:**\n| Criterion | Example | Why Delete |\n|-----------|---------|------------|\n| Redundant | \"Use TypeScript\" (in a .ts project) | Agent already knows |\n| Too vague | \"Write clean code\" | Not actionable |\n| Overly obvious | \"Don't introduce bugs\" | Wastes context |\n| Default behavior | \"Use descriptive variable names\" | Standard practice |\n| Outdated | References deprecated APIs | No longer applies |\n\n**Output format:**\n```markdown\n## Flagged for Deletion\n\n| Instruction | Reason |\n|-------------|--------|\n| \"Write clean, maintainable code\" | Too vague to be actionable |\n| \"Use TypeScript\" | Redundant - project is already TS |\n| \"Don't commit secrets\" | Agent already knows this |\n| \"Follow best practices\" | Meaningless without specifics |\n```\n\n---\n\n## Execution Checklist\n\n```\n[ ] Phase 1: All contradictions identified and resolved\n[ ] Phase 2: Root file contains ONLY essentials\n[ ] Phase 3: All remaining instructions categorized\n[ ] Phase 4: File structure created with proper links\n[ ] Phase 5: Redundant\u002Fvague instructions removed\n[ ] Verify: Each linked file is self-contained\n[ ] Verify: Root file is under 50 lines\n[ ] Verify: All links work correctly\n```\n\n---\n\n## Anti-Patterns\n\n| Avoid | Why | Instead |\n|-------|-----|---------|\n| Keeping everything in root | Bloated, hard to maintain | Split into linked files |\n| Too many categories | Fragmentation | Consolidate related topics |\n| Vague instructions | Wastes tokens, no value | Be specific or delete |\n| Duplicating defaults | Agent already knows | Only override when needed |\n| Deep nesting | Hard to navigate | Flat structure with links |\n\n---\n\n## Examples\n\n### Before (Bloated Root)\n```markdown\n# CLAUDE.md\n\nThis is a React project.\n\n## Code Style\n- Use 2 spaces\n- Use semicolons\n- Prefer const over let\n- Use arrow functions\n... (200 more lines)\n\n## Testing\n- Use Jest\n- Coverage > 80%\n... (100 more lines)\n\n## TypeScript\n- Enable strict mode\n... (150 more lines)\n```\n\n### After (Progressive Disclosure)\n```markdown\n# CLAUDE.md\n\nReact dashboard for real-time analytics visualization.\n\n## Commands\n- `pnpm dev` - Start development server\n- `pnpm test` - Run tests with coverage\n- `pnpm build` - Production build\n\n## Guidelines\n- [Code Style](.claude\u002Fcode-style.md)\n- [Testing](.claude\u002Ftesting.md)\n- [TypeScript](.claude\u002Ftypescript.md)\n```\n\n---\n\n## Verification\n\nAfter refactoring, verify:\n\n1. **Root file is minimal** - Under 50 lines, only universal info\n2. **Links work** - All referenced files exist\n3. **No contradictions** - Instructions are consistent\n4. **Actionable content** - Every instruction is specific\n5. **Complete coverage** - No instructions were lost (unless flagged for deletion)\n6. **Self-contained files** - Each linked file stands alone\n\n---\n",{"name":5,"license":15,"description":7},"add-x-twitter-scraper-skill","7bc347b2f7dc2dde2761a965585925e0d0171748","cli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fagent-md-refactor",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 agent-md-refactor",{"tool":38,"command":39},"bunx","bunx skills add Carchaloneo22\u002FClaude-Code-template --skill agent-md-refactor",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Carchaloneo22\u002FClaude-Code-template --skill agent-md-refactor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCarchaloneo22\u002FClaude-Code-template\u002Fblob\u002Fadd-x-twitter-scraper-skill\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fagent-md-refactor\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"README.md","REFERENCE","参考文档",7326,"https:\u002F\u002Fgithub.com\u002FCarchaloneo22\u002FClaude-Code-template\u002Fblob\u002Fadd-x-twitter-scraper-skill\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fagent-md-refactor\u002FREADME.md",[53,60,69,76,83,90],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"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":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":64,"licenseFileUrl":65,"sourceHtmlUrl":66,"categories":67,"keywords":68,"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":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},"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":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},"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":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},"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":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"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",[],[]]