
Screenshot Feature Extractor
FreeExtract features from product screenshots efficiently.
Free · Opens the source repo
What Screenshot Feature Extractor does
The Screenshot Feature Extractor skill provides a structured approach to analyze product screenshots by extracting relevant features and generating actionable development task lists. This skill is particularly useful for product managers, designers, and developers looking to derive insights from visual references, whether for competitive analysis or for creating product requirement documents (PRDs). By leveraging a coordinated multi-agent analysis pipeline, users can gain a comprehensive understanding of UI components, user interactions, and business logic present in the screenshots.
The extraction process is divided into several phases. Initially, the skill collects screenshots and organizes them for analysis. It then employs three specialized agents that operate in parallel: the UI Analyzer focuses on layout and design patterns, the Interaction Analyzer assesses user navigation and interactions, and the Business Analyzer evaluates the underlying business functions. This parallel analysis ensures a thorough examination of each screenshot, capturing essential details that might be overlooked in a less structured approach.
Once the analyses are complete, the skill synthesizes the findings into a unified task list that is easy to understand and actionable. This task list is then reviewed for quality and completeness, ensuring that the final output is coherent and ready for implementation. The skill emphasizes breaking down features into small, executable subtasks, making it easier for development teams to prioritize and tackle them effectively.
Overall, the Screenshot Feature Extractor is designed for professionals who need to quickly analyze visual information and convert it into structured development tasks. Its multi-agent architecture not only enhances the thoroughness and speed of the analysis but also improves the quality of the output, making it a valuable tool in any product development workflow.
When to use it
Use this skill when you need to analyze multiple product screenshots for feature extraction or when generating task lists from UI designs.
When not to use it
This skill may not be suitable for real-time analysis or when detailed implementation guidance is required, as it focuses on feature extraction rather than technical specifics.
What you can build with it
Competitive Analysis
Use this skill to analyze screenshots of competitor products, extracting unique features and identifying gaps in your own offerings.
UI Design Review
Generate development task lists directly from your UI designs to streamline the transition from design to implementation.
Batch Processing Screenshots
Quickly analyze multiple screenshots from a product to create a comprehensive feature list for development planning.
How to install Screenshot Feature Extractor
View source1. Install with the skills CLI
npx skills add davila7/claude-code-templates/screenshot-feature-extractor --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by davila7Screenshot Analyzer (Multi-Agent)
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
Frequently asked questions about Screenshot Feature Extractor
Similar skills
Spring Boot Testing
Master testing techniques for Spring Boot 4 applications.
GitHub Issues
Manage GitHub issues efficiently with MCP tools.
Geofeed Tuner
Optimize your IP geolocation feeds in CSV format.
Batch Files
Master Windows batch scripting for automation and task management.
Adobe Illustrator Scripting
Automate your Illustrator workflows with ExtendScript.
Plugin Structure
Create and organize Claude Code plugins effectively.
