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.
Install / Use
npx skills add rampstackco/claude-skills --skill content-brief-authoringInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Content & MediaSupported Platforms
Tags
Our assessment of content-brief-authoring
content-brief-authoring scores 86/100 on our quality scale, 738th of 1,153 Content & Media skills we index.
Its SKILL.md is 22 KB long, well organised into 16 sections and no code examples: a thorough specification that gives an agent plenty to work with.
It has 902 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so content-brief-authoring is actively maintained.
- Our last check on 2026-11-03 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
content-brief-authoring compared with similar skills
All 4 of these similar skills score higher than content-brief-authoring; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| content-brief-authoring (this skill)by rampstackco | 86 | 902 | 2mo ago | SKILL.md |
| siyuanby siyuan-note | 100 | 47.3k | today | MCP Server |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
Frequently asked questions
- How do I install content-brief-authoring?
- Run
npx skills add rampstackco/claude-skills --skill content-brief-authoring. The install tabs above show the steps for each supported agent. - Which AI agents does content-brief-authoring work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is content-brief-authoring safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is content-brief-authoring still maintained?
- The repository was last updated about 2 months ago, so content-brief-authoring is actively maintained.
Skill content
View source on GitHubname: content-brief-authoring description: "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). Triggers on content brief, brief the writer, brief the article, brief authoring, content brief template, brief audit, per-piece brief, editorial brief, target keyword brief, search intent brief. Also triggers when briefing a human writer or an AI agent on a single content piece." category: content catalog_summary: "Per-piece editorial brief: target keyword, intent, audience, outline, entity coverage, internal linking, success criteria, and the discipline that distinguishes useful briefs from bloat" display_order: 2
Content Brief Authoring
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.
What this skill is for
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-briefis 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-strategyis a program-level editorial strategy. Pillars, calendar, topic clusters, governance. What to produce across a quarter or a year.content-and-copyis the writing itself. Voice, structure, edit pass, tone calibration. Execution scope for general editorial.- This skill is the per-piece brief between
content-strategy(program decided) andcontent-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.
Thin vs thick vs effective briefs
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.
The 12 fields of an effective brief
A useful brief has 12 fields. Skip any of them and the writer fills the gap from priors; the gap is where output drifts.
- Target keyword + supporting cluster. Primary keyword plus 3 to 5 supporting keywords from the same cluster. The cluster is what tells the writer the topic has range; the primary is what the piece optimizes for.
- Search intent classification. Informational, navigational, commercial, or transactional. Plus the dominant SERP format check (article, listicle, comparison, video, tool). The intent decides what kind of piece this is; the format decides the shape.
- Target audience. Specific role and sophistication level. Not "anyone interested in X." A senior data engineer at a 500-person SaaS company is a target; "data people" is not.
- Job to be done. The problem the reader is trying to solve when they land on the piece. One sentence. Specific.
- Word count / depth target. Calibrated to the SERP, not to a content quota. If the top 10 are all 1,200 words, briefing 3,000 wastes effort; if the top 10 are all 4,000 words, briefing 1,500 produces a piece that cannot rank.
- Heading structure outline. H2s and H3s explicit, ordered logically. The outline is where the writer reads the brief most carefully; spend time here.
- Required entities, statistics, citations. For AEO and GEO, the named tools, methods, experts, and statistics the piece must cover. The entity gap is the agent's prioritization signal.
- Internal linking strategy. 3 to 5 pages this piece should link out to with anchor text; 1 to 3 existing pages that should link back to this piece after publish.
- External proof points. Required citations, sources, expert quotes. Not optional.
- Anti-patterns. What not to do. Off-topic tangents the writer might wander into, off-brand voice, AI clichés the brief explicitly forbids by listing them in a do-not-use list (the standard set of overused corporate-speak adjectives, throat-clearing openers, and verbs that signal AI generation).
- Success criteria. What good looks like. Rank for the target keyword in 90 days. Get cited by ChatGPT for the cluster within 60 days. Drive 50 trial signups in the first 30 days. Measurable, time-bound, tied to the program goal.
- Author voice and tone reference. Link to the brand-voice guide. If the piece needs a tone shift from the default voice, note it here in one sentence.
The fields that do not earn their keep, and should be omitted from briefs unless the writer is brand new to the program:
- Long executive summary (the brief itself is the executive summary)
- Brand-guidelines refresher (link to it; do not repeat)
- Comprehensive competitive landscape (link to research; do not dump)
- Brief history of the publication, company, or brand (irrelevant to this piece)
Detail and templates per content type in references/brief-templates.md.
Search intent classification
The four standard intents:
- Informational. The reader wants to learn. SERP usually shows articles, guides, explainers.
- Navigational. The reader wants a specific brand or page. SERP usually shows the brand site at #1; ranking against navigational intent is mostly impossible unless you are the brand.
- Commercial. The reader is researching a purchase. SERP usually shows comparisons, reviews, "best X" listicles.
- Transactional. The reader is ready to buy. SERP usually shows product pages, pricing pages, signup flows.
The dominant SERP format check. After classifying intent, scan the SERP top 10 and tag the dominant format: article, listicle, comparison, video, tool, hybrid. The dominant format tells you the shape of the piece, which is more decisive than the intent label.
The override pattern. When the intent feels informational but the SERP shows mostly listicles, write the listicle. When the intent feels commercial but the SERP shows mostly long-form articles, write the article. The SERP is the source of truth, not your priors. Rankings come from matching the SERP's accepted shape; deviating costs ranking.
The AEO/GEO consideration. AI engines tend to favor pieces that match SERP intent format because the intent classification was trained on the SERP corpus. Mismatched format is a citation risk in addition to a ranking risk.
Detail in references/search-intent-classification.md.
Heading structure design
Heading hierarchy patterns the brief should specify:
- H2 sections that match common follow-up questions for the keyword. The reader's mental model is a series of questions; the H2s answer them in order.
- H3s under H2s only when they add navigational value. No orphan H3s. No H2-H3-H4 cascades that nobody scrolls through.
- Featured snippet bait pattern: a 40 to 60 word answer paragraph immediately following an H2 question. Google often pulls this paragraph as the snippet; AI engines often quote it as the citation.
- H2 ordering that matches the reader's mental model, not the writer's enthusiasm. Put the obvious answer first; the writer's clever angle goes in H2 #4, not H2 #1.
Anti-patterns the brief should explicitly forbid:
- H2s that all start with "How to" or all start with "The." Repetitive structure signals AI generation to AEO/GEO crawlers and to readers.
- Buried lede: H2 #4 has the actual answer. The reader bounced at H2 #2.
- Section length wildly uneven: H2 #1 is 1,500 words, H2 #2 is 80 words. The 80-word section reads as a placeholder.
Detail in references/heading-structure-patterns.md.
Entity coverage for AEO and GEO
AI engines (ChatGPT, Perplexity, Claude, Gemini, Google AI Mode) tend to cite content that mentions the entities the SERP top-ranking pages mention, includes specific statistics with sources, contains citation-formatted proof points, and demonstrates topical depth via entity coverage.
The entity discovery pattern, run before briefing the piece:
- Pull SERP top 10 for the target keyword.
- Identify entities mentioned across multiple pages: named tools, named methods, named experts, named data sources, named statistics.
- Identify entities mentioned by 1 to 2 pages but not in your existing content. This is the entity gap.
- Add the gap entities to the brief as req
Truncated for display — read the full file on GitHub.
Related Skills
siyuan
47.3kAn open-source, privacy-first, self-hosted knowledge workspace where humans and AI agents work together 开源、隐私优先、自托管的知识工作空间,让人与智能体在此协作
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
