skills/seo-content-brief/SKILL.md
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.
npx skillsauth add mohitagw15856/pm-claude-skills seo-content-briefInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
Ask the user for these if not provided:
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?]
What the searcher wants: [What someone typing this keyword is actually trying to accomplish]
What "good" looks like for this query:
User's next question: [What they'll search for after reading a good answer — use for internal linking]
| 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]
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)
[H2: First main section]
[H2: Second main section]
[H2: Third main section]
[H2: FAQ section] (recommended for informational queries)
Conclusion (100–150 words)
| 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] |
| Anchor text | Link to | Why | |---|---|---| | [Relevant phrase] | [/page-path] | [Topic relevance] |
development
Build a framework for creating shareable, high-reach social media content. Use when asked to plan viral content, develop a shareable content strategy, create a hook writing system, or build a repeatable process for content that gets shared. Produces a platform-specific viral content framework with hook formulas, content structures, shareability triggers, and a content testing system.
development
Generate article or newsletter thumbnail candidates using the Gemini API from inside Claude Code. Claude reads article copy, proposes composition concepts, writes image generation prompts incorporating brand specs, calls Gemini to generate the images, evaluates the results via computer vision, and returns ranked candidates with rationale. Use when asked to create thumbnails, generate cover images, or produce visual candidates for an article or newsletter.
testing
Flips Claude's default from "find reasons you're right" to "find reasons you're wrong." A genuine thinking partner, not a mirror with grammar. Use before high-stakes decisions, plans, assumptions, or pitches you haven't stress-tested.
development
Scrapes a Substack Notes page and exports engagement data (likes, comments, restacks) to a formatted .xlsx file with conditional formatting and summary stats.