agentleFS
powerczukpowerczuk/seo-machine/skills/content-brief/SKILL.md

content-brief

Skill0 starsChanged 2 months agoMITView on GitHub

Writer-ready SEO brief: primary entity, keywords, fan-out sub-queries, tagged outline, required real material, meta drafts, links, schema, quality targets.

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

Files
SKILL.md

/content-brief — SEO content brief

Target: $ARGUMENTS

Targets and thresholds: ${CLAUDE_PLUGIN_ROOT}/skills/seo-fundamentals/references/scoring-spec.md. Ground-truth rules: ${CLAUDE_PLUGIN_ROOT}/skills/seo-fundamentals/SKILL.md.

Research

  1. Entity and keywords — primary entity (Knowledge Graph entity, not just the string), primary keyword and intent, 5–8 secondary keywords, 3–5 question keywords (PAA), 3–5 semantically related terms.
  2. Query fan-out — 8–12 sub-queries AI Mode would decompose the query into (definition, how-to, comparison, troubleshooting, best practice, alternatives, cost, when).
  3. Competitive landscape — top-10 content types, lengths (median), structures, snippet opportunities, presence of an AI Overview.
  4. Entity coverage — run /entity-coverage (or reuse its output). The brief must list the MUST-COVER entities and 5–8 information-gain points by name; each gain point becomes an outline section. If /entity-coverage cannot run, build a lighter matrix from the top 5 and say so.

Brief output

Header — target keyword, primary entity, intent, target length (SERP median +20–30%), audience, content type, difficulty.

Keywords table — primary (title, H1, first 50 words as sentence subject, 2–3 H2s, conclusion, slug), secondary (body, some H2/H3), questions (H2/H3 for snippets), related terms (naturally). No density target — the spam floor is 3%.

Outline — H1 with the primary entity; each H2/H3 tagged [MUST-COVER], [OPPORTUNITY], [INFORMATION GAIN], or [FAN-OUT TARGET: sub-query]; snippet targets marked. For each section: purpose (2–3 sentences), key points, how competitors handle it, differentiation angle, and the requirement that the first 40–60 words after the heading answer the heading's question.

Material the writer must obtain — for each information-gain point: the real data, case, quote, or screenshot needed and from whom. State explicitly that placeholders [NEEDS REAL DATA] are acceptable in drafts and fabricated material is not.

Meta draft — 3 title options (50–60 chars, entity front-loaded, click copy) and 3 descriptions (150–160 chars, value + CTA); slug (3–5 words). Final variants via /meta-tags.

Snippet strategy — target format (paragraph 40–60 words / list 5–9 items / table / definition), target question, placement right after the matching H2.

Links — 3–5 internal targets (existing pages), 2–3 external primary sources.

Schema — Article + Person (author, sameAs) + BreadcrumbList; FAQ only if the Q/A will be in the body verbatim.

Engagement requirements — hook type, where real anecdotes go (2–3), CTA placement (first within 500 words), visual notes.

Quality targets — length, Flesch ≥50 (60–70 for broad audiences), heading every 300–400 words, ≥4 citable passages per 1,000 words, ≥8 specialized entities, ≥3 information-gain points, ≥3 internal links, 2–3 external primary sources, publish threshold 70/100 with AI Overviews readiness ≥ PARTIAL.

Next: /write-seo with this brief.

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.