creative-variants

I took a look at how creative-variants approaches generating variation patterns, and I'm curious about the decision to focus on content transformation over structural variation—was that a deliberate scope choice, or something that emerged during development?

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 67/100, solidly in D territory. This is based on Anthropic's best practices for agentic skills. Your strongest area is Spec Compliance (12/15) — the frontmatter and naming conventions are clean. The weakest spot is Progressive Disclosure Architecture (18/30) — you've got everything crammed into SKILL.md when it should be spread across reference files.

What's Working Well

• Clean spec foundation — Your YAML frontmatter is valid, naming follows conventions, and the overall structure is grammatically sound
• Practical framework — The Hook Library (benefit, problem, proof, story, contrarian, curiosity) is a solid taxonomy that actually maps to how creative testing works in paid media
• Channel-aware matrix thinking — Recognizing that format varies by channel (Stories, Reels, static feed) shows you understand the domain

The Big One: Missing Reference Architecture

Your biggest blocker is the reference file gap. You list "Templates" (variant tracker, copy bank, storyboard sheet) but don't actually provide them. This violates Progressive Disclosure Architecture completely — users are left with abstract concepts instead of actionable templates they can immediately use.

Fix: Create a references/ directory with:

• references/variant-tracker.md — Actual template with columns (Hook Type, Copy, Asset, Status, CTR, Conversions)
• references/copy-bank.md — Concrete examples: "Benefit: Save 10 hours/w...