CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-visual-feedback

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

64

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

62%Weight 40%Scale 1-3

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

The skill has a clear, well-validated multi-phase workflow but is verbose and placeholder-heavy, with monolithic inlining of material that could be split into references. Actionability is mixed: search patterns are concrete while fix steps are templated.

Suggestions

Replace the many [placeholder] template markdown blocks with a single concrete worked example (real file paths, real before/after diffs) so the guidance is copy-paste-ready rather than fill-in-the-blanks.

Move the Common Patterns, Quick Reference tables, and verification checklists into reference files under references/ and link to them one level deep, reducing the SKILL.md body to a lean overview.

Tighten or remove the repetitive template scaffolding (e.g. repeated 'Fixing [Issue N]...' blocks) to respect the token budget and Claude's competence.

DimensionReasoningScore

Conciseness

The body is padded with many repetitive template markdown blocks full of [placeholder] text that Claude could generate itself; it avoids explaining known concepts but could be substantially tightened.

2 / 3

Actionability

Concrete Glob/Grep patterns and breakpoint ranges are given, but the implementation and fix-plan steps rely on placeholder pseudocode ('[file path]', '[what to change]') rather than executable, copy-paste-ready guidance.

2 / 3

Workflow Clarity

A clearly sequenced five-phase process with explicit verification (Phase 5 checklist) and a user-confirmation checkpoint, satisfying the validation requirement even for batch 'fix everywhere' operations.

3 / 3

Progressive Disclosure

Content is well-sectioned but monolithic at ~450 lines with no bundle files; the patterns, examples, and checklists that could live in separate references are all inlined.

2 / 3

Total

9

/

12

Passed

Description

90%Weight 40%Scale 1-3

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

A concise, third-person description that answers both 'what' and 'when' with a clear explicit trigger clause and low conflict risk. It could name more concrete actions to lift specificity.

DimensionReasoningScore

Specificity

Names the domain ('screenshot-based UI/UX feedback') and actions ('Process ... to fix visual issues'), but the verbs are generic rather than enumerating multiple concrete actions, so it falls short of a 3.

2 / 3

Completeness

States both what it does ('Process ... to fix visual issues') and when to use it via an explicit 'use when users share screenshots of bugs' clause.

3 / 3

Trigger Term Quality

Includes natural terms users would say — 'screenshot', 'UI/UX', 'visual issues', 'bugs' — giving good coverage of likely phrasings.

3 / 3

Distinctiveness Conflict Risk

The screenshot/visual-feedback niche has distinct triggers unlikely to conflict with non-visual skills.

3 / 3

Total

11

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
nyldn/claude-octopus
Reviewed

Table of Contents

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.