Content Brief
Turn a vague content request into a brief a writer can execute without a second conversation: one question, reader, intent, angle, structure, evidence required. Use for content briefs.
Install
npx skills add eshmith7/claude-skills-library --skill content-briefgit clone --depth 1 https://github.com/eshmith7/claude-skills-library.git /tmp/claude-skills-library
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills-library/content-skills/content-brief ~/.claude/skills/content-briefPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Content Brief Builder "We need a blog post about X" is not a brief, and it is what most writers actually receive. So the writer guesses the audience, guesses the angle, guesses the length, and produces something the requester rejects for reasons that were never written down. Then it happens again next week, with a different topic and the same conversation. ## When to use this Trigger on: content brief, writer brief, blog brief, creative brief, commissioning, freelance brief, article outline, "we need a post about", "what should this piece cover", SEO brief, "brief the writer". ## Before you start Required: the request, however vague. "We need something on X" is enough to start from. Ask these, and do not proceed on a guess for the first two: 1. **Who is this for, and what do they already know?** A piece for somebody who has never heard of the category and a piece for somebody comparing two vendors share nothing except the topic. 2. **What should the reader do or think differently afterwards?** If the answer is "be aware of us", push for something a reader could act on. A piece with no intended change cannot be judged, so it gets reviewed on taste instead. 3. Where it publishes and gets read, since that governs length, form and how much context is needed. 4. What already exists on this topic internally. Most teams write a fourth piece on a subject where the answer was to update the first. 5. Who reviews and approves it, and what has been rejected before. ## Workflow
Details
- Skill name
content-brief- Repository
- eshmith7/claude-skills-library
- Path
content-skills/content-brief/SKILL.md- Repo updated
- 9 September 2026
FAQ
What does the Content Brief skill do?
Turn a vague content request into a brief a writer can execute without a second conversation: one question, reader, intent, angle, structure, evidence required. Use for content briefs.
How do I install the Content Brief skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add eshmith7/claude-skills-library --skill content-brief. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Content Brief popular?
It lives in eshmith7/claude-skills-library, which has 5 GitHub stars and 1 forks.
Related skills
Content Performance Audit
5eshmith7/claude-skills-library
Turn a performance export into one decision per asset: keep, refresh, rewrite, consolidate or delete, with cannibalisation groups found first. Use for content audits or pruning.
Content Prepublication Check
5eshmith7/claude-skills-library
Check a draft before publishing: every claim registered with its source, numbers verified, headline against body, originality and compliance flags. Use before anything goes out.
Content Repurposing
5eshmith7/claude-skills-library
Break one asset into its atomic ideas, match each to the right channel, and rewrite for that channel rather than truncating. Use for repurposing or multi-channel distribution.
Writing Skills
8Freddy-CHEN-ux/00_claude_skills
Use when creating reusable process documentation. Apply TDD: baseline without skill → document failures → write skill → test → iterate. Four types: Discipline, Technique, Pattern, Reference. Iron Law: No skill without failing test first.
Writing Plans
8Freddy-CHEN-ux/00_claude_skills
Use after brainstorming, before implementation. Breaks work into discrete, actionable tasks with clear verification points.
Value Stream Mapping
5vnovakovits/claude-skills
Map how a request flows from ask to value — Mike Rother & John Shook's "Learning to See" (1999) and Karen Martin & Mike Osterling's "Value Stream Mapping" (2013), adapted to software and knowledge work. Covers scoping one value stream, the map grammar (process boxes with lead time, process time and %C&A, queue triangles, push and pull arrows, information flow, the timeline ladder, kaizen bursts), collecting real numbers from tracker state history instead of opinions, the summary metrics (total lead time, process time, flow efficiency or activity ratio, rolled %C&A), the future-state questions,
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.