mcpbeat Sign in

SEO Content Brief Skill for Claude

Create an SEO writing brief or outline from a topic, audience and available search evidence. Use for content briefs before writing.

768 tokens
context cost
SKILL.md, read when the skill is used
2
files
plus reference files
0
copies elsewhere
how many repositories repackaged it
834
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/AgriciDaniel/chatgpt-seo --skill seo-content-brief

What comes with it

202 bytes besides the instruction
agents/openai.yaml

The instruction itself

7 sections, as written by the author

SEO content brief

Input

A topic or query and the intended site/audience. A URL is helpful but not required for a new-site brief.

Evidence and runtime

If a skill-resource reader fails to open a linked supporting file, try the

available file or execution tool using the installed plugin root returned by

the host or resolved from this skill's location. Do not hardcode a home folder,

version, or working directory. Distinguish a failed reader call from an absent

file, and files actually attempted from files not attempted. Report a resource

as unavailable only after the supported access paths have failed. If no file

or execution access is available, continue within the evidence you can read

and state that limit.

Read the operating contract when this

workflow is selected. Use runtime and data paths

when choosing a tool or handling missing data. Recheck relevant

search facts and primary sources

before date-sensitive claims. For a quantitative diagnostic, read

scoring; unavailable categories stay unknown.

Supporting resources

Read only the resources needed for the selected part of this task:

  • page-type outlines.
  • claim requirements.

Workflow

  • Define the page type and primary intent before drafting the outline. State locale assumptions and whether live search was inspected.
  • Review available search results as an intent sample. Include forums, video, reference pages or marketplaces when they reveal what searchers need; do not automatically discard them as irrelevant competitors.
  • Separate measured keyword data from brainstormed candidates. Never invent search volume, difficulty or a top-ten ranking sample.
  • Design an outline around useful questions, evidence gaps and original contributions. Map each important claim to a source or a fact the writer must obtain.
  • Specify internal link opportunities from real known URLs, suitable metadata drafts, visual ideas and any relevant schema after checking eligibility.
  • Provide acceptance criteria: reader task completed, claims supported, known facts retained, useful differentiation and a clear next action.

Deliverable

A writer-ready brief with intent, evidence scope, outline, primary/supporting topics, unique contribution, fact requirements and internal links. For outline-only requests keep it short.

Boundary

A keyword list without SERP data is a planning hypothesis. The brief does not promise rankings or require a particular word count.

Adapted from the public Claude SEO seo-content-brief workflow.

How to use it

Copy the folder

Take agricidaniel/seo-content-brief from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.