CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

choreograph

Coordinate several elements that animate together — decide what moves, in what order, how much they overlap, and what stays still — so a group reads as one intentional motion instead of a pile of separate animations. Use when building or fixing a staggered list, a hero entrance, a view swap inside a container, a multi-step flow, an element leaving while its siblings close the gap, a morph between rich states, or any interaction with several moving parts (icon + background + lines, panel + content, items flying into a target). Triggers on — stagger, staggerChildren, delayChildren, animation-delay, sequence, sequencing, orchestration, choreography, cascade, wave, timeline, "one after another", "at the same time", crossfade, popLayout, mode="wait", AnimatePresence mode, hero entrance, list entrance, multi-step, step transition, morph, useAnimate, Promise.all animations, "feels mechanical", "feels robotic", "too much going on", "feels slow to open".

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

77%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 strong, opinionated instruction set with specific timing budgets, a decision tree for pairing elements, explicit verification steps, and a required output format. Its main defect is structural: it repeatedly defers detail to a RECIPES.md that is missing from the bundle, leaving dead-end references.

Suggestions

Add the missing RECIPES.md to the bundle (containing the duplicate-view crossfade technique, duration-scaling/clamp recipes, and per-tool CSS/Motion implementation recipes), or remove the three references and inline the essential recipes.

Trim the "Initial Response" section and rhetorical asides (e.g., the wave/queue framing repeats) to tighten token efficiency.

Include one small complete, copy-paste-ready code example (e.g., a CSS --index stagger or a Motion variants snippet) so the common case is fully executable from SKILL.md alone.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious, specific guidance (timing budgets like "30–80ms between items, with the total under ~300ms", a clamp formula, interruption tests) and explains nothing Claude already knows, but the "Initial Response" script and occasional rhetorical flourishes are minor instances of content that could be trimmed, fitting the efficient-with-minor-trims anchor rather than every-token-earns-its-place.

4 / 5

Actionability

Concrete, executable inline guidance appears throughout ("--index custom property per item × a delay variable, on a keyframe with animation-fill-mode: both", "delayChildren: stagger(...)", "pass the direction through custom", "await Promise.all(...)", a useRef gating pattern), which is mostly executable with minor gaps — no complete copy-paste example, and per-tool recipes are deferred to RECIPES.md.

4 / 5

Workflow Clarity

A clear two-level sequence (Steps 1–5, then Workflow 1–6) is paired with explicit validation checkpoints: write the timeline before coding and check it against budgets, record and step through frame by frame, run the interruption checks, and "imagine the 50th use of the day", plus a 3-part required output format — matching the anchor for clear sequence with explicit validation steps and checklists.

5 / 5

Progressive Disclosure

Section structure is good and references are clearly signaled, but the body points to [RECIPES.md](RECIPES.md) three times (duplicate-view technique, duration-scaling recipes, per-tool implementation recipes) and no RECIPES.md exists in the bundle — the referenced content is simply unavailable, which is a real organization gap beyond the minor-gaps level.

3 / 5

Total

16

/

20

Passed

Description

96%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 exemplary: it states a clear purpose with concrete sub-decisions, an explicit and broad "Use when" clause, and an extensive natural-language trigger list covering APIs, synonyms, and user phrasings. Its only weakness is mild overlap risk with sibling animation skills on generic Motion terms.

DimensionReasoningScore

Specificity

The description enumerates concrete decisions ("decide what moves, in what order, how much they overlap, and what stays still") and a comprehensive list of concrete scenarios (staggered list, hero entrance, view swap, multi-step flow, siblings closing a gap, morph between rich states), matching the comprehensive-coverage anchor.

5 / 5

Completeness

It explicitly answers both what ("Coordinate several elements that animate together — decide what moves, in what order...") and when ("Use when building or fixing a staggered list, a hero entrance..." plus an explicit "Triggers on" list), matching the anchor for clear and explicit what AND when with concrete trigger phrases.

5 / 5

Trigger Term Quality

Trigger coverage spans library APIs (staggerChildren, delayChildren, popLayout, mode="wait", useAnimate), natural user phrases ("one after another", "feels mechanical", "too much going on"), and domain synonyms (cascade, wave, orchestration, choreography), which is comprehensive including synonyms.

5 / 5

Distinctiveness Conflict Risk

The multi-element choreography niche is clearly scoped with distinctive stagger/orchestration triggers, but broader terms (timeline, crossfade, morph, useAnimate, AnimatePresence) carry minor overlap risk with a closely related single-animation or Motion-library skill, so it fits "mostly distinct; minor overlap risk" rather than minimal conflict risk.

4 / 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: 2 missing

Warning

Total

15

/

16

Passed

Repository

englishstreetventures/osn

Path

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