Install any skill in seconds. Free to start, no credit card required.
Get Started Free →rampstackco/content-brief-authoring
How to author a content brief that actually guides a writer (human or AI) to produce a piece that ranks, converts, or both. Per-piece editorial brief: target keyword and cluster, search intent, audience and JTBD, heading structure, entity coverage for AEO/GEO, internal linking strategy, success criteria. The middle path between thin briefs (a keyword and a deadline) and thick briefs (a 4-page document nobody reads).
Passed 17 of 22 test cases with the skill, and 12 of 22 without it.
and 5 more in the full report
5 fixed12 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are building our editorial strategy for Q3 and need to map out our topic pillars, keyword clusters, content calendar, and publishing cadence across the next six months. Can you structure our program-level content plan?
| Checked | Without skill | With skill |
|---|---|---|
| States that program-level editorial strategy falls outside per-piece brief authoring. | Missed | Passed |
| Declines generating a program-level content calendar. | Missed | Passed |
The instructions your model reads when the skill loads.
A senior content strategist's playbook for authoring per-piece content briefs that actually guide writers to produce content worth publishing.
Most content briefs are some flavor of broken. The thin version is a keyword, a word count, and a deadline; the writer fills in everything else from scratch and the output is generic. The thick version is a 4-page document nobody reads, that the writer skims for the headline and the outline and ignores the rest. Either way, the brief failed at its job: making the writer's work easier and the output more predictable.
This skill is the middle path. It defines the 12 fields that earn their keep in a content brief, the fields that bloat without helping, and the discipline of writing briefs that route a writer (human or AI) toward a content piece that ranks for its target keyword, gets cited by AI engines, converts the right reader, or whatever the success criteria say. It assumes you have decided what to write (see content-strategy for program-level decisions) and now you are briefing each piece. The piece itself gets written separately (see content-and-copy).
When to use this skill: briefing a writer (human or AI) on an individual content piece, auditing existing briefs that are not producing good content, building a brief template for a content program, or running a brief-generation pipeline through Frase, AirOps, or another tool.
This skill spans the per-piece editorial brief discipline. It composes with three sister skills, and the distinction between them is what keeps each one sharp.
creative-brief is a project brief. It bridges discovery to execution at the project level: a new website, app, brand, or campaign. Audience, goals, scope, success at project scope.content-strategy is a program-level editorial strategy. Pillars, calendar, topic clusters, governance. What to produce across a quarter or a year.content-and-copy is the writing itself. Voice, structure, edit pass, tone calibration. Execution scope for general editorial.content-strategy (program decided) and content-and-copy (piece gets written). It briefs a single content artifact: keyword, intent, audience, outline, entities, success criteria.The clean reading order: content-strategy decides what to produce; this skill briefs each piece; content-and-copy writes it. If the team is briefing a redesign or a new brand build, that is creative-brief, not this skill.
The audience: content strategists, SEO content marketers, editorial leads, content ops managers, agencies running content programs at scale, and any PM or marketer briefing a writer (human or AI). The voice is senior content strategist to junior content marketer. Specific, opinionated, honest about what makes a brief useful versus useless.
The keystone distinction. Three concrete shapes.
Thin brief. Keyword, word count target, deadline. Maybe a one-line summary of the angle. The writer fills in everything else from scratch. Output is generic, drifts off-topic, does not rank, and does not convert. The cost is the rewrite cycle: editor spends two hours rewriting because the writer chose the wrong intent, the wrong audience, or the wrong outline.
Thick brief. A 4-page document with executive summary, brand-guidelines refresher, comprehensive competitive analysis, voice guidelines, plus the actual brief somewhere in the middle. The writer skims for the outline, ignores the rest. Output is not materially better than from a thin brief because the writer never read most of the document. The cost is the authoring time: the strategist spends three hours producing pages of context the writer will never absorb.
Effective brief. One to two pages. Every field earns its keep. Writer reads all of it because there is no fluff. Output is predictable enough that the editor does not have to rewrite the lede. The cost is the discipline of cutting fields that do not change writer behavior.
The discipline. Every field in the brief has a job. If you can remove the field without degrading the output, remove it. The brief is the contract between editorial leader and writer; vague contracts produce vague output, overstuffed contracts produce output that reflects only the parts the writer read.
Most briefs that are not working are thin, not thick. The instinct to add more usually makes the brief worse. The instinct to be more specific in fewer fields usually makes the brief better.
test cases passed, vs 12 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.