Claude Skill

content-brief

SERP-driven content brief for a target keyword — what ranks, what to cover, headings, questions, internal links from your own data. Use when asked for a "content brief", "outline to rank for X", "what should this article cover", or before writing any SEO page.

LLM Mart · 0 points · 8 views 0 listing impressions 0 install-command copies
Virus-scanned Reviewed automatically before listing.

Full trust report

Download Ryze-AI-Adgent-open-seo-mcp-skills-skills_content-brief-e33761c.zip · 1 KB
Part of ryze-ai-adgent/open-seo-mcp-skills — 8 skills

Install

skills CLI npx skills add https://github.com/Ryze-AI-Adgent/open-seo-mcp-skills/tree/main/skills/content-brief
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install ryze-ai-adgent-open-seo-mcp-skills@llmmart
Git git clone https://github.com/Ryze-AI-Adgent/open-seo-mcp-skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole ryze-ai-adgent/open-seo-mcp-skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Content Brief

Requires

The free Ryze MCP connector (https://connector.get-ryze.ai/mcp). Claude Code: claude mcp add ryze --transport http https://connector.get-ryze.ai/mcp. claude.ai / Desktop / Cursor: add it as a custom connector with the same URL. Setup: https://www.get-ryze.ai/how-to-connect-claude-to-google-meta-ads-mcp

A brief grounded in the live SERP plus the site's own data — not a generic outline.

Workflow

  1. The SERP. If the workspace exposes DataForSEO SERP tools, pull the live Google top 10 for the target keyword (native__get_provider_docs, provider dataforseo, for the request shape) — titles, URLs, SERP features (featured snippet, PAA, video). If unavailable, fetch the top results via web search instead; the brief must be built from a real SERP either way.
  2. Read the top 3. Fetch and skim the top-ranking pages: their structure, depth, angle, what they all cover (table stakes) and what none cover (the opening).
  3. Keyword set. google_ads__generateKeywordIdeas seeded with the target — secondary keywords and question variants worth folding in, with volumes via google_ads__generateKeywordHistoricalMetrics.
  4. Your existing foothold. google_search_console__runRawSearchAnalytics filtered to the topic — queries the site already gets impressions for (work them into headings), and existing pages on adjacent topics (internal-link sources; also flag if one already half-covers this and should be expanded instead of a new page).
  5. Assemble the brief:
    • Target keyword + secondaries with volumes
    • Search intent and required format (guide/listicle/comparison/tool page), inferred from what actually ranks
    • Proposed title + meta (write for the CTR, under 60/155 chars)
    • H2/H3 outline with a one-line note per section on what it must say
    • Questions to answer (PAA + question keywords)
    • Table stakes vs the differentiating angle
    • Internal links: 3–5 existing pages to link from, with anchors
    • Target length: match the ranking median, don't pad

Output

The brief, ready to hand to a writer (or to write from directly). No preamble.

Files (open-seo-mcp-skills)
  • SKILL.md 2.4 KB
    ---
    name: content-brief
    description: SERP-driven content brief for a target keyword — what ranks, what to cover, headings, questions, internal links from your own data. Use when asked for a "content brief", "outline to rank for X", "what should this article cover", or before writing any SEO page.
    ---
    
    # Content Brief
    
    ## Requires
    
    The free Ryze MCP connector (`https://connector.get-ryze.ai/mcp`). Claude Code: `claude mcp add ryze --transport http https://connector.get-ryze.ai/mcp`. claude.ai / Desktop / Cursor: add it as a custom connector with the same URL. Setup: https://www.get-ryze.ai/how-to-connect-claude-to-google-meta-ads-mcp
    
    A brief grounded in the live SERP plus the site's own data — not a generic outline.
    
    ## Workflow
    
    1. **The SERP.** If the workspace exposes DataForSEO SERP tools, pull the live Google top 10 for the target keyword (`native__get_provider_docs`, provider `dataforseo`, for the request shape) — titles, URLs, SERP features (featured snippet, PAA, video). If unavailable, fetch the top results via web search instead; the brief must be built from a real SERP either way.
    2. **Read the top 3.** Fetch and skim the top-ranking pages: their structure, depth, angle, what they all cover (table stakes) and what none cover (the opening).
    3. **Keyword set.** `google_ads__generateKeywordIdeas` seeded with the target — secondary keywords and question variants worth folding in, with volumes via `google_ads__generateKeywordHistoricalMetrics`.
    4. **Your existing foothold.** `google_search_console__runRawSearchAnalytics` filtered to the topic — queries the site already gets impressions for (work them into headings), and existing pages on adjacent topics (internal-link sources; also flag if one already half-covers this and should be expanded instead of a new page).
    5. **Assemble the brief:**
       - Target keyword + secondaries with volumes
       - Search intent and required format (guide/listicle/comparison/tool page), inferred from what actually ranks
       - Proposed title + meta (write for the CTR, under 60/155 chars)
       - H2/H3 outline with a one-line note per section on what it must say
       - Questions to answer (PAA + question keywords)
       - Table stakes vs the differentiating angle
       - Internal links: 3–5 existing pages to link from, with anchors
       - Target length: match the ranking median, don't pad
    
    ## Output
    
    The brief, ready to hand to a writer (or to write from directly). No preamble.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related