CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

live-design-sweep

Compatibility alias for the ui skill. Use only when the user explicitly invokes the older live-design-sweep name; otherwise use ui for live route and accessibility verification.

Quality

93%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%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.

An exemplary minimal alias body: three unambiguous instructions, an exact reference path to the canonical skill, and explicit anti-duplication guidance with zero padding. Nothing is missing for its stated purpose, and it correctly resists inlining content that belongs elsewhere.

DimensionReasoningScore

Conciseness

The body is three lean numbered instructions with zero padding, no over-explanation, and full trust in Claude's competence ('Read and follow `.agents/skills/ui/SKILL.md`'). Every token earns its place, matching the top anchor.

5 / 5

Actionability

The single required action is fully executable: it gives the exact path to read and follow (`.agents/skills/ui/SKILL.md`) plus unambiguous rules for naming and documentation. As an instruction-only skill with concrete, complete guidance, there are no gaps; not a 4 because nothing is missing or high-level.

5 / 5

Workflow Clarity

This is a single-purpose skill whose single action (delegate to the ui skill) is unambiguous, and the three-step list is clearly sequenced. No destructive or batch operations exist, so no validation checkpoints are needed — the simple-skill exception applies cleanly.

5 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external bundle references, and is well-organized with a heading and numbered list. It deliberately defers all detail one level deep to the ui skill's SKILL.md rather than duplicating it, which is exactly the right structure.

5 / 5

Total

20

/

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.

A precise, well-scoped alias description that explicitly states both what it is and exactly when to use it, with clean disambiguation from the ui skill. Its weaknesses are thin capability coverage (only 'live route and accessibility verification' are named) and sparse natural-term synonyms for the underlying capability.

Suggestions

Enumerate the ui skill's core verification actions (e.g., 'verifies live routes render correctly and checks pages for accessibility issues') to raise specificity beyond two named capabilities.

Add common synonyms users might say for the underlying capability (e.g., 'design sweep', 'a11y check', 'visual verification') so those terms route to the correct skill.

DimensionReasoningScore

Specificity

The description names its domain and routing purpose explicitly ('Compatibility alias for the ui skill', 'live route and accessibility verification') but only lists two underlying capabilities with no detail on what verification entails, matching 'names domain and 1-2 concrete actions, but not comprehensive'. It is not a 4 because it does not enumerate several specific concrete actions of the underlying skill.

3 / 5

Completeness

It clearly answers both what ('Compatibility alias for the ui skill... for live route and accessibility verification') and when ('Use only when the user explicitly invokes the older live-design-sweep name; otherwise use ui') with a concrete trigger phrase. This matches the top anchor exactly.

5 / 5

Trigger Term Quality

It includes the exact natural trigger users would say ('live-design-sweep'), plus 'ui', 'live route', and 'accessibility verification' — good coverage with a few natural terms missing. Not a 5 because synonyms like 'a11y', 'design sweep', or 'visual verification' are absent.

4 / 5

Distinctiveness Conflict Risk

It carves out a clear niche (legacy-name invocation only) and explicitly disambiguates against the overlapping ui skill ('otherwise use ui'), yielding minimal conflict risk. It is well above the 'minor overlap risk' anchor at 4.

5 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

BigSimmo/PsychSift

Path

.agents/skills/live-design-sweep/SKILL.md

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.