← ClaudeAtlas

content-brief-generatorlisted

Use when planning a new article. The agent Googles the keyword, reads the top 10 results, classifies intent, maps the content gap, and produces a writer-ready brief with structure, outline, and on-page artifacts. No keyword tool required. When a SearchAtlas MCP is connected, leverages SA tools (rank tracking, brand vault, GBP, OTTO, LLM Visibility) first before falling back to generic web search.
search-atlas-group/amm-founding-circle · ★ 0 · AI & Automation · score 72
Install: claude install-skill search-atlas-group/amm-founding-circle
# Content Brief ## SearchAtlas MCP tools to use first Pulls live SERP composition from `analysis`, organic ranking context from `organic`, keyword intent from `keyword_research`, and topical map context from `topical_maps` before generating the brief. | Phase | SA MCP tool | What it gives you | |---|---|---| | Step 1 | `keyword_research` → `lookup_keyword` | Live search volume, CPC, competition, intent label, related keywords. Replaces the manual SERP-counting step. | | Step 1 | `analysis` → `get_serp_overview` | Top 10 ranking URLs, SERP features present, AI Overview detection. The canonical SERP read. | | Step 1 | `analysis` → `get_serp_features` | Featured snippets, PAA, video, image, local pack. Each maps to a content format decision. | | Step 2 | `organic` → `get_organic_keywords(project_identifier=<domain>, limit=20)` | How the brand currently ranks for this keyword's cluster. Identifies cannibalization risks. | | Step 3 | `content_retrieval` → `get_project_articles` | Existing articles on related topics. Avoid duplicate-content briefs. | | Step 3 | `topical_maps` → `list_topical_maps` | Is this keyword already in a topical map? If yes, brief reinforces the cluster; if no, suggest the topical map first. | | Output | `content_retrieval` → `cg_create_article_brief` | Optionally push the finished brief into Atlas Content Genius so the writer can pick it up there. | **Routing rule:** Always call the SearchAtlas MCP tools listed above before resorting to `web_search` or