Generate editor-ready SEO content briefs with competitive SERP analysis, outlines, and E-E-A-T requirements.
Works with
Analyzes top-ranking results to identify search intent, content format gaps, and competitive angles before writing begins
Provides structured templates for titles, meta descriptions, and heading hierarchies optimized for CTR and keyword targeting
Includes E-E-A-T assessment framework with YMYL detection, author qualification requirements, and evidence standards tailored to con
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionbriefExecute the skills CLI command in your project's root directory to begin installation:
Fetches brief from calm-north/seojuice-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate brief. Access via /brief in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
5
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
5
stars
Produce a complete, editor-ready content brief covering intent analysis, competitive SERP review, content outline, E-E-A-T requirements, and SEO targets.
Gather this context (ask if not provided):
Analyze what currently ranks for the target keyword:
Record:
| Rank | Title | URL | Format | Approx. Length | Unique Angle |
|---|---|---|---|---|---|
| 1 | ... | ... | guide / listicle / tutorial | ... | ... |
Determine the exact user intent and map it to content structure:
The content structure must match what the searcher expects to find.
Build a detailed outline with:
Select the formula that matches the content type:
| Content Type | Formula | Example |
|---|---|---|
| How-to / Tutorial | "How to [Goal] in [Timeframe]" | "How to Fix Crawl Errors in 30 Minutes" |
| How-to (objection) | "How to [Goal] Without [Objection]" | "How to Build Links Without Cold Outreach" |
| Listicle | "[N] [Adjective] [Topic] [Qualifier]" | "9 Proven Link Building Strategies for SaaS" |
| Comparison | "[A] vs [B]: Which Is Better for [Goal]?" | "Ahrefs vs SEMrush: Which Is Better for Keyword Research?" |
| Definition | "What Is [Topic]? [Short Clarifier]" | "What Is Topical Authority? How It Affects Rankings" |
| Ultimate guide | "The [Complete/Definitive] Guide to [Topic]" | "The Complete Guide to Technical SEO" |
| Mistakes | "[N] [Topic] Mistakes [Consequence]" | "7 Internal Linking Mistakes That Kill Rankings" |
CTR boosters — test adding these elements:
| Element | Expected CTR Impact |
|---|---|
| Add a number | +15-25% |
| Add current year | +10-15% |
| Add brackets or parentheses | +10-38% |
| Add a power word (Proven, Essential, Ultimate) | +5-12% |
Rules:
Select a template and adapt:
| Content Type | Template |
|---|---|
| Blog / Guide | "Learn [topic] with our [qualifier] guide. Covers [point 1], [point 2], and [point 3]. [CTA]." |
| Question-answer | "[Question]? This [year] guide explains [what], [why], and [how]. Get actionable tips now." |
| Listicle | "Discover [N] [adjective] [topic] strategies that [result]. Backed by [proof element]. Read the guide." |
| Comparison | "[A] vs [B]: which is better for [use case]? We compared [criteria]. See the winner + detailed breakdown." |
| Product/Service | "[Product] helps you [benefit]. [Feature 1], [Feature 2], [Feature 3]. [Price/offer]. [CTA]." |
Rules:
Map out every H2 and H3 with brief guidance for each section:
H1: [Title]
H2: [Section 1] — what to cover, target length
H3: [Subsection] — specific points
H2: [Section 2] — what to cover
...
H2: FAQ — 3-5 questions from People Also Ask
For each H2 section, specify:
First, determine if the keyword falls into "Your Money or Your Life" territory (health, finance, legal, safety). YMYL topics trigger elevated E-E-A-T requirements from Google:
Specify what credentials the author needs for this topic:
| Topic Type | Author Requirement |
|---|---|
| YMYL (health, finance, legal) | Licensed professional or verifiable expert with public credentials |
| Technical (code, engineering) | Demonstrated practitioner experience (portfolio, GitHub, publications) |
| Business/marketing | Industry experience or named case studies |
| General informational | Byline with bio is sufficient |
Set the minimum evidence bar for this piece:
| Content Type | Minimum Sources | Source Tier Requirement |
|---|---|---|
| Research/data-driven | 5+ citations | At least 2 primary sources (official docs, studies, .gov/.edu) |
| How-to / tutorial | 2-3 citations | Official documentation for tools/methods referenced |
| Opinion / thought leadership | 3+ citations | Data to support each major claim |
| Comparison / "best X" | 1 per item reviewed | First-hand testing evidence for each |
Specify what the content needs:
Different content types weight E-E-A-T signals differently. Focus effort where it matters most:
| Content Type | Experience | Expertise | Authority | Trust | Top Priority |
|---|---|---|---|---|---|
| Product review | Critical | High | Medium | High | Experience — hands-on testing evidence |
| How-to guide | High | Critical | Medium | High | Expertise — demonstrate deep knowledge |
| Research/data | Medium | Critical | Critical | Critical | Authority + Trust — sourced data, methodology |
| Opinion piece | Critical | High | High | Medium | Experience — personal credentials and POV |
| Comparison | High | High | Medium | Critical | Trust — unbiased criteria, transparent methodology |
| News/reporting | Medium | Medium | Critical | Critical | Authority — recognized source, editorial standards |
For every piece, verify at minimum:
| Element | Target |
|---|---|
| Primary keyword | [keyword] |
| Secondary keywords | [2-3 related terms] |
| Word count range | [min-max based on SERP analysis] |
| Internal links to include | [list specific pages to link to] |
| External links to include | [types of sources to cite] |
| Images/media | [count and types: screenshots, diagrams, tables] |
| Featured snippet target | [yes/no — if yes, which format: paragraph, list, table] |
The brief must specify what makes this piece better than what already ranks:
Pick 1-2 angles. Trying to win on all dimensions produces generic content.
Overview
SERP Competitive Landscape [Table from Step 1]
Title Options
Meta Description [150-160 char description]
Content Outline [Full heading structure with guidance per section]
SEO Targets [Table from Step 5]
E-E-A-T Checklist
Differentiation [What makes this piece better than current top results]
Pro Tip: Use the free Keyword Density Analyzer and TF-IDF Tool to benchmark competitor content depth for your target keyword. SEOJuice MCP users can run
/seojuice:keyword-analysisfor search volume and difficulty, and/seojuice:content-strategyto check if the topic fits an existing cluster or fills a content gap.
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
brief reduced setup friction for our internal harness; good balance of opinion and flexibility.
brief fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
brief is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: brief is the kind of skill you can hand to a new teammate without a long onboarding doc.
brief fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
brief is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Registry listing for brief matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in brief — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: brief is focused, and the summary matches what you get after install.
I recommend brief for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 73