agentsclimarketplace

Content brief

Skill SkillMedev/skills/skills/content-brief

The open Skill Me catalog — every hosted skill as a portable, MIT-licensed SKILL.md

Install
npx -y skills add SkillMedev/skills --skill content-brief

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Builds an SEO content brief a writer can execute without guesswork - primary and semantic keywords, search intent, recommended format matched to the SERP, title, H1, meta description, a full H2/H3 outline, word-count guidance derived from ranking pages, internal links with anchors, featured-snippet opportunities, CTA, and the content gap competitors miss. Use when someone says "create a brief for this keyword", "what should this article cover to rank", "outline a page targeting X", or is handing work to a content writer. Do NOT use for grouping keywords into a site-wide topic plan - use keyword-cluster-builder instead - or for optimizing an already-written page - use seo-optimizer instead.

SKILL.md

3.5 KB, 631 tokens by cl100k_base, as published. Nobody here has run it

Content Brief

You create the brief a writer follows to produce a page that ranks in search and serves the reader. The brief removes guesswork.

Process

  1. Gather: target keyword, the business goal of the page, the audience, and any competing URLs ranking now.
  2. Determine search intent (below) - everything flows from it.
  3. Build the brief.

Brief components

  1. Primary keyword - the exact phrase to target.
  2. Secondary / semantic keywords - 5-15 related terms and entities to cover (the topic's vocabulary). These help relevance, not just repetition.
  3. Search intent - informational, commercial, transactional, or navigational. This dictates format and depth.
  4. Target audience and their knowledge level - beginner vs. expert changes everything.
  5. Recommended format - listicle, how-to guide, comparison, definition + deep dive. Match what already ranks unless you can do better.
  6. Title and H1 - compelling, includes the keyword naturally.
  7. Meta description - under 155 chars, includes keyword, written to earn the click.
  8. Outline - full H2/H3 structure. This is the core of the brief.
  9. Target word count - based on what ranking pages do, not an arbitrary number.
  10. Internal links - specific existing pages to link to, with anchor suggestions.
  11. External / authority references - types of sources to cite.
  12. Featured-snippet opportunity - if a definition, list, or table could win position zero, specify it.
  13. Call to action - what the reader should do next.

Determining intent

Look at what currently ranks for the keyword:

  • Mostly guides? Informational - write to teach.
  • Product/category pages? Commercial/transactional - write to convert.
  • Match the dominant format. Fighting intent rarely ranks.

Outline quality

  • Headers should answer the questions a searcher actually has (mine "People Also Ask" and related searches).
  • Logical progression: what → why → how → what next.
  • Each H2 is a sub-topic a reader (and Google) expects. Cover the topic comprehensively without padding.
  • Note where to place the primary keyword (title, H1, first 100 words, one H2, naturally throughout).

Word count guidance

  • Derive from the SERP: roughly match or modestly exceed the top results' depth. Don't write 3,000 words because a tool said so if the intent is a quick answer.
  • More words only help if they add value; thin padding hurts.

Anti-patterns

  • Keyword stuffing instructions - write for humans, optimize lightly.
  • Ignoring intent and forcing a format.
  • Outlines that just restate competitors instead of filling gaps they miss.

Output

Deliver the complete brief. Highlight the content gap - what the top-ranking pages fail to cover that this piece should - because that's the page's best shot at outranking them.

Gives 0 of the 12 instructions most plan spec skills give in 631 tokens

Counted across 1,100 of the 1,860 authors here whose files we hold, read 2026-08-06

  • ask one question at a timein 46 of 1100, across 38 files
  • Break plans into vertical slicesin 28 of 1100, across 10 files
  • Publish issues in dependency orderin 27 of 1100, across 9 files
  • Iterate until user approves the breakdownin 24 of 1100, across 6 files
  • Explore the repository to understand the codebase statein 24 of 1100, across 7 files
  • Use domain glossary vocabularyin 23 of 1100, across 5 files
  • Apply correct triage labels to published issuesin 23 of 1100, across 5 files
  • Write failing tests before implementation codein 23 of 1100, across 18 files
  • Prefer AFK slices over HITLin 22 of 1100, across 7 files
  • ask clarifying questions until requirements are concretein 21 of 1100, across 13 files
  • Respect existing architecture decision recordsin 20 of 1100, across 5 files
  • write a specification before writing any codein 20 of 1100, across 12 files

Said here and by no other author read

  • Gather the target keyword, goal, audience, and competitors.
  • Determine search intent before building the brief.
  • Match the recommended format to ranking pages.
  • Specify internal links and authority references.
  • Highlight the content gap competitors miss.

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.