plugins/pm-gtm/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
Analyse competitor moves and translate them into strategic implications for your product roadmap. Use when a competitor announces a new feature, pricing change, partnership, or strategic shift, or when producing a periodic competitive intelligence report. Produces a categorised signal analysis with reactive-vs-proactive assessment, threat ratings, specific roadmap implications, and recommended responses with owners.
development
Build a community management playbook for a brand's social media channels. Use when asked to create guidelines for managing comments, DMs, and community interactions, define a moderation policy, or build response frameworks for social media community managers. Produces a complete playbook with response templates, escalation paths, moderation rules, and tone guidelines.
development
Activate a 4-stage coding discipline framework that forces Claude to plan before coding, isolate changes on a branch, write tests first, and self-review output twice before presenting it. Use when starting a complex coding task, when past Claude sessions produced broken first drafts, or when you want to prevent rework cycles. Produces a confirmed written plan, isolated feature branch, test-first implementation, and a double-reviewed output with a correctness and code-quality checklist.
development
Optimize an article for Answer Engine Optimization (AEO) — restructuring content so AI engines like ChatGPT, Perplexity, and Claude can extract, quote, and cite it. Rewrites headings as questions, drops 50-80 word answer capsules, audits paragraph length, and flags trust signals. Use when asked to AEO-optimize, make content AI-readable, improve AI citation chances, or adapt an article for answer engines.