[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CMS4QA54FFN6GS66RYYP3P":3,"skill-same:01M7CMS4QA54FFN6GS66RYYP3P":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},"01M7CMS4QA54FFN6GS66RYYP3P","screenshot-feature-extractor",null,"Analyze product screenshots to extract feature lists and generate development task checklists. Use when: (1) Analyzing competitor product screenshots for feature extraction, (2) Generating PRD\u002Ftask lists from UI designs, (3) Batch analyzing multiple app screens, (4) Conducting competitive analysis from visual references.","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\u002Fscreenshot-feature-extractor\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: screenshot-feature-extractor\ndescription: \"Analyze product screenshots to extract feature lists and generate development task checklists. Use when: (1) Analyzing competitor product screenshots for feature extraction, (2) Generating PRD\u002Ftask lists from UI designs, (3) Batch analyzing multiple app screens, (4) Conducting competitive analysis from visual references.\"\n---\n\n# Screenshot Analyzer (Multi-Agent)\n\nExtract product features from UI screenshots using a coordinated multi-agent analysis pipeline.\n\n**Core principle**: Describe WHAT to build (features\u002Finteractions), NOT HOW (no tech stack).\n\n## Multi-Agent Architecture\n\nThis skill orchestrates 5 specialized agents for comprehensive analysis:\n\n```\n                    ┌─────────────────┐\n                    │   Coordinator   │\n                    │   (this skill)  │\n                    └────────┬────────┘\n                             │\n         ┌───────────────────┼───────────────────┐\n         │                   │                   │\n         ▼                   ▼                   ▼\n┌─────────────────┐ ┌─────────────────┐ ┌─────────────────┐\n│  UI Analyzer    │ │  Interaction    │ │   Business      │\n│  (parallel)     │ │   Analyzer      │ │    Analyzer     │\n│                 │ │  (parallel)     │ │   (parallel)    │\n└────────┬────────┘ └────────┬────────┘ └────────┬────────┘\n         │                   │                   │\n         └───────────────────┼───────────────────┘\n                             ▼\n                    ┌─────────────────┐\n                    │   Synthesizer   │\n                    │   (sequential)  │\n                    └────────┬────────┘\n                             │\n                             ▼\n                    ┌─────────────────┐\n                    │    Reviewer     │\n                    │   (sequential)  │\n                    └─────────────────┘\n```\n\n## Process\n\n### Phase 1: Screenshot Collection\n\nGather all screenshots to analyze:\n1. Read the screenshot file(s) provided by the user\n2. For each screenshot, note the file path and any context provided\n3. If multiple screenshots, determine if they are from the same product\n\n### Phase 2: Parallel Analysis\n\nLaunch THREE Task agents IN PARALLEL for each screenshot:\n\n**Agent 1: screenshot-ui-analyzer**\n```\nAnalyze this screenshot for UI components, layout structure, and design patterns.\nScreenshot: [file path]\nReturn your analysis as JSON.\n```\n\n**Agent 2: screenshot-interaction-analyzer**\n```\nAnalyze this screenshot for user interactions, navigation flows, and state transitions.\nScreenshot: [file path]\nReturn your analysis as JSON.\n```\n\n**Agent 3: screenshot-business-analyzer**\n```\nAnalyze this screenshot for business functions, data entities, and domain logic.\nScreenshot: [file path]\nReturn your analysis as JSON.\n```\n\n**IMPORTANT**: Use the Task tool with THREE parallel calls in a single message to maximize efficiency.\n\n### Phase 3: Synthesis\n\nAfter all parallel analyses complete, launch the synthesizer agent:\n\n**Agent 4: screenshot-synthesizer**\n```\nSynthesize these analysis results into a unified development task list.\n\nUI Analysis:\n[paste UI analyzer result]\n\nInteraction Analysis:\n[paste Interaction analyzer result]\n\nBusiness Analysis:\n[paste Business analyzer result]\n\nProduct Name: [product name]\nOutput file: docs\u002Fplans\u002FYYYY-MM-DD-\u003Cproduct>-features.md\n```\n\n### Phase 4: Review\n\nLaunch the reviewer agent to validate the output:\n\n**Agent 5: screenshot-reviewer**\n```\nReview this task list for completeness and quality.\n\nOriginal screenshot(s): [file paths]\nTask list: [synthesized output]\n\nIf issues found, provide corrections.\n```\n\n### Phase 5: Output\n\n1. Write final task list to `docs\u002Fplans\u002FYYYY-MM-DD-\u003Cproduct>-features.md`\n2. Use format from [references\u002Foutput-format.md](references\u002Foutput-format.md)\n3. Present summary to user\n\n## Key Guidelines\n\n- Use `- [ ]` checkbox format for all tasks\n- Break features into small, executable subtasks\n- Focus on user interactions, not implementation details\n- For multiple screenshots: deduplicate features across all screens\n- For competitive analysis: highlight unique features and gaps\n\n## Benefits of Multi-Agent Approach\n\n1. **Thoroughness** - Three specialized perspectives catch more details\n2. **Speed** - Parallel analysis reduces total time\n3. **Quality** - Synthesis + Review ensures coherent, complete output\n4. **Specialization** - Each agent focuses on its domain expertise\n","# Screenshot Analyzer (Multi-Agent)\n\nExtract product features from UI screenshots using a coordinated multi-agent analysis pipeline.\n\n**Core principle**: Describe WHAT to build (features\u002Finteractions), NOT HOW (no tech stack).\n\n## Multi-Agent Architecture\n\nThis skill orchestrates 5 specialized agents for comprehensive analysis:\n\n```\n                    ┌─────────────────┐\n                    │   Coordinator   │\n                    │   (this skill)  │\n                    └────────┬────────┘\n                             │\n         ┌───────────────────┼───────────────────┐\n         │                   │                   │\n         ▼                   ▼                   ▼\n┌─────────────────┐ ┌─────────────────┐ ┌─────────────────┐\n│  UI Analyzer    │ │  Interaction    │ │   Business      │\n│  (parallel)     │ │   Analyzer      │ │    Analyzer     │\n│                 │ │  (parallel)     │ │   (parallel)    │\n└────────┬────────┘ └────────┬────────┘ └────────┬────────┘\n         │                   │                   │\n         └───────────────────┼───────────────────┘\n                             ▼\n                    ┌─────────────────┐\n                    │   Synthesizer   │\n                    │   (sequential)  │\n                    └────────┬────────┘\n                             │\n                             ▼\n                    ┌─────────────────┐\n                    │    Reviewer     │\n                    │   (sequential)  │\n                    └─────────────────┘\n```\n\n## Process\n\n### Phase 1: Screenshot Collection\n\nGather all screenshots to analyze:\n1. Read the screenshot file(s) provided by the user\n2. For each screenshot, note the file path and any context provided\n3. If multiple screenshots, determine if they are from the same product\n\n### Phase 2: Parallel Analysis\n\nLaunch THREE Task agents IN PARALLEL for each screenshot:\n\n**Agent 1: screenshot-ui-analyzer**\n```\nAnalyze this screenshot for UI components, layout structure, and design patterns.\nScreenshot: [file path]\nReturn your analysis as JSON.\n```\n\n**Agent 2: screenshot-interaction-analyzer**\n```\nAnalyze this screenshot for user interactions, navigation flows, and state transitions.\nScreenshot: [file path]\nReturn your analysis as JSON.\n```\n\n**Agent 3: screenshot-business-analyzer**\n```\nAnalyze this screenshot for business functions, data entities, and domain logic.\nScreenshot: [file path]\nReturn your analysis as JSON.\n```\n\n**IMPORTANT**: Use the Task tool with THREE parallel calls in a single message to maximize efficiency.\n\n### Phase 3: Synthesis\n\nAfter all parallel analyses complete, launch the synthesizer agent:\n\n**Agent 4: screenshot-synthesizer**\n```\nSynthesize these analysis results into a unified development task list.\n\nUI Analysis:\n[paste UI analyzer result]\n\nInteraction Analysis:\n[paste Interaction analyzer result]\n\nBusiness Analysis:\n[paste Business analyzer result]\n\nProduct Name: [product name]\nOutput file: docs\u002Fplans\u002FYYYY-MM-DD-\u003Cproduct>-features.md\n```\n\n### Phase 4: Review\n\nLaunch the reviewer agent to validate the output:\n\n**Agent 5: screenshot-reviewer**\n```\nReview this task list for completeness and quality.\n\nOriginal screenshot(s): [file paths]\nTask list: [synthesized output]\n\nIf issues found, provide corrections.\n```\n\n### Phase 5: Output\n\n1. Write final task list to `docs\u002Fplans\u002FYYYY-MM-DD-\u003Cproduct>-features.md`\n2. Use format from [references\u002Foutput-format.md](references\u002Foutput-format.md)\n3. Present summary to user\n\n## Key Guidelines\n\n- Use `- [ ]` checkbox format for all tasks\n- Break features into small, executable subtasks\n- Focus on user interactions, not implementation details\n- For multiple screenshots: deduplicate features across all screens\n- For competitive analysis: highlight unique features and gaps\n\n## Benefits of Multi-Agent Approach\n\n1. **Thoroughness** - Three specialized perspectives catch more details\n2. **Speed** - Parallel analysis reduces total time\n3. **Quality** - Synthesis + Review ensures coherent, complete output\n4. **Specialization** - Each agent focuses on its domain expertise\n",{"name":5,"description":7},"add-x-twitter-scraper-skill","7bc347b2f7dc2dde2761a965585925e0d0171748","cli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fscreenshot-feature-extractor",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 screenshot-feature-extractor",{"tool":38,"command":39},"bunx","bunx skills add Carchaloneo22\u002FClaude-Code-template --skill screenshot-feature-extractor",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Carchaloneo22\u002FClaude-Code-template --skill screenshot-feature-extractor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCarchaloneo22\u002FClaude-Code-template\u002Fblob\u002Fadd-x-twitter-scraper-skill\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fscreenshot-feature-extractor\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Foutput-format.md","REFERENCE","参考文档",2461,"https:\u002F\u002Fgithub.com\u002FCarchaloneo22\u002FClaude-Code-template\u002Fblob\u002Fadd-x-twitter-scraper-skill\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fscreenshot-feature-extractor\u002Freferences\u002Foutput-format.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",[],[]]