gsap
GSAP animations for JARVIS HUD transitions and effects
64
55%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/gsap/SKILL.mdQuality
Discovery
32%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 identifies a specific technology (GSAP) and context (JARVIS HUD) but lacks concrete action verbs and completely omits trigger guidance. It reads more like a category label than a functional skill description that would help Claude choose it from a large skill library.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when creating animations for JARVIS-style interfaces, implementing HUD transitions, or when the user mentions GSAP, GreenSock, or sci-fi UI effects'.
List specific concrete actions such as 'Creates entrance/exit animations, builds radar sweep effects, animates data panels, implements glowing borders and scan lines'.
Include natural keyword variations users might say: 'animate', 'motion', 'GreenSock', 'sci-fi UI', 'Iron Man interface', 'futuristic dashboard'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (GSAP animations) and context (JARVIS HUD), but lacks specific concrete actions like 'create entrance animations', 'build transition effects', or 'animate UI elements'. | 2 / 3 |
Completeness | Only addresses 'what' at a high level (GSAP animations for JARVIS HUD). Completely missing a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords 'GSAP', 'animations', 'JARVIS', 'HUD', 'transitions', 'effects', but missing common variations users might say like 'animate', 'motion', 'GreenSock', or 'UI animation'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'GSAP' and 'JARVIS HUD' provides some distinctiveness, but 'animations', 'transitions', and 'effects' are generic enough to potentially overlap with other animation or UI skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable GSAP animation skill with excellent executable code examples and clear TDD workflow. The main weaknesses are moderate verbosity with repeated patterns (cleanup, reduced motion) and a monolithic structure that could benefit from splitting detailed sections into reference files. The pre-implementation checklist and explicit validation steps are strong points.
Suggestions
Extract Performance Patterns (Section 6) and Anti-Patterns (Section 8) into separate reference files, keeping only summaries in the main skill
Consolidate repeated cleanup and reduced motion patterns into a single 'Core Patterns' section that other sections reference rather than duplicate
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy - the same cleanup patterns and reduced motion checks are repeated multiple times across sections. Some sections like the anti-patterns repeat guidance already covered in implementation patterns. | 2 / 3 |
Actionability | Excellent executable code examples throughout - complete Vue components, composables, TypeScript with proper types, and copy-paste ready patterns. Every concept is backed by concrete, runnable code. | 3 / 3 |
Workflow Clarity | Clear TDD workflow with explicit steps (write test → implement → refactor → verify). Pre-implementation checklist provides explicit validation checkpoints across three phases. The workflow includes verification commands and clear sequencing. | 3 / 3 |
Progressive Disclosure | The skill is quite long (~400 lines) with detailed inline content that could be split into reference files. Only one reference file is mentioned (advanced-patterns.md). Performance patterns, testing patterns, and anti-patterns could be separate files with summaries in the main skill. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
68%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (685 lines); consider splitting into references/ and linking | Warning |
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 11 / 16 Passed | |
- Repository
- martinholovsky/claude-skills-generator
- Commit
1086ef2
- 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.