Name: guide-swiftui-animations
Rating: 61.6 (1 reviews)
Author: Prisma-Labs-Dev

guide-swiftui-animations

SwiftUI animation patterns — implicit/explicit animations, transitions, phase/keyframe animations, the Animatable protocol, and the @Animatable macro. Use when implementing animations, transitions, or motion in SwiftUI views.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./disabled-skills/guide-swiftui-animations/SKILL.md

Quality

Content

58%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 an exemplar of lean progressive disclosure — a clean, one-level-deep reference index to three verified files — but as a standalone SKILL.md body it offers no inline executable code or sequenced workflow, leaving actionability and workflow clarity to the deferred reference files.

Suggestions

Add a brief inline quick-start snippet (e.g., a minimal `withAnimation { ... }` / `.animation(...)` example) so the body provides immediately executable guidance before deferring to references.

Include a short decision workflow such as "identify the animation need → open the matching reference → apply the pattern → preview in Canvas" so Claude has a clear sequenced path, not just an index.

Add a one-line "when to use" cue per reference row (or fold it into the topic column) so navigation is driven by trigger conditions rather than topic labels alone.

Dimension	Reasoning	Score
Conciseness	The body is extremely lean — a one-line guide-skill banner plus a three-row reference table — with no padding and no explanation of concepts Claude already knows; every token largely earns its place, fitting the anchor-5 lean-and-efficient example.	5 / 5
Actionability	The body provides only an index of file pointers ("references/animation-basics.md" etc.) with topic descriptions but no executable code, commands, or concrete steps, matching anchor 2's minimal concrete guidance missing the specific steps to execute; actionable detail is deferred entirely to the reference files.	2 / 5
Workflow Clarity	There is no multi-step process or sequenced workflow with checkpoints in the body — only a topic-to-file mapping; a rough implicit "find your topic then read the file" path exists (above anchor 1) but it lacks the defined steps and structure of anchor 3 and above, and no validation is needed since animations are non-destructive.	2 / 5
Progressive Disclosure	The body is a clear overview with well-signaled, one-level-deep references (three real files verified to exist: animation-basics.md, animation-transitions.md, animation-advanced.md), each mapped to a topic with no nesting, content appropriately split, and easy navigation via the table — matching the anchor-5 example.	5 / 5
	Total	14 / 20 Passed

Description

87%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 that explicitly covers both what it does and when to use it, with concrete enumerated capabilities and natural trigger terms scoped tightly to SwiftUI animation. The only gap is framing topics as nouns rather than actions and a few missing synonyms.

Dimension	Reasoning	Score
Specificity	The description enumerates several concrete sub-capabilities ("implicit/explicit animations, transitions, phase/keyframe animations, the Animatable protocol, and the @Animatable macro"), giving broad coverage, but frames them as named patterns/topics rather than verb-actions, and omits specifics like springs or timing curves, so it sits just below the comprehensive-actions anchor 5.	4 / 5
Completeness	It clearly states what ("SwiftUI animation patterns — ...@Animatable macro") and explicitly when ("Use when implementing animations, transitions, or motion in SwiftUI views") with concrete trigger phrases, matching the anchor-5 pattern of answering both what and when explicitly.	5 / 5
Trigger Term Quality	Natural terms a user would say are present ("animations", "transitions", "motion", "SwiftUI views") in an explicit "Use when implementing..." clause, but common synonyms like "animate"/"animated" and spring/curve terms are missing, keeping it short of the comprehensive-synonym anchor 5.	4 / 5
Distinctiveness Conflict Risk	The skill occupies a clear niche (SwiftUI animation/motion specifically) with distinct triggers scoped to SwiftUI views, giving minimal conflict risk with other skills, matching the anchor-5 clear-niche example.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: Prisma-Labs-Dev/apple-skills
Path: disabled-skills/guide-swiftui-animations/SKILL.md
Commit: 4986260

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.