CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

improve-animations

Survey a codebase's animation and motion code as a senior motion advisor, then produce a prioritized audit and self-contained implementation plans for other agents (or cheaper models) to execute. Read-only on source code — it plans improvements, it does not apply them. Use when the user asks to "improve the animations", "audit the motion", "make this app feel better", or wants a roadmap of animation fixes rather than a review of a single diff.

Quality

90%

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 improve-animations in emilkowalski/skills

SKILL.md
Quality
Evals
Security

Quality

Content

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

A tightly written, well-sequenced advisor workflow with concrete audit guidance, explicit vetting, and clear effort calibration. Its one significant flaw is that the two load-bearing bundle files it references (AUDIT.md, PLAN-TEMPLATE.md) are missing from the bundle, undermining both progressive disclosure and end-to-end actionability.

Suggestions

Ship AUDIT.md and PLAN-TEMPLATE.md in the skill bundle — the body defers the rule catalog ('precise values lives in AUDIT.md') and the plan format to them, so without them Phases 2 and 4 cannot be executed as specified.

Alternatively, inline the eight category headings with their key rule values (easing/duration targets) into SKILL.md so the skill is self-sufficient even if the reference files are absent.

Trim the canned 'Initial Response' greeting block ('Do not provide any other information until the user asks a question') — it delays useful output and spends tokens on ceremony rather than the audit.

DimensionReasoningScore

Conciseness

The body is dense and functional throughout: grep sweep terms, an effort-level table, severity definitions, and a variants table, with no padding or explanation of concepts Claude already knows. The brief 'Operating Posture' and 'Tone' sections set judgment criteria rather than re-teaching basics, so every token earns its place.

5 / 5

Actionability

Mostly executable guidance: exact grep terms ('transition', '@keyframes', 'prefers-reduced-motion'), the findings table schema, plan naming ('NNN-short-slug.md'), and a concrete command ('git rev-parse --short HEAD'). It falls short of fully copy-paste ready because the critical concrete values (easing rules, plan format) are delegated to AUDIT.md and PLAN-TEMPLATE.md, so the written text alone leaves minor gaps for Phases 2 and 4.

4 / 5

Workflow Clarity

Four clearly sequenced phases with explicit validation checkpoints: Phase 3 mandates re-reading every cited finding at file:line with named rejection criteria, a stop-and-wait user confirmation gate (with a non-interactive default), and plans require verification sections including feel-checks. The workflow is read-only, so the destructive-operation cap does not apply.

5 / 5

Progressive Disclosure

Structure and signaling are good — two clearly flagged, one-level-deep references ('The rule catalog with precise values lives in [AUDIT.md](AUDIT.md)') and a well-organized overview — but both referenced files are absent from the bundle (no AUDIT.md or PLAN-TEMPLATE.md exists alongside SKILL.md), so the navigation leads nowhere and the detailed content is effectively missing. This lands between 'good structure' (4) and disorganized (2); broken references are a substantive defect, not a minor gap.

3 / 5

Total

17

/

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 actions, explicit read-only scope, and quoted natural trigger phrases, with an explicit disambiguation against a sibling review skill. Only minor gap is a few missing motion-related synonyms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Survey a codebase's animation and motion code', 'produce a prioritized audit and self-contained implementation plans' — and explicitly bounds scope ('Read-only on source code — it plans improvements, it does not apply them'). Coverage of the skill's niche is comprehensive; not score 4 territory since no meaningful action is missing.

5 / 5

Completeness

Explicitly answers both: what ('Survey... then produce a prioritized audit and self-contained implementation plans') and when ('Use when the user asks to "improve the animations"...'), with concrete quoted trigger phrases matching the anchor-5 example structure.

5 / 5

Trigger Term Quality

Includes natural phrases users would actually say: 'improve the animations', 'audit the motion', 'make this app feel better', 'roadmap of animation fixes'. A few natural synonyms are absent (e.g., 'transitions', 'easing', 'micro-interactions'), so it sits between 'good coverage' (4) and 'comprehensive' (5).

4 / 5

Distinctiveness Conflict Risk

Clear niche (whole-codebase motion audit + planning) with an explicit boundary against the neighboring skill — 'It does not review a single diff (that's `review-animations`)' — and against implementing fixes, minimizing wrong-skill triggering.

5 / 5

Total

19

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 4 missing

Warning

Total

15

/

16

Passed

Repository

englishstreetventures/osn

Path

.agents/skills/improve-animations/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.