impeccable

Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%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 body is a dense, well-structured overview: lean directive prose, a sequenced Setup with an explicit bounded-verification checkpoint and failure fallback, and a Commands table that cleanly fans out to one-level-deep references. The only minor gap is that copy-paste executable examples are deferred to the reference files rather than shown inline.

Suggestions

Include one or two short inline command invocations with expected output in the body so the most common path (e.g. running `impeccable context` and its result) is executable without opening a reference.

Tighten the Setup step 1 sentence, which packs path resolution, Windows fallback, binary behavior, --target, loaded artifacts, and directives into a single long clause.

Dimension	Reasoning	Score
Conciseness	Terse directive prose ("The brief wins.", "Refinement preserves; redesign replaces.") that assumes Claude's competence and never explains basic design or programming concepts; every line carries an instruction or a routing rule.	5 / 5
Actionability	Concrete executable commands are given ("impeccable context", ".github/skills/impeccable/scripts/impeccable pin <pin\|unpin> <command>", "/impeccable hooks <on\|off\|status\|...>", "--target <path>"), but full worked examples and code live in the referenced per-command files, leaving minor gaps in the body itself.	4 / 5
Workflow Clarity	A numbered Setup sequence is paired with an explicit validation checkpoint ("Verify in bounded passes... inspect once with a batched round... confirm with at most one more round, and stop polishing") and a launcher-failure feedback loop with a prescribed fallback message.	5 / 5
Progressive Disclosure	The body is a clear overview with a Commands table linking to one-level-deep per-command references (e.g. [reference/shape.md](reference/shape.md)), with content appropriately split and easy to navigate; references are clearly signaled rather than buried.	5 / 5
	Total	19 / 20 Passed

Description

100%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 explicit, comprehensive, and well-bounded: it answers both what the skill does and when to use it, surfaces many natural trigger terms, and disambiguates itself with a clear negative boundary. It is dense, but the enumerations are concrete capabilities and triggers rather than fluff.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions ("design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract") plus concrete deliverable domains, giving comprehensive coverage rather than generic language.	5 / 5
Completeness	Opens with an explicit "Use when..." trigger clause, states clearly what it does (improve a frontend interface across many listed surfaces), and adds a concrete negative boundary ("Not for backend-only or non-UI tasks").	5 / 5
Trigger Term Quality	Comprehensive natural keywords and synonyms users actually say ("bolder", "quieter", "animate", "colorize", "polish", "critique", "audit", "live browser iteration"), with no common variations obviously missing.	5 / 5
Distinctiveness Conflict Risk	Scoped to frontend/UI design with explicit out-of-scope language ("Not for backend-only or non-UI tasks"), giving a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	20 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 34 missing	Warning

	Total	14 / 16 Passed

Repository: pbakaus/impeccable
Path: .github/skills/impeccable/SKILL.md
Commit: 0a4e72a

Reviewed: 3 days 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.