# Extract Screenshot Features Into Task Lists

Screenshots often hide product requirements that are hard to convert into tasks. This skill extracts UI, interaction, and business features into organized development checklists.

## Install

```bash
npx skillstore add notedit/screenshot-feature-extractor
```

## Metadata

- Status: approved
- Slug: notedit-screenshot-feature-extractor
- Skillstore revision: r1
- Version status: missing
- Tree hash: 69dccf0eed726ac21a27ac4a38e74da52a2458b5b264100093492ce49c14f897
- Author: notedit
- GitHub username: notedit
- License: MIT
- Repository: https://github.com/notedit/happy-coding-agent/tree/main/skills/screenshot-feature-extractor
- Ref: 62e2a730c5cd74eab4c7164309d810de660fcea3
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 74
- Public page: https://skillstore.pages.dev/skills/notedit-screenshot-feature-extractor
- Manifest: https://skillstore.pages.dev/api/skills/notedit-screenshot-feature-extractor/manifest

## Capabilities

- Collects one or more user-provided screenshot paths and related context.
- Coordinates separate UI, interaction, and business analysis passes.
- Synthesizes analysis results into a unified development task list.
- Reviews the task list for completeness and quality issues.
- Formats output using the included task checklist reference.

## Use Cases

- Turn mockups into tasks: Convert a product design screenshot into modules, features, and small checklist items.
- Review competitor screens: Extract visible feature patterns from competitor screenshots for planning and gap analysis.
- Prepare implementation plans: Create a structured feature checklist before engineering starts from visual references.

## Prompt Templates

### Analyze one screenshot

```
Use this skill to analyze this screenshot: [path]. Create a feature checklist for the visible product screen.
```

### Compare several screens

```
Analyze these screenshots from the same product: [paths]. Deduplicate repeated features and produce one task list.
```

### Extract competitor features

```
Analyze these competitor screenshots: [paths]. Highlight visible features, unique interactions, and gaps we should consider.
```

### Create a reviewed implementation checklist

```
Analyze these product screenshots with context: [context]. Produce a reviewed checklist grouped by module and user workflow.
```

## Limitations

- Requires screenshots or image paths supplied by the user.
- Cannot verify features that are hidden outside the provided screens.
- Avoids technology stack recommendations by design.
- Quality depends on screenshot clarity and available product context.

## Best Practices

- Provide clear screenshot paths and short product context before starting analysis.
- Group related screens from the same product in one request.
- Review the generated checklist against real product goals before implementation.

## Anti Patterns

- Do not ask the skill to infer hidden backend behavior from one screen.
- Do not use low-quality screenshots for detailed interaction planning.
- Do not treat competitor screenshots as permission to copy protected assets.

## Security Audit

- Audited at: 2026-07-05T19:50:21.116\+00:00
- Summary: All static findings appear to be false positives. SKILL.md contains markdown diagrams and agent prompts, not executable shell commands. references/output-format.md is readable documentation, not obfuscated content.

## Stats

- Views: 240
- Downloads: 19
- Favorites: 0
- Popularity score: 0