SEO Content Brief Skill
Generates a structured SEO content brief with search intent analysis, competitor insights, outline, and on-page SEO requirements for any target keyword.
What this file does
Generates a structured SEO content brief with search intent analysis, competitor insights, outline, and on-page SEO requirements for any target keyword.
When to use it
- Creating a content brief for a new blog post or landing page
- Planning a content strategy around specific keywords
- Briefing writers on SEO requirements for a piece of content
- Improving existing content to rank better in search results
name: seo-content-brief description: "Create a structured SEO content brief for any target keyword or topic. Use when asked to write an SEO brief, content brief, keyword brief, or content strategy document. Produces a complete brief with target keyword, search intent, outline, competitor insights, internal links, and on-page SEO guidance."
SEO Content Brief Skill
Produces a complete SEO content brief that writers can use to create content that ranks — combining search intent analysis, competitive insights, and on-page optimisation requirements into a single actionable document.
Required Inputs
Ask the user for these if not provided:
- Target keyword or topic
- Target audience (who is searching for this?)
- Website or domain (for internal linking context)
- Content goal (rank for keyword / drive leads / build authority / support existing content)
- Current ranking or page (if improving existing content — optional)
- Word count target or preference (optional — if not provided, derive from search intent)
Output Structure
SEO Content Brief: [Target Keyword]
Target keyword: [Primary keyword] Secondary keywords: [Related terms to include naturally] Search intent: [Informational / Navigational / Commercial / Transactional] Target word count: [Range — e.g. 1,200–1,800 words] Content type: [Blog post / Landing page / Guide / Comparison / Listicle] Audience: [Who will read this] CTA: [What action should this page drive?]
Search Intent Analysis
What the searcher wants: [What someone typing this keyword is actually trying to accomplish]
What "good" looks like for this query:
- Format: [How results typically appear — guide, list, comparison table, etc.]
- Depth: [Surface-level overview vs. comprehensive deep dive]
- Tone: [Expert / Conversational / Technical / Beginner-friendly]
User's next question: [What they'll search for after reading a good answer — use for internal linking]
Competitor Content Analysis
| Ranking page | Word count | Key sections covered | Gaps or weaknesses |
|---|---|---|---|
| [URL or description] | [~N words] | [Sections] | [What they're missing] |
Opportunity to differentiate: [Specific angle, data, or depth your content can add that competitors lack]
Recommended Outline
Each heading is the exact H2/H3 to use (these are what Google reads):
[H1: Title — include primary keyword, under 60 characters]
Introduction (150–200 words)
- Hook with the problem or question
- State what the reader will learn
- Include primary keyword naturally in first 100 words
[H2: First main section]
- [Key points to cover]
- [Include secondary keyword: X]
[H2: Second main section]
- [Key points]
[H2: Third main section]
- [Key points — consider a table or list here for featured snippet opportunity]
[H2: FAQ section] (recommended for informational queries)
- Q: [Question from "People Also Ask" for this keyword]
- Q: [Question 2]
Conclusion (100–150 words)
- Summarise key takeaways
- Include CTA
On-Page SEO Requirements
| Element | Requirement |
|---|---|
| Title tag | [60 chars max — primary keyword near start] |
| Meta description | [155 chars max — include keyword + benefit] |
| H1 | [Match or close to title tag] |
| Keyword density | [Use primary keyword 3–5x naturally; don't force it] |
| Image alt text | [Describe image + include keyword where natural] |
| Internal links | [3–5 internal links — see suggestions below] |
| External links | [1–2 authoritative sources to cite] |
Internal Linking Suggestions
| Anchor text | Link to | Why |
|---|---|---|
| [Relevant phrase] | [/page-path] | [Topic relevance] |
Quality Checks
- Search intent is correctly identified (informational vs commercial)
- Outline addresses the actual user question (not just the keyword)
- Competitor gaps are specific and actionable
- FAQ section addresses real "People Also Ask" questions
- Title tag is under 60 characters and includes the keyword
- Internal linking suggestions are relevant and specific
Example Trigger Phrases
- "Write an SEO brief for the keyword [keyword]"
- "Create a content brief for [topic]"
- "What should I include in a blog post about [keyword]?"
- "Build a content strategy brief for [topic]"
What's inside
10 sections: required inputs, output structure, search intent analysis, competitor analysis, outline, on-page SEO, internal links, quality checks, example triggers.
Change this for your project
- Replace
[Target Keyword]with your actual keyword - Replace
[Website or domain]with your own site for internal linking context - Replace
[URL or description]in competitor table with real competitor pages
Where it goes
Save as SKILL.md inside a skill folder. Loaded when the agent selects that skill.
Worth borrowing
- Checklist of quality checks at the end to ensure completeness
- Example trigger phrases to help users invoke the skill naturally
Related Documents
Video Script
Guides an AI to write ready-to-film two-column AV scripts with hooks, segment breakdowns, B-roll cues, text overlays, timing estimates, and shot lists.
Image Generation Skill
Provides Python functions for generating, editing, and transforming images via DALL-E 3, FLUX (Replicate/fal.ai), and local Stable Diffusion, plus utilities and prompt engineering helpers.
AI Artist — Engineering Specification
Defines a 21-section engineering specification for a prompt construction skill, covering contracts, deterministic design, error taxonomy, and production readiness.
Karis
Turns an AI agent into a marketing CMO with brand analysis, SEO audits, Reddit monitoring, and viral tweet optimization via CLI or API.