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] |
business
Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win/loss rates by segment and competitor, representative quotes, and prioritized actions for product, marketing, and sales.
development
Route a fuzzy request to the right skill in this library. Use when the user is unsure which skill fits, asks 'which skill should I use for X', describes a task without naming a skill, or when a request could plausibly match several skills. Produces a best-fit recommendation with the inputs to gather, a runner-up with the tie-breaker, and a workflow recipe when the job spans multiple skills.
testing
Triage a vulnerability or scanner finding — assess real severity, exploitability, and how urgently to fix. Use when asked to triage a CVE, prioritize scanner/pentest findings, assess a vuln's risk, or decide what to patch first. Produces a triage verdict: CVSS-informed severity adjusted for your context, exploitability, real risk, a fix/mitigation, and an SLA — so you fix what matters, not just what's red.
development
Stand up a Voice of Customer (VoC) program that turns feedback into action. Use when asked to build a VoC program, design a customer feedback loop, consolidate feedback sources, or set up a closed-loop feedback process. Produces a VoC program design — objectives, feedback sources and channels, a taxonomy, collection and analysis cadence, closed-loop routing, ownership, and success metrics.