Agent skill

Screenshot Feature Extractor

by davila7 in davila7/claude-code-templates

Analyze product screenshots to extract feature lists and generate development task checklists.

MITAuto-check passedFrontend & Design

Install Screenshot Feature Extractor

skills CLI
$ npx skills add davila7/claude-code-templates --skill screenshot-feature-extractor -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install davila7/claude-code-templates screenshot-feature-extractor --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/davila7/claude-code-templates.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cli-tool/components/skills/development/screenshot-feature-extractor .claude/skills/screenshot-feature-extractor && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
screenshot-feature-extractor
GitHub stars
33k
Used in
1 other repo
Token cost
~1.1k tokens
SKILL.md length
241 words
Files
2 (incl. references)
Skills in repo
479
Repo updated
First seen
Licence
MIT

At a glance

Analyze product screenshots to extract feature lists and generate development task checklists.

  • Works in 5 steps: Screenshot Collection → Parallel Analysis → Synthesis → …
  • Analyzing competitor product screenshots for feature extraction
  • SKILL.md covers Multi-Agent Architecture, Process, Key Guidelines and Benefits of Multi-Agent Approach
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Screenshot Feature Extractor is an agent skill from davila7/claude-code-templates. 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/task lists from UI designs, (3) Batch analyzing multiple app screens, (4) Conducting competitive analysis from visual references.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/output-format.md`).

It sits in Frontend & Design, covering Task breakdown, Competitor analysis and UI design. The repository describes itself as: CLI tool for configuring and monitoring Claude Code. The licence is MIT.

When your agent uses it

  • Analyzing competitor product screenshots for feature extraction
  • Generating PRD/task lists from UI designs
  • Batch analyzing multiple app screens
  • Conducting competitive analysis from visual references

Example prompts

  • “/screenshot-feature-extractor”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Screenshot Collection
  2. Parallel Analysis
  3. Synthesis
  4. Review
  5. Output

What it can do on your machine

Read from SKILL.md and the folder at commit c0ca7da. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Screenshot Feature Extractor loads about 1.1k tokens when it runs, and up to ~1.7k if it reads all its reference files. Until then it costs about 88 tokens; SKILL.md has 241 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~88
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from davila7/claude-code-templates at commit c0ca7da, republished under its MIT licence (© davila7). 241 words, ~1,110 tokens.

Download SKILL.mdSave it as .claude/skills/screenshot-feature-extractor/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
screenshot-feature-extractor
description
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/task lists from UI designs, (3) Batch analyzing multiple app screens, (4) Conducting competitive analysis from visual references.

Screenshot 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:

  1. Read the screenshot file(s) provided by the user
  2. For each screenshot, note the file path and any context provided
  3. 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
  1. Write final task list to docs/plans/YYYY-MM-DD-<product>-features.md
  2. Use format from references/output-format.md
  3. 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

  1. Thoroughness - Three specialized perspectives catch more details
  2. Speed - Parallel analysis reduces total time
  3. Quality - Synthesis + Review ensures coherent, complete output
  4. Specialization - Each agent focuses on its domain expertise

© davila7, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in cli-tool/components/skills/development/screenshot-feature-extractor of davila7/claude-code-templates.

  • SKILL.md
  • references/output-format.md

Open the folder on GitHubat commit c0ca7da

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in davila7/claude-code-templates, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Screenshot Feature Extractor next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Screenshot Feature Extractor compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Screenshot Feature Extractor this skilldavila7/claude-code-templates33k1 repos~1.1kAutomated safety check: PassMIT
Web Designxiaopu-ai/web-design783—~3kAutomated safety check: PassMIT
Design System Builderzebbern/claude-code-guide4.7k2 repos~1.7kAutomated safety check: PassMIT
Tasks Generatoraiskillstore/marketplace433—~1.1kAutomated safety check: PassNone
Spec App Consistency Auditleo-kuang-ai/spec-first107—~4.6kAutomated safety check: PassMIT
CCPM Project Managementautomazeio/ccpm8.4k—~1.1kAutomated safety check: PassMIT

Similar skills

  • Web Design

    xiaopu-ai/web-design

    Web 视觉设计 SKILL。输入 PRD / 参考 URL / 截图 / 关键词(任意组合),先产出一份标准化 DESIGN.md 设计规范,用户确认后据此生成 UI/UX、视觉、动效、响应式全部达标的 web 代码。专攻 web 端:Landing Page、Portfolio、产品页、博客、个人站、SaaS 介绍页等。当用户说"帮我做个网站""设计一个页面""参考 XX…

    783 GitHub stars~3k tokensUpdated 3 mo ago
    Frontend & DesignAuto-check passed
  • Design System Builder

    zebbern/claude-code-guide

    Extract design systems from reference UI images and generate implementation-ready UI design prompts.

    4.7k GitHub starsUsed in 2 repos~1.7k tokens
    Frontend & DesignAuto-check passed
  • Tasks Generator

    aiskillstore/marketplace

    Generate structured task roadmaps from project specifications.

    433 GitHub stars~1.1k tokensUpdated today
    Product & Project ManagementAuto-check passed
  • Spec App Consistency Audit

    leo-kuang-ai/spec-first

    Audit mobile App PRD/Figma/local-source consistency across page routes, KMP/Clean Architecture, components, analytics, i18n, engineering quality, and industry lenses before runtime validation; use…

    107 GitHub stars~4.6k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.

    8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed
  • Audits one product surface against its own design evidence and writes self-contained implementation plans for another agent, without touching product source.

    9.6k GitHub stars~2k tokensUpdated today
    Frontend & DesignAuto-check passed

More from davila7/claude-code-templates

All 479 skills in this repo
  • Perplexity Web Search

    davila7/claude-code-templates

    Runs web-grounded searches through Perplexity's Sonar models over OpenRouter for current events, recent literature and cited facts beyond the model's training cutoff.

    33k GitHub starsUsed in 11 repos~3.5k tokens
    Auto-check: notes
  • Neuropixels Data Analysis

    davila7/claude-code-templates

    Analyzes Neuropixels recordings from SpikeGLX or Open Ephys through preprocessing, drift correction, Kilosort4 spike sorting, quality metrics and curation.

    33k GitHub starsUsed in 9 repos~2.8k tokens
    Auto-check passed
  • Scientific Venue Templates

    davila7/claude-code-templates

    Supplies LaTeX templates and formatting rules for journals, conferences, posters, and grant proposals, then can check a draft against them.

    33k GitHub starsUsed in 9 repos~5.1k tokens
    Auto-check: notes
  • Brand Voice Content Creator

    davila7/claude-code-templates

    Analyzes a brand's existing writing to lock in a consistent voice, then builds SEO blog posts and platform-specific social content around it.

    33k GitHub starsUsed in 3 repos~1.9k tokens
    Auto-check passed
  • CAPA Officer

    davila7/claude-code-templates

    Guides corrective and preventive action (CAPA) work in a quality management system, from initiation and root cause analysis through effectiveness verification.

    33k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed
  • Fda Consultant Specialist

    davila7/claude-code-templates

    Senior FDA consultant and specialist for medical device companies including HIPAA compliance and requirement management.

    33k GitHub starsUsed in 1 repo~2.7k tokens
    Auto-check passed

Questions about Screenshot Feature Extractor

What does Screenshot Feature Extractor do?

Analyze product screenshots to extract feature lists and generate development task checklists. Screenshot Feature Extractor is an agent skill from davila7/claude-code-templates. Analyze product screenshots to extract feature lists and generate development task checklists.

When should I use Screenshot Feature Extractor?

Screenshot Feature Extractor fits situations like: analyzing competitor product screenshots for feature extraction; generating PRD/task lists from UI designs; batch analyzing multiple app screens; conducting competitive analysis from visual references.

How do I install Screenshot Feature Extractor in Claude Code?

Run `npx skills add davila7/claude-code-templates --skill screenshot-feature-extractor -a claude-code`. Or copy the skill folder (cli-tool/components/skills/development/screenshot-feature-extractor in davila7/claude-code-templates) into .claude/skills/screenshot-feature-extractor in your project. Claude Code loads it when a task matches its description.

How do I install Screenshot Feature Extractor in Codex?

Run `npx skills add davila7/claude-code-templates --skill screenshot-feature-extractor -a codex`. Or copy the skill folder (cli-tool/components/skills/development/screenshot-feature-extractor in davila7/claude-code-templates) into .agents/skills/screenshot-feature-extractor in your project. Codex loads it when a task matches its description.

Can I use Screenshot Feature Extractor in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add davila7/claude-code-templates --skill screenshot-feature-extractor -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/screenshot-feature-extractor, .gemini/skills/screenshot-feature-extractor, .github/skills/screenshot-feature-extractor and .opencode/skills/screenshot-feature-extractor in your project.

What does Screenshot Feature Extractor need to run?

SKILL.md names no scripts, command-line tools or credentials: Screenshot Feature Extractor is instructions for the agent only.

Does Screenshot Feature Extractor access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Screenshot Feature Extractor safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Screenshot Feature Extractor use?

Screenshot Feature Extractor is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Screenshot Feature Extractor use?

About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 616 tokens, read only when the agent opens those files.

What are the alternatives to Screenshot Feature Extractor?

Skills that share tags, products or a category with Screenshot Feature Extractor: Web Design (xiaopu-ai/web-design, 783 stars), Design System Builder (zebbern/claude-code-guide, 4.7k stars), Tasks Generator (aiskillstore/marketplace, 433 stars) and Spec App Consistency Audit (leo-kuang-ai/spec-first, 107 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Screenshot Feature Extractor?

davila7 (a GitHub user) maintains it in davila7/claude-code-templates, which has 32,512 GitHub stars. The repository holds 479 skills in this directory. The repository was last updated on October 10, 2026.

Source: davila7/claude-code-templates on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.