Screenshot Analyzer (Multi-Agent)
SkillProductivityscreenshot-feature-extractor is a skill that lets an AI agent analyze product screenshots and extract feature lists from them. It can also generate development task checklists from UI designs, making it useful when turning app screens into PRD or task lists, batch analyzing multiple screens, or conducting competitive analysis.
Use Screenshot Analyzer (Multi-Agent) in Claude, ChatGPT or Ahel Desktop
Free. Sign in, add Screenshot Analyzer (Multi-Agent) and connect your AI. About a minute.
Also: Claude Code · Cursor · Codex
Then ask your AI: use the Screenshot Analyzer (Multi-Agent) skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; ahel provides instructions and does not run this skill.
No other account needed.
Have an AI agent that supports loading skills.
What your AI can do with it
- Analyze product screenshots to extract feature lists
- Generate development task checklists from UI designs
- Generate PRD and task lists from UI designs
- Batch analyze multiple app screens
- Conduct competitive analysis from competitor product screenshots
Getting started
- Have an AI agent that supports loading skills.
- Add the screenshot-feature-extractor skill to the agent.
- Provide product screenshots and ask the agent to extract features or generate a task checklist.
What this skill tells your AI
The instructions your AI receives, as published by davila7/claude-code-templates in cli-tool/components/skills/development/screenshot-feature-extractor/SKILL.md and read by ahel’s review.
Extract product features from UI screenshots using a coordinated multi-agent analysis pipeline.
Core principle: Describe WHAT to build (features/interactions), NOT HOW (no tech stack).
Multi-Agent Architecture
This skill orchestrates 5 specialized agents for comprehensive analysis:
┌─────────────────┐
│ Coordinator │
│ (this skill) │
└────────┬────────┘
│
┌───────────────────┼───────────────────┐
│ │ │
▼ ▼ ▼
┌─────────────────┐ ┌─────────────────┐ ┌─────────────────┐
│ UI Analyzer │ │ Interaction │ │ Business │
│ (parallel) │ │ Analyzer │ │ Analyzer │
│ │ │ (parallel) │ │ (parallel) │
└────────┬────────┘ └────────┬────────┘ └────────┬────────┘
│ │ │
└───────────────────┼───────────────────┘
▼
┌─────────────────┐
│ Synthesizer │
│ (sequential) │
└────────┬────────┘
│
▼
┌─────────────────┐
│ Reviewer │
│ (sequential) │
└─────────────────┘
Process
Phase 1: Screenshot Collection
Gather all screenshots to analyze:
- Read the screenshot file(s) provided by the user
- For each screenshot, note the file path and any context provided
- If multiple screenshots, determine if they are from the same product
Phase 2: Parallel Analysis
Launch THREE Task agents IN PARALLEL for each screenshot:
Agent 1: screenshot-ui-analyzer
Analyze this screenshot for UI components, layout structure, and design patterns.
Screenshot: [file path]
Return your analysis as JSON.
Agent 2: screenshot-interaction-analyzer
Analyze this screenshot for user interactions, navigation flows, and state transitions.
Screenshot: [file path]
Return your analysis as JSON.
Agent 3: screenshot-business-analyzer
Analyze this screenshot for business functions, data entities, and domain logic.
Screenshot: [file path]
Return your analysis as JSON.
IMPORTANT: Use the Task tool with THREE parallel calls in a single message to maximize efficiency.
Phase 3: Synthesis
After all parallel analyses complete, launch the synthesizer agent:
Agent 4: screenshot-synthesizer
Synthesize these analysis results into a unified development task list.
UI Analysis:
[paste UI analyzer result]
Interaction Analysis:
[paste Interaction analyzer result]
Business Analysis:
[paste Business analyzer result]
Product Name: [product name]
Output file: docs/plans/YYYY-MM-DD-<product>-features.md
Phase 4: Review
Launch the reviewer agent to validate the output:
Agent 5: screenshot-reviewer
Review this task list for completeness and quality.
Original screenshot(s): [file paths]
Task list: [synthesized output]
If issues found, provide corrections.
Phase 5: Output
- Write final task list to
docs/plans/YYYY-MM-DD-<product>-features.md - Use format from references/output-format.md
- Present summary to user
Key Guidelines
- Use
- [ ]checkbox format for all tasks - Break features into small, executable subtasks
- Focus on user interactions, not implementation details
- For multiple screenshots: deduplicate features across all screens
- For competitive analysis: highlight unique features and gaps
Benefits of Multi-Agent Approach
- Thoroughness - Three specialized perspectives catch more details
- Speed - Parallel analysis reduces total time
- Quality - Synthesis + Review ensures coherent, complete output
- Specialization - Each agent focuses on its domain expertise
Signals
- GitHub stars
- 32k
- Forks
- 4k
- Last commit
- Oct 2026
Questions
- When should this skill be used?
- Use it when analyzing competitor product screenshots for feature extraction, generating PRD or task lists from UI designs, batch analyzing multiple app screens, or conducting competitive analysis.
- What does it produce?
- It produces feature lists extracted from product screenshots and development task checklists generated from UI designs.
- Can it handle multiple screenshots at once?
- Yes, it supports batch analyzing multiple app screens.
Advanced
- Item type
- skill
- Key
screenshot-feature-extractor- Source
- github.com/davila7/claude-code-templates
github.com/davila7/claude-code-templates
More in Productivity
Skill · coreyhaines31
More in Productivitygws-calendar
Skill · googleworkspace
More in Productivitylark-workflow-standup-report
Skill · larksuite
More in Productivitywriting-plans
Skill · obra
More in Productivityenergy-procurement
Skill · affaan-m
More in Productivityhomelab-pihole-dns
Skill · affaan-m
More in Productivity