CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

team-motion-design

Unified team skill for motion design. Animation token systems, scroll choreography, GPU-accelerated transforms, reduced-motion fallback. Uses team-worker agent architecture. Triggers on "team motion design", "animation system".

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 ./.claude/skills/team-motion-design/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.

The body is well-organized, concise, and offers genuinely executable scaffolding (spawn template, CLI tools, message bus), but it depends on role/spec reference files that are not present in the bundle, which breaks progressive disclosure and leaves the per-role execution detail non-actionable from the SKILL.md alone.

Suggestions

Include the referenced role spec files (roles/<role>/role.md) and spec files (specs/*.md) in the bundle so the signaled progressive-disclosure links resolve.

Add an explicit validation/verification feedback loop (e.g. validate motion tokens -> fix -> re-validate) inline to push workflow clarity to 5.

Inline a short summary of each role's Phase 2-4 responsibilities so the skill is actionable even before the role.md files are read.

DimensionReasoningScore

Conciseness

The body is lean and token-efficient: terse ASCII diagram, tables, and a copy-paste spawn template with no padding or explanation of concepts Claude already knows, matching the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

Provides a concrete, copy-paste-ready Agent({}) spawn template, real CLI commands ('ccw cli --mode analysis'), and message-bus invocations, but the per-role Phase 2-4 execution detail is delegated to role.md files that are absent from the bundle, leaving a gap beyond 'minor'.

4 / 5

Workflow Clarity

Clear sequenced pipeline (research -> choreography -> animation -> performance testing) with a phase diagram, role registry, session layout, GC-round limit, and an error-handling table covering failure modes; not 5 because no explicit validate->fix->retry feedback loop is inlined and the tester's verification step is externalized.

4 / 5

Progressive Disclosure

References are clearly signaled and one-level-deep in intent (roles/<role>/role.md, specs/*.md) with proper markdown links, but none of the referenced files exist in the bundle, so navigation to the detail content is broken rather than clean.

3 / 5

Total

16

/

20

Passed

Description

67%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 specific and complete with an explicit trigger clause, but its trigger phrases are thin and partly self-referential, capping trigger-term quality and distinctiveness. Strengthening natural-sounding triggers would raise the score.

Suggestions

Add natural user-facing trigger phrases beyond the skill name, e.g. 'scroll animation', 'page transitions', 'reduced-motion', 'animation performance'.

Reframe capability noun-phrases as concrete verbs (e.g. 'Build animation token systems, choreograph scroll sequences, ...') to lift specificity toward 5.

Add a 'Use when ...' clause naming concrete situations (e.g. designing a motion system, optimizing scroll/animation performance) to push completeness to 5.

DimensionReasoningScore

Specificity

Names four concrete capability domains ('Animation token systems, scroll choreography, GPU-accelerated transforms, reduced-motion fallback'), matching the 'several specific actions; minor gaps' anchor; not 5 because capabilities are noun-phrases rather than enumerated concrete verbs, and not 3 because more than 1-2 are listed.

4 / 5

Completeness

Has a clear 'what' (motion design pipeline capabilities) and an explicit 'when' clause ('Triggers on ...'), matching the 'both what and when; when could be more explicit' anchor; not 5 because the trigger set is only two coined phrases rather than rich concrete situations.

4 / 5

Trigger Term Quality

Provides two explicit trigger phrases ('team motion design', 'animation system') but one is the skill's own coined name and natural user synonyms like 'animation', 'scroll animation', or 'page transitions' are missing, matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

A fairly specific niche (GPU-accelerated transforms, scroll choreography, reduced-motion) with a distinctive team-agent architecture angle, mostly distinct with minor overlap risk against generic CSS/animation skills; not 5 because the coined trigger phrases are not naturally distinguishing.

4 / 5

Total

15

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

relative_links

Relative link issues: 9 missing, 5 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

catlog22/Claude-Code-Workflow

Path

.claude/skills/team-motion-design/SKILL.md

Revision

07491b0

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill