motion

I took a look at your motion skill and wanted to share some thoughts.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 85/100, solid B grade territory. This is based on Anthropic's skill best practices rubric. Your strongest area is Spec Compliance (14/15) — the frontmatter and structure are tight. Where you're leaving points on the table: Utility (17/20) and PDA (26/30) — mostly small efficiency wins rather than fundamental issues.

What's Working Well

• Killer metadata: 30+ trigger patterns covering framer-motion aliases, gesture terms, and hooks like useAnimate. This is exactly what makes skills discoverable.
• Clean reference architecture: SKILL.md stays lean (~218 lines) with two focused reference files for patterns and verification. The reference_index table is chef's kiss for navigation.
• Practical examples: FadeIn, Modal, gesture handling — these show real problems the skill solves, not theoretical nonsense.
• Solid 5-step workflow: Your quick_start section with success_criteria gives users a clear validation path.

The Big One: Redundancy in constraints

Your constraints and anti_patterns sections are doing the same job. Both mention AnimatePresence wrapping and avoiding width/height animation. This eats tokens without adding value.

The fix: Consolidate these into a single, tighter constraints section that clearly separates "must do" from "must not do." Something like:

constraints: |
  - Always wrap exit animations in AnimatePresence
  - Animate transform/opacity only (not width/height)
  - Use GPU-accelerated properties

This picks up +1 point and makes your PDA score tighter.

Other Things Worth Fixing

1. Second-person creep in description: "Use when asked to...