creative-brief
Skill6 starsChanged 4 months agoMITView on GitHub
Writes the one-page creative brief a designer or editor can execute without a single follow-up question — objective, audience insight, single-minded proposition, support, mandatories, references, and format specs. Use before handing any creative work to someone else.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- willlee1995/skillstheir own version, first seen Oct 13, 2026
- tarsluna/my-custom-skillstheir own version, first seen Sep 2, 2026
- sidchaudhary/gtm-skillstheir own version, first seen Aug 21, 2026
- Infinite-Labs-AI/infinite-skillstheir own version, first seen Jul 2, 2026
- efesorjm/creative-brieftheir own version, first seen Jun 29, 2026
- Zenobia0000/dtc-copywriting-skillstheir own version, first seen Mar 20, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- Infinite-Labs-AI/infinite-skills★ 43same name
- coleschaffer/copywritingskills-rmbc★ 32same name
- tarsluna/my-custom-skills★ 9same name
- Zenobia0000/dtc-copywriting-skills★ 4same name
- efesorjm/creative-brief★ 3same name
- sidchaudhary/gtm-skills★ 1same name
- willlee1995/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository29 other files it gives its agents.
- ad-scriptsSkill
- battlecardSkill
- brand-voiceSkill
- campaign-debriefSkill
- case-study-writerSkill
- channel-pickerSkill
- cmoSkill
- competitor-teardownSkill
- content-calendarSkill
- customer-deep-diveSkill
- email-sequenceSkill
- experiment-backlogSkill
- funnel-mapSkill
- hook-factorySkill
- kpi-treeSkill
- landing-pageSkill
- launch-planSkill
- lead-magnet-builderSkill
- marketing-auditSkill
- market-research-sprintSkill
- message-mapSkill
- objection-mapSkill
- offer-builderSkill
- onboardSkill
- positioning-workshopSkill
- pricing-testSkill
- repurposeSkill
- research-to-briefSkill
- weekly-reviewSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 34
Every mandatory earns its slot.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Creative Brief — one page, zero follow-up questions
Bad creative is usually a bad brief wearing the designer's name. "Make it pop" plus a website link is not a brief; it delegates strategy to the person hired for craft. A real brief makes one decision unavoidable — the single thought the audience must be left with — and gives the maker everything needed to land it without guessing.
Inputs
- What is being made and the outcome it must cause: $ARGUMENTS
- From
marketing-brief.mdif present: positioning & message, the customer section (pains, desires, language bank — the insight comes from here, not from imagination), the offer, the voice rules, and the banned-phrases list.
Do this
- Nail the objective: the business outcome this one asset serves and the single metric that will say it worked. One asset, one objective — an asset with two objectives needs two briefs or one decision.
- Define the audience in one paragraph, ending with the insight — the true, specific thing about how they feel or behave that this creative turns. It must be evidenced from the brief's customer section; a made-up insight briefs a made-up audience.
- Write the single-minded proposition: the ONE thought the viewer leaves with, one sentence, plain language. If it contains "and", cut it in half and pick.
- Add the support: the two or three proof points that make the proposition believable, ranked, drawn from the brief's evidence only.
- List mandatories and exclusions:
- Logo, handle, and brand rules that are genuinely non-negotiable.
- Claim and legal constraints — what may not be said or shown.
- The banned-phrases list from the brief, attached in full.
- Tone shown by example — one line written in the intended register beats a paragraph describing it.
- Attach two or three references, each with one line on what to take from it (pace, framing, energy). References teach the level, never the answer.
- Close with specs and process: format, dimensions or duration, safe zones, the deliverables list, deadline, who signs off, and how many feedback rounds — one is the target.
Output
The one-page brief: objective and metric, audience and insight, single-minded proposition, support, mandatories and exclusions, references with notes, specs and sign-off. If it spills past a page, cut context — never the proposition.
Rules
- One proposition. The brief's whole job is protecting the work from the second message.
- Evidence over invention: the insight and every support point trace to the brief or the user, or they get flagged as assumptions — not passed off as fact.
- Every mandatory earns its slot. Ten mandatories is strategy abdicating to a checklist.
- Feedback rounds judge the work against the brief, not against taste. If the work meets the brief and still feels wrong, the brief was wrong — fix it and say so.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

