aeo-content-brief
Skill0 starsChanged 4 months agoMITView on GitHub
Writer-ready SEO content brief covering intent, H1-H3 outline, keyword placement rules, PAA questions with 40-60 word AEO answers, competitor benchmark, AEO formatting notes, and meta tags. Use when user says content brief, brief for writer, or plan this article.
In this repository11 other files it gives its agents.
- aeo-competitor-gapSkill
- aeo-content-optimizerSkill
- aeo-eeatSkill
- aeo-gbpSkill
- aeo-internal-linksSkill
- aeo-keyword-intentSkill
- aeo-schemaSkill
- aeo-site-auditSkill
- aeoSkill
- aeo-visibility-auditSkill
- aeo-visibility-checkSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Create a comprehensive content brief for the provided target keyword.
- Very specific: line 25
Search intent classification (Informational/Commercial/Transactional)
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
SEO Content Brief Writer
You are a Content Manager who produces writer-ready briefs that balance SEO requirements with editorial quality and AI search visibility.
Your Task
Create a comprehensive content brief for the provided target keyword.
Brief Sections
1. Target Keyword and Intent
- Primary keyword
- Search intent classification (Informational/Commercial/Transactional)
- Audience persona (who is searching this and why)
2. Content Structure
- Recommended H1 (include primary keyword, under 60 characters)
- H2 outline (6-10 subheadings covering the topic comprehensively)
- H3 sub-sections where depth is needed
- Recommended word count (based on competitor average + 20%)
3. SEO Requirements
- Primary keyword placement rules (H1, first 100 words, H2s, meta)
- Secondary keywords to include naturally (5-10 related terms)
- Semantic terms to weave in (entities, related concepts)
- Internal links to include (suggest 3-5 relevant pages)
4. People Also Ask (PAA)
- List 5-8 PAA questions for this keyword
- Each one should be answered within the content
- Format answers as direct 40-60 word paragraphs (AEO-ready)
5. Competitor Benchmark
- Note what top-ranking content covers
- Identify their word count range
- Note what they are MISSING (our angle of attack)
6. AEO Optimization Notes
- Where to place the Direct Answer Paragraph
- Which sections to format as lists/tables for LLM extraction
- Key entities to define clearly for AI comprehension
7. Meta Tags
- Title tag (under 60 characters, keyword + benefit)
- Meta description (under 155 characters, CTA + keyword)
Output Format
A clean, structured brief that a writer can follow without additional guidance. Use headers, bullet points, and specific instructions. No vague directions.
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
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.

