Create an SEO writing brief or outline from a topic, audience and available search evidence. Use for content briefs before writing.
npx skills add https://github.com/AgriciDaniel/chatgpt-seo --skill seo-content-brief
A topic or query and the intended site/audience. A URL is helpful but not required for a new-site brief.
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.
Read only the resources needed for the selected part of this task:
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.
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.
Take agricidaniel/seo-content-brief from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
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.