creative-learnings
Document learnings from creative tests including patterns of what worked and what didn't, updating the angle/hook performance database, and identifying new hypotheses to test. Use after test cycles to capture institutional knowledge and inform future creative strategy.
npx skills add majiayu000/claude-skill-registry --skill creative-learnings --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Creative Learnings Document and systematize learnings from creative tests. ## Process ### Step 1: Analyze Recent Test Results **Gather Test Data:** - All creatives tested in period - Performance metrics (CPA, CTR, CVR) - Spend and volume - Test duration **Categorize Results:** - Clear winners (scale) - Promising (iterate) - Clear losers (kill) - Inconclusive (retest) ### Step 2: Extract Patterns **What Worked - Analyze:** - Common elements in winners - Hook types performing - Body structures winning - CTA formats converting - Visual styles succeeding - Avatar responses **What Didn't Work - Analyze:** - Common failure points - Hook types failing - Angles not resonating - Visual styles flopping - Audiences not responding ### Step 3: Update Performance Database **Angle Tracker:** | Angle | Tests | Wins | Win Rate | Best CPA | Notes | |-------|-------|------|----------|----------|-------| | [Angle 1] | X | X | X% | $X | [Learning] | **Hook Type Tracker:** | Hook Type | Tests | Wins | Win Rate | Notes | |-----------|-------|------|----------|-------| | Greed | X | X | X% | [Learning] | | Emotion | X | X | X% | [Learning] | **Framework Tracker:** | Framework | Tests | Wins | Win Rate |
- Process
- Step 1: Analyze Recent Test Results
- Step 2: Extract Patterns
- Step 3: Update Performance Database
- Step 4: Identify New Hypotheses
- Step 5: Output Learnings Document
- Building Institutional Knowledge
What does the creative-learnings skill do?
Document learnings from creative tests including patterns of what worked and what didn't, updating the angle/hook performance database, and identifying new hypotheses to test. Use after test cycles to capture institutional knowledge and inform future creative strategy.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill creative-learnings --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.