agentleFS
SkillMedevSkillMedev/content-marketing-engine/skills/content-brief/SKILL.md

content-brief

Skill1 starsChanged 39 days agoMITView on GitHub

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.

19 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use competitor-gap, serp-analysis and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • DarynaRodriguezSkill

    competitor-gap

    Finds the terms rivals rank for and the site does not, confirms who the real organic competitors are, and returns a gap table split into terms to win, terms underperforming, and terms to concede.

    Also in 4 projects that use this

  • opencueSkill

    serp-analysis

    Use when the user asks to "analyze SERPs"; reviews ranking factors, features, intent, AI Overviews, and snippets. SERP分析/搜索结果

    Also in 3 projects that use this

  • indranilbanerjeeSkill

    client-proposal

    Draft a client proposal or RFP response: scope, deliverables, KPIs, pricing tiers. \"respond to this RFP\"

    Also in 3 projects that use this

  • akii-technologies-ltdSkill

    internal-linking

    Analyze and improve internal linking strategy. Use when the user asks about "internal links", "link structure", "site architecture", "link strategy", "orphan pages", "link equity", "page authority distribution", "anchor text", "topical clusters", "siloing", or wants to improve how pages connect.

    Also in 3 projects that use this

  • akii-technologies-ltdSkill

    keyword-clustering

    Cluster and organize keywords into topical groups for SEO. Use when the user asks to "cluster keywords", "group keywords", "organize keywords", "keyword mapping", "topic clusters", "keyword grouping", "build a content plan", "pillar pages", "topical authority", "semantic clustering", or pastes a list of keywords.

    Also in 3 projects that use this

  • silvainfmSkill

    schema-markup

    When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," or "breadcrumb schema." For broader SEO issues, see seo-audit.

    Also in 5 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Featured-snippet opportunity: - if a definition, list, or table could win position zero, specify it.

    line 31
  2. Distinctive:

    Look at what currently ranks for the keyword:

    line 36

“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.