CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

vercel-react-view-transitions

Guide for implementing smooth, native-feeling animations using React's View Transition API (`<ViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter/exit of components, animate list reorder, implement directional (forward/back) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.

Quality

95%

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 vercel-react-view-transitions in vercel-labs/agent-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.

A strong, expert-level body: dense decision tables, executable examples, a mandated step-by-step workflow with verification in the bundle, and clean one-level reference splitting. Weaknesses are minor — some repeated `default="none"` guidance and a missing `AGENTS.md` compiled document referenced at the end.

Suggestions

Consolidate the `default="none"` guidance (currently spread across the Props section, 'Use default="none" Deliberately', and the shared-element bullets) into one place and cross-reference it from the others.

Remove the duplicate type-keyed example (the 'enter and exit don't have to be symmetric' snippet repeats the 'nav-forward'/'nav-back' classes already shown) or replace it with a genuinely different asymmetry.

Either include the `AGENTS.md` compiled document in the bundle or delete the 'Full Compiled Document' section, since the file it points to does not exist.

DimensionReasoningScore

Conciseness

Largely efficient — tables and code carry the weight and it assumes React competence (no basic-concept explanations) — but there is some repetition: `default="none"` guidance appears in three sections (Props, 'Use default="none" Deliberately', and the shared-element bullets), and the type-keyed 'nav-forward'/'nav-back' example is shown twice in near-identical form.

4 / 5

Actionability

Code examples are concrete and executable: the works/broken placement-rule pair, the type-object mapping syntax, the complete copy-paste `DirectionalTransition` wrapper, and the two-layer list-identity/shared-element composition cover the common cases, with CSS recipes correctly delegated to a reference file.

5 / 5

Workflow Clarity

The body mandates "follow references/implementation.md step by step. Start with the audit — do not skip it", and that file (verified) contains a 7-step sequence beginning with a navigation-map audit checklist and ending in "Step 7: Verify Each Navigation Path" — explicit sequencing with a verification checkpoint and audit-driven feedback loop.

5 / 5

Progressive Disclosure

Good structure: five one-level-deep reference files, all real (anchors `#layout-displacement-morph` and `#reduced-motion` verified), each clearly signaled inline and summarized in a Reference Files section. The one flaw is the dangling pointer: the "Full Compiled Document: `AGENTS.md`" line references a file that does not exist in the bundle.

4 / 5

Total

18

/

20

Passed

Description

100%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 concrete capabilities using the exact API names, provides two explicit 'use when' trigger clauses covering both task-level and keyword-level phrasing, and carves out a distinct niche. No padding or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities: "using React's View Transition API (`<ViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements)" plus specific tasks like "create shared element animations", "animate list reorder", and "implement directional (forward/back) navigation animations" — comprehensive coverage with no vague filler.

5 / 5

Completeness

Explicitly answers both questions: 'what' via the opening capability sentence and 'when' via two explicit trigger clauses ("Use this skill whenever the user wants to..." and "Also use when the user mentions...") with concrete trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

Covers natural user phrasing comprehensively: "page transitions", "animate route changes", "animate enter/exit", "forward/back", "view transitions", "startViewTransition", "ViewTransition", "transition types", and "without third-party animation libraries" — both task-level phrases and exact API mentions users would say.

5 / 5

Distinctiveness Conflict Risk

Clear niche — React's native View Transition API — with distinct triggers; "in React without third-party animation libraries" explicitly separates it from general animation-library skills. Minimal overlap risk.

5 / 5

Total

20

/

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

boranfurkan/reproducer-hackathon

Path

skills/.agents/skills/vercel-react-view-transitions/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.