skill-visual-feedback

Process screenshot-based UI/UX feedback to fix visual issues — use when users share screenshots of bugs

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/skill-visual-feedback/SKILL.md

Quality

Content

48%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill lays out a clear, well-sequenced visual-feedback workflow with useful tool patterns, but it is weighed down by pervasive placeholder templates and inlined content that hurts token efficiency and progressive disclosure. Tightening the templates and moving reference material into bundle files would materially raise quality.

Suggestions

Replace placeholder scaffolding blocks ('[Issue 1]', '[File: file path]') with one concrete worked example per phase and trim the rest, to improve conciseness and actionability.

Move the Common Patterns examples, checkbox templates, and quick-reference tables into a references/ file linked from SKILL.md to improve progressive disclosure.

Add an automated verification step (e.g., a lint/build command or screenshot-diff check) to turn the manual checklist into an explicit validate-fix-retry feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is noticeably padded with placeholder template blocks ('[Issue 1: e.g., ...]', '[list specific styling issues]'), redundant checklists, and restated workflow sections that add tokens without new guidance.	2 / 5
Actionability	Provides concrete tool usage (Glob/Grep patterns, `npm run dev`, named tools) but most fix-plan code blocks are placeholder scaffolding rather than executable, copy-paste-ready instruction.	3 / 5
Workflow Clarity	A clear five-phase sequence with a scoping decision gate and a verification checklist plus user-confirmation loop; verification is a manual checklist rather than an automated validate-fix-retry loop, keeping it just below the top anchor.	4 / 5
Progressive Disclosure	Well-structured with clear headers and tables, but all ~270 lines are inlined in SKILL.md with no external references, and template-heavy sections that could be split out remain inline.	3 / 5
	Total	12 / 20 Passed

Description

82%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: it concisely states what the skill does and gives a concrete, natural trigger phrase. Its only weakness is limited enumeration of specific capabilities, which keeps specificity at the midpoint.

Suggestions

Expand the description with 2-3 more specific actions (e.g., 'identify inconsistent styling, locate offending components, and verify fixes across breakpoints') to raise specificity.

Add common synonyms users might say (e.g., 'mockups', 'UI screenshots', 'design feedback') to broaden trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('screenshot-based UI/UX feedback') and two concrete actions ('Process ... feedback', 'fix visual issues'), matching the anchor for 1-2 concrete actions but not comprehensive coverage.	3 / 5
Completeness	Explicitly answers both what ('Process screenshot-based UI/UX feedback to fix visual issues') and when ('use when users share screenshots of bugs') with a concrete trigger phrase.	5 / 5
Trigger Term Quality	Includes natural user phrases ('screenshots', 'UI/UX feedback', 'visual issues', 'users share screenshots of bugs') with good coverage, though a few synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (screenshot-driven visual fixes) with distinct triggers and minimal overlap risk against other skills.	5 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nyldn/claude-octopus
Path: .claude/skills/skill-visual-feedback/SKILL.md
Commit: 1bee725

Reviewed: ~12 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.