CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

find-animation-opportunities

Search a codebase or UI for places that don't animate but should, and reject everything that shouldn't. Read-only; it proposes motion with exact values, it does not implement it. Use when the user asks "what could be animated here?" or wants to "make this feel more alive". For fixing existing animations, use improve-animations or review-animations instead.

Quality

92%

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

The canonical home for this skill is find-animation-opportunities in emilkowalski/skills

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 unusually actionable skill body: exact motion values, frequency/purpose gating with explicit verdicts, a sequenced workflow with completion criteria, and a required output format that forces showing rejections. Its only weaknesses are minor editorial padding and no externalization of reference-style detail.

Suggestions

Trim meta-commentary sentences ('This section is what separates this skill from an animation wishlist', 'A search skill. It does ONE thing...') — the rules already imply them, saving tokens without losing guidance.

If the skill grows, move the duration-budget table, easing-token vocabulary, and 'Where to Hunt' catalog into a references/ file linked one level deep, keeping SKILL.md as the gate + workflow overview.

DimensionReasoningScore

Conciseness

The body is dense and operational — budget tables, exact CSS/spring values, grep sweep patterns — with only minor trimmable editorial lines such as 'This section is what separates this skill from an animation wishlist' and 'A search skill. It does ONE thing...'. Not 5: a handful of meta-commentary sentences don't earn their tokens; not 3: padding is minor and localized.

4 / 5

Actionability

Guidance is fully concrete and copy-paste ready: 'transform: scale(0.97)' with 'transition: transform 160ms ease-out', 'clip-path: inset(0 100% 0 0)' hold-to-confirm specs, spring configs '{ type: "spring", duration: 0.5, bounce: 0.2 }', velocity threshold '~0.11', named easing curves, grep patterns, and a filled-in example output table. Not 4: common cases are covered with exact values, not just templates.

5 / 5

Workflow Clarity

Recon → Sweep → Gate → Report is clearly sequenced with explicit checkpoints: 'Done when every seam class has either yielded candidates with file:line evidence or been explicitly cleared', a four-question gate that 'must survive all four questions, in order' with recorded answers, and a required rejected-candidates section. The skill is read-only, so the destructive/batch validation cap does not apply. Not 4: checkpoints (done-when, ordered gate, mandatory rejections) are explicit, not implicit.

5 / 5

Progressive Disclosure

A single well-organized file with clear section headers and easy navigation; no bundle files exist. Not 5: at ~135 lines, detail such as the duration/easing tables and the 'Where to Hunt' catalog could live in a one-level-deep reference; not 3: everything inline is genuinely used in a single pass and nothing is buried.

4 / 5

Total

18

/

20

Passed

Description

92%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: concrete third-person actions, explicit quoted trigger phrases, clearly stated scope limits (read-only, no implementation), and explicit disambiguation from sibling skills. The only gap is a few missing natural synonyms such as 'micro-interactions' or 'transitions'.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'Search a codebase or UI for places that don't animate but should, and reject everything that shouldn't', 'proposes motion with exact values', 'Read-only... it does not implement it' — with comprehensive coverage of both capabilities and explicit limits. Not 4: there are no minor gaps; finding, rejecting, proposing, and scope boundaries are all stated.

5 / 5

Completeness

It explicitly answers what ('Search... and reject everything that shouldn't', 'proposes motion with exact values', 'Read-only') and when ('Use when the user asks "what could be animated here?" or wants to "make this feel more alive"') with concrete trigger phrases. Not 4: the when-clause contains quoted trigger phrases rather than merely implied or generic guidance.

5 / 5

Trigger Term Quality

It quotes natural user phrases — 'what could be animated here?' and 'make this feel more alive' — which are exactly what a user would say when needing this skill. Not 5: common synonyms such as 'micro-interactions', 'transitions', or 'motion polish' are absent; not 3: the given triggers are natural phrases, not jargon.

4 / 5

Distinctiveness Conflict Risk

The niche is distinct (finding animation opportunities vs. implementing) and it explicitly routes overlapping intents elsewhere: 'For fixing existing animations, use improve-animations or review-animations instead.' Not 4: conflict risk is not merely reduced but actively disambiguated against sibling skills.

5 / 5

Total

19

/

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

englishstreetventures/osn

Path

.agents/skills/find-animation-opportunities/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.