Hand a writer a brief they can start from without a meeting.
Turns a keyword or topic plus an audience into a writer-ready brief that kills the back-and-forth.
Inside: Search intent, the angle, the outline, must-cover questions, internal links, and one CTA.
Install it in one line, or paste it in.
~/.claude/skills/ and runs automatically when it is relevant.Connect your context. Set it to your motion.
it sees the real questions people ask around the topic, so the must-cover list is theirs, not invented.
it sees which of your existing posts earn attention, so the internal links point to pages that convert.
it can pull your live URLs and pick real internal-link targets instead of placeholders.
This was built for a content team publishing to a defined audience. Set these to your stack:
Write one brief per intent. A "learn" piece and a "compare" piece are different articles. If the topic hides two intents, the skill splits it.
| Set this | What it is | Example |
|---|---|---|
| TOPIC | the keyword or subject | "cold email deliverability" |
| AUDIENCE | who the piece is for | foundersRevOpssupport leads |
| INTENT | what the reader wants to do | learn →comparedecidefix |
| GOAL | what the piece should drive | signupdemosubscriberead next |
| SEARCH_CONSOLE | your query-data connector | a search console |
| INTERNAL_LINKS | where real URLs live | a CMSa sitemap |
| WORD_TARGET | rough length to aim at | 1200 (match intentnot a quota) |
Everything the skill does, in full.
Takes a topic and an audience and hands your writer a brief they can start from cold: what the reader is actually trying to do, the angle that beats what already ranks, a section-by-section outline, the exact questions the piece must answer, the internal links to weave in, and the single call to action at the end. It removes the "what did you want here again" round trip.
- 1Search intent
Name what the reader is trying to do: learn, compare, decide, or fix. Everything else in the brief serves that. The skill flags a topic that mixes two intents and recommends splitting it.
- 2Angle
The one take that makes this piece worth reading over the results already ranking. Not "a guide to X," but the specific frame, contrarian, more practical, more current, that earns the click. The skill grounds the angle against the competing URLs you paste.
- 3Outline
A section-by-section skeleton with headers, in the order the reader needs them. Intro promises the payoff, body delivers it, each header is a step or a question, not a vague label.
- 4Must-cover questions
The specific questions the piece has to answer to be complete and to be quotable by an answer engine. Pulled from real related queries when a search console is connected, drawn from the topic when it is not.
- 5Internal links
Named target pages to link to, with suggested anchor text, so the piece pulls its weight in your site's structure. Real URLs when a CMS is connected, labeled placeholders when not.
- 6The CTA
One call to action, matched to the GOAL and the intent. A "learn" piece earns a subscribe, not a demo. One ask, not five.
- One primary intent per brief. Mixed intent is flagged and split.
- Every must-cover question is answerable, never filler to pad length.
- Internal links are real URLs when a source is connected, and clearly labeled placeholders when not. No invented links.
- One CTA, matched to intent. No stacking asks.
CONTENT BRIEF · topic: "cold email deliverability" · audience: founders
Intent: fix (they have a problem now)
Angle: Not "deliverability 101." The 5 settings founders miss before
they blame the copy. Practical, do-it-today.
Goal: subscribe -> newsletter
Outline:
H1 Why your cold email lands in spam (and it is not the subject line)
H2 Authenticate the domain (SPF, DKIM, DMARC) in plain English
H2 Warm the inbox before you send at volume
H2 The volume ceiling nobody tells you about
H2 A 5-minute pre-send checklist
Must-cover questions:
- What actually triggers a spam filter on cold email?
- How long does inbox warming take?
- How many sends per day is safe on a new domain?
Internal links:
-> /guide/domain-setup anchor: "authenticate your domain"
-> /guide/inbox-warming anchor: "warm the inbox" (placeholder)
CTA: "Get the pre-send checklist" -> newsletter subscribe
Next: connect a search console to replace assumed questions with real ones.
Where an operator takes this next.
The read is step one. Here's where an operator takes it once the manual version proves out.
You built the read once; now it runs itself.
Point a scheduled Claude task at your keyword list weekly and drop a ready brief into each writer's queue before the sprint starts.
Connect a search console so the must-cover questions and the angle update as real query data shifts, not a one-time guess.
Chain this into builtgtm-article-writer so the brief becomes a draft automatically, then route the draft to Slack for review.
One skill is the on-ramp.
A single skill does one job. Chained into a playbook, or run as a full build, it becomes a system. Here is where this one plugs in.