agentleFS
Sign inStart free
prosyo-aiprosyo-ai/gtm-skill/skills/seo-content-brief/SKILL.md

seo-content-brief

Skill13 starsChanged 23 days agoMITView on GitHub

Use this skill when you need a B2B SEO content brief that a writer can turn into a page that ranks and converts: \"write an SEO brief\", \"content brief for this keyword\", \"plan a blog post that ranks\", \"outline for a landing page\". Analyses search intent, what currently ranks and what it misses, picks the angle and format, builds the outline with headings, questions to answer, entities, internal links, schema and the conversion path, and sets the success metrics.

32 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use seo-sxo, seo-google and 10 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.
  • timruebenachSkill

    seo-sxo

    Search Experience Optimization: reads Google SERPs backwards to detect page-type mismatches, derives user stories from search intent signals, and scores pages from multiple persona perspectives. Identifies why well-optimized pages fail to rank by analyzing what Google rewards for each keyword. Use when user says "SXO", "search experience", "page type mismatch", "SERP analysis", "user story", "persona scoring", "why isn't my page ranking", "intent mismatch", or "wireframe".

    Also in 12 projects that use this

  • timruebenachSkill

    seo-google

    Google SEO APIs: Search Console (Search Analytics, URL Inspection, Sitemaps), PageSpeed Insights v5, CrUX field data with 25-week history, Indexing API v3, and GA4 organic traffic. Provides real Google field data for Core Web Vitals, indexation status, search performance, and organic traffic trends. Use when user says "search console", "GSC", "PageSpeed", "CrUX", "field data", "indexing API", "GA4 organic", "URL inspection", "google api setup", "real CWV data", "impressions", "clicks", "CTR", "position data", "LCP", "INP", "CLS", "FCP", "TTFB", or "Lighthouse scores".

    Also in 11 projects that use this

  • indranilbanerjeeSkill

    seo-drift

    Compare two SEO exports (Search Console, two dates): gainers, losers, drift classes. \"what moved after the core update\"

    Also in 11 projects that use this

  • amirjahfar1Skill

    seo-firecrawl

    Ad-hoc web scraping, site mapping, and full-site crawling via Firecrawl MCP. Returns raw HTML, parsed metadata (og:*, twitter:*, JSON-LD, canonical, robots), JS-rendered DOM, and screenshots that WebFetch cannot. Distinct from the DataForSEO skills (which give keyword/traffic/SERP data) and from WebFetch (which gives markdown prose only). Use when the user says "scrape this page", "crawl this site", "map this site", "find all pages on", "get the OG tags", "get the JSON-LD", "render this JS-heavy page", or any task where raw `<head>` metadata, structured-data scripts, or post-JS DOM are the actual deliverable. Also invoked as a sub-step from other skills that need raw HTML.

    Also in 3 projects that use this

  • Teapot-AgencySkill

    seo-internal-linking

    AI-powered internal linking recommendations z brief + site map. Reads brief.json (z $seo-content-brief) + site_map.json (z $seo-site-crawler), AI-skóruje candidate URLs by semantic relevance to brief topic + secondary KWs, outputs ranked top 5-10 s anchor suggestions a reasoning. Auto-fired počas $seo-content-brief Section 7. Triggers - "navrhni internal linky pre brief XYZ", "internal linking pre <slug>", "linking suggestions pre brief". Pre site URL discovery (zdroj data) use $seo-site-crawler. Pre brief generation use $seo-content-brief.

    Also in 3 projects that use this

  • AgriciDanielSkill

    seo-agentic

    Audit and fix agent readiness: the Lighthouse Agentic Browsing fraction, accessibility tree for agents, robots.txt and Content-Signal for AI agents, WAF treatment of agent traffic, llms.txt, Markdown delivery, ai-catalog.json, /.well-known discovery files, and WebMCP tools. Use when the user asks whether AI agents can use or browse the site, or about llms.txt or WebMCP. Exclude AI citability and brand signals (seo-geo) and commerce protocol depth (seo-ecommerce).

    Also in 3 projects that use this

  • +6 more from timruebenach

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 31 edited versions we read keep these.

  • 8

    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:

    Use this before any page is written for search.

    line 16
  2. Distinctive:

    Look at what ranks today and classify the intent: informational (how to, what is), commercial (best, vs, alternatives, tools), …

    line 27
  3. Distinctive:

    Read references/brief-template.md for the full template.

    line 36
  4. Distinctive:

    Every heading has a job; no "Introduction" or "Conclusion" sections.

    line 51
  5. Distinctive:

    MUST base the outline on actual intent and the current results.

    line 58
  6. Distinctive:

    MUST include something original (data, template, expert view, example).

    line 59
  7. Distinctive:

    NEVER target a keyword an existing page already covers without a consolidation plan.

    line 60
  8. Distinctive:

    NEVER recommend keyword stuffing, doorway pages or fake reviews.

    line 61

“Common” is measured: kept by at least 6 in 10 of the 31 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

Use this before any page is written for search. A good brief makes the writer's job specific: who it is for, what it must answer better than what ranks today, and what the reader should do next.

Inputs

  • The target keyword or topic.
  • Product, audience and the problem it connects to.
  • Existing pages on the site (to link and avoid cannibalising).

The play

1. Read the intent

Look at what ranks today and classify the intent: informational (how to, what is), commercial (best, vs, alternatives, tools), transactional (pricing, template, free tool) or navigational. The format of the top results is the format searchers expect; fight it only with a reason.

2. Find the gap

For the top results, note what they cover, how deep they go, what they miss, and how fresh they are. Your page wins on one of: depth, original data, a better tool or template, expert experience, or clearer structure.

3. Choose angle and format

One sentence: "The <format> that <does what the others don't> for <audience>."

4. Build the outline

Read references/brief-template.md for the full template. It covers:

  • Title tag (under 60 characters) and meta description (under 155).
  • H1 and H2/H3 structure, each with what it must say.
  • Questions to answer (from search suggestions and buyer calls), each answered in the first sentence of its section.
  • Entities and terms that should appear naturally.
  • Original value: data, examples, screenshots, templates.
  • Internal links to and from the page; schema (FAQ, HowTo, SoftwareApplication, Article).
  • The conversion path: a CTA that fits the intent (template download, free tool, demo for commercial intent).

5. Set success metrics

Target position and traffic, plus what matters more: sign-ups, demo requests or assisted pipeline from the page.

What good looks like

  • The brief says exactly why this page will be better than what ranks.
  • Every heading has a job; no "Introduction" or "Conclusion" sections.
  • Answers lead each section (good for featured snippets and AI answers).
  • The CTA matches the intent: nobody searching "what is an ICP" wants a demo.
  • The common mistake is a brief that is a keyword list plus "write 2,000 words", which produces the same page as everyone else.

Rules

  • MUST base the outline on actual intent and the current results.
  • MUST include something original (data, template, expert view, example).
  • NEVER target a keyword an existing page already covers without a consolidation plan.
  • NEVER recommend keyword stuffing, doorway pages or fake reviews.

Example prompts

  • "Write an SEO brief for 'cold email templates for SaaS'."
  • "Brief a comparison page for 'Acme alternatives'."
  • "Plan a cluster of 8 pages around 'sales prospecting'."

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.

Check your setup, free