CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

view-transitions

Use when adding page transition animations, image expand/contract effects, shared-element transitions, or improving navigation UX in a single-page or multi-page application.

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/view-transitions/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 tight, well-structured overview body: exact API names in the Quick Reference, a clear Check/Fix/Explain/Code Review workflow with a concrete review checkpoint, and correct deferral of full code examples to a real one-level-deep reference file. The only weaknesses are a trimmable motivational intro paragraph and the absence of any inline runnable snippet or fallback-check mention in the body.

Suggestions

Trim the two-sentence motivational intro paragraph; Claude already knows why smooth transitions matter, and the body can open directly with the Quick Reference.

Inline one minimal snippet (e.g., the startViewTransition wrapper with the document.startViewTransition fallback check) so the body is self-sufficient for the most common case without opening the reference.

DimensionReasoningScore

Conciseness

The ~45-line body is lean: Quick Reference bullets name exact APIs and the Check/Fix/Explain/Code Review sections are 1-2 lines each. The two-sentence motivational intro ('Jarring instant page changes are one of the most noticeable perceived-performance problems...') is background Claude does not need — a minor trimmable instance, matching anchor 4 rather than 5.

4 / 5

Actionability

Concrete, executable API-level guidance: 'Wrap DOM mutations in document.startViewTransition() for same-page transitions', 'Add view-transition-name to elements', '@view-transition { navigation: auto }', plus exact review criteria ('missing prefers-reduced-motion guards, duplicate view-transition-name values'). Not anchor 5 because the body contains no runnable code snippet — code lives in references/rule.md.

4 / 5

Workflow Clarity

Clear sequenced workflow (Check → Fix → Explain → Code Review) with the Code Review section serving as an explicit validation checkpoint listing concrete failure modes. Minor gaps: no browser-support/fallback verification step in the body itself (feature detection is only in the reference file), so anchor 4 rather than 5.

4 / 5

Progressive Disclosure

Compact overview body with full details deferred to a single well-signaled, one-level-deep reference: 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md' — verified to exist (244 lines, own section structure, no nested references). Matches anchor 5: clear overview, appropriately split, easy navigation.

5 / 5

Total

17

/

20

Passed

Description

66%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 well-scoped, natural-sounding trigger description with specific enumerated scenarios, but it is entirely a 'when' clause: it never states what the skill does or names the View Transitions API, leaving its capability implicit. Adding an explicit capability statement (e.g., 'Implement page and shared-element transitions with the View Transitions API...') would lift completeness and specificity.

Suggestions

Add an explicit 'what' statement before the 'Use when' clause, e.g., 'Implement smooth page and shared-element transitions with the View Transitions API. Use when adding page transition animations...'.

Include 'View Transitions' / 'View Transitions API' as a trigger term, since users asking about this feature often name the API directly.

Consider trimming the broad 'improving navigation UX' phrasing or anchoring it to transitions specifically, to reduce overlap with generic navigation/routing skills.

DimensionReasoningScore

Specificity

Lists several specific concrete actions — 'adding page transition animations, image expand/contract effects, shared-element transitions' — with minor coverage gaps; the skill's own capability (implementing with the View Transitions API) is never named. Matches anchor 4 rather than 5 because implementation verbs and the API itself are absent, and not 3 since more than 1-2 concrete actions are given.

4 / 5

Completeness

The 'when' is explicit and rich ('Use when adding... in a single-page or multi-page application') but the 'what' is never explicitly stated — no capability statement such as 'Implement transitions with the View Transitions API'; the what is only implied by the enumerated triggers. Falls between anchor 2 (only 'when' present, no 'what') and anchor 3, closer to 3 because the implied what is substantive.

3 / 5

Trigger Term Quality

Good natural-term coverage: 'page transition animations', 'image expand/contract effects', 'shared-element transitions', 'navigation UX', 'single-page', 'multi-page application'. A few natural terms a user would say are missing — 'View Transitions' / the API name itself, 'smooth transitions', 'page change animation' — so anchor 4 fits better than 5 or 3.

4 / 5

Distinctiveness Conflict Risk

'shared-element transitions' and 'image expand/contract effects' are distinctive niche triggers with minimal conflict risk, but 'improving navigation UX' is broad enough to overlap with generic navigation/routing or CSS-animation skills. Mostly distinct with minor overlap risk — anchor 4.

4 / 5

Total

15

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

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