CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ui

Inspect and verify the live PsychSift interface across routes, breakpoints, interactions, accessibility modes, reduced motion, and forced colors. Use for UI, frontend, routing, styling, responsive, browser, or accessibility work.

Quality

87%

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

86%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 efficient, well-sequenced checklist with real commands and explicit verification steps. It falls just short of top marks on actionability and workflow clarity because two steps lack concrete commands and there is no failure/retry guidance.

DimensionReasoningScore

Conciseness

Six lean numbered steps with zero padding or explanations of known concepts; phrases like 'do not assume a port' and 'when proportionate' show it assumes Claude's competence. Every token earns its place.

5 / 5

Actionability

Provides concrete executable commands ('npm run workflow:design-sweep -- --write-evidence', 'npm run ensure', 'npm run verify:ui', 'node_modules/next/dist/docs/'), but 'Verify project identity' and 'Add the smallest focused browser proof' lack a specified command or tool, leaving minor gaps.

4 / 5

Workflow Clarity

A clear 1-6 sequence with verification checkpoints present (steps 2 and 5), but no explicit error-recovery feedback loop (e.g., what to do when 'npm run ensure' fails), which keeps it below the top anchor.

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, needs no external references (no bundle files exist), and is well organized as a single numbered list, satisfying the simple-skill exception for a top score.

5 / 5

Total

18

/

20

Passed

Description

83%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 strong description that states concrete inspection scope for a named project and gives an explicit 'Use for...' trigger clause with natural keywords. The only weaknesses are limited verb variety and a few missing common synonyms in the trigger list.

DimensionReasoningScore

Specificity

Names the domain ('live PsychSift interface') and enumerates specific coverage areas ('routes, breakpoints, interactions, accessibility modes, reduced motion, and forced colors'), but relies on only two verbs (inspect/verify), leaving minor gaps in distinct concrete actions.

4 / 5

Completeness

Explicitly answers both 'what' ('Inspect and verify the live PsychSift interface across routes, breakpoints...') and 'when' with concrete trigger phrases ('Use for UI, frontend, routing, styling... work'), matching the top anchor's pattern.

5 / 5

Trigger Term Quality

'Use for UI, frontend, routing, styling, responsive, browser, or accessibility work' provides good natural keyword coverage, though common synonyms like 'CSS', 'design', 'visual', or 'a11y' are missing.

4 / 5

Distinctiveness Conflict Risk

The project-specific 'PsychSift interface' scope carves a clear niche, but broad trigger terms like 'UI, frontend, styling, browser' carry minor overlap risk with generic frontend skills.

4 / 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/ui/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.