creative-brief-framework

I checked out your creative-brief-framework skill and was curious about the scoring—a 63/100 lands it as a solid D, which usually signals either some structural gaps or a mismatch between ambition and execution. What's the core use case you're targeting here, and are there specific areas where you felt the rubric didn't capture what you were going for?

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

TL;DR

You're at 63/100, which puts you in D territory. This is based on Anthropic's skill best practices. Your strongest area is Spec Compliance (11/15)—the frontmatter and naming are solid. The real drag is Utility (10/20)—the framework exists as an outline, but it lacks concrete examples, templates, and validation patterns that would actually make it useful for someone running it.

What's Working Well

• Clean spec structure – Your YAML frontmatter is valid and properly formatted; name follows conventions perfectly.
• Clear 5-step framework – The progression from Objective through Messaging to Stakeholders/Timeline makes intuitive sense.
• Concise writing – You're not over-explaining; the language is direct and scannable.

The Big One: No Templates or Examples (High Priority)

This is killing your utility score. You mention "One-page creative brief document" and "Stakeholder Q&A worksheet" in the Templates section, but they don't actually exist. Someone reading this skill has the structure of a brief but no idea what a completed one looks like.

The fix: Create two reference files:

• references/example-brief.md – A filled-in brief showing real values: Goal="Increase trial signups 20%", KPIs="CPA <$50, CVR >3%", Audience insights with actual data sources
• references/template-brief.md – A blank template users can copy and fill in

This alone could bump you +7 points and actually make the skill runnable. Right now it's architecture without blueprints.

Other Things Worth Fixing

1. Add trigger phrases to the description – Currently it's vague ("Use to structure concise creative briefs"). Change it to include explicit triggers: "Use when asked to 'create brief', 'campaign kickoff', 'brief template'". This helps discoverability and hits spec compliance. +2 points

2. Define jargon inline – You use "RTBs" in step 3 without explaining it's "reasons to believe". Small thing, but it creates friction for anyone not in marketing. +1 point

3. Add a Validation Checklist – No feedback loops exist. Give users a way to know if their brief is complete: □ All 5 sections filled □ KPIs are measurable □ Audience has data sources □ Stakeholders approved. This adds practical utility. +3 points

Quick Wins

• Create the two reference files (biggest impact)
• Rewrite description with trigger phrases
• Inline-define "RTBs" and other acronyms
• Add a validation checklist before the Tips section

These changes get you closer to 80+ pretty quickly.

Checkout your skill here: SkillzWave.ai | SpillWave We have an agentic skill installer that install skills in 14+ coding agent platforms. Check out this guide on how to improve your agentic skills.