brief▌
calm-north/seojuice-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Generate editor-ready SEO content briefs with competitive SERP analysis, outlines, and E-E-A-T requirements.
- ›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
Content Brief
Produce a complete, editor-ready content brief covering intent analysis, competitive SERP review, content outline, E-E-A-T requirements, and SEO targets.
Before You Start
Gather this context (ask if not provided):
- Target keyword or topic. The primary keyword this content should rank for.
- Business context. What does the company do? What should readers do after reading (sign up, buy, contact)?
- Content type preference. Blog post, landing page, guide, comparison, tutorial?
- Audience. Who is reading this? Beginners, practitioners, decision-makers?
Step 1: SERP Analysis
Analyze what currently ranks for the target keyword:
- Search the keyword (use web search) and review the top 5-10 results.
- Identify the dominant intent. Are results informational guides, product pages, listicles, tools?
- Note the content format. Average word count, heading structure, use of images/tables/videos.
- Find the gaps. What do all top results cover? What do none of them cover well?
Record:
| Rank | Title | URL | Format | Approx. Length | Unique Angle |
|---|---|---|---|---|---|
| 1 | ... | ... | guide / listicle / tutorial | ... | ... |
Step 2: Intent Mapping
Determine the exact user intent and map it to content structure:
- "How to" intent → Step-by-step tutorial with numbered sections
- "What is" intent → Definition + context + examples + next steps
- "Best X" intent → Curated list with comparison criteria and recommendations
- "X vs Y" intent → Side-by-side comparison table + verdict
- "Review" intent → Hands-on evaluation with pros/cons/alternatives
The content structure must match what the searcher expects to find.
Step 3: Content Outline
Build a detailed outline with:
Title Options (2-3 variants)
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:
- Include the primary keyword
- Keep under 60 characters (55 for mobile safety)
- Use odd numbers in listicles (they outperform even)
- Rewrite if CTR is below 2% at positions 1-3 or below 5% at positions 4-10
Meta Description
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:
- 150-160 characters (aim for 140-155 for mobile safety)
- Include the primary keyword naturally
- End with a clear value proposition or call to action
- Add numbers or statistics where possible (+5-15% CTR boost)
Heading Structure
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
Key Points Per Section
For each H2 section, specify:
- The main point to make
- Data or examples to include
- How this section differs from competitor coverage
- Internal link opportunities (link to related pages on the site)
Step 4: E-E-A-T Requirements
YMYL Check
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:
- YMYL keywords require: named author with verifiable credentials, citations to official sources (.gov, .edu, professional bodies), clear disclosure of affiliations, and medical/ legal/financial review where applicable.
- Non-YMYL keywords still benefit from E-E-A-T but don't require the same rigor.
Author Qualification
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 |
Evidence Floor
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 |
E-E-A-T Signals
Specify what the content needs:
- Experience: First-hand examples, case studies, screenshots, "we tested this" statements
- Expertise: Cite specific data, reference industry standards, show depth beyond surface-level
- Authoritativeness: Link to authoritative external sources, reference recognized frameworks
- Trustworthiness: Include dates, update frequency, author bio, transparent methodology
E-E-A-T Priority by Content Type
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 |
Content Quality Checklist (Top Priorities)
For every piece, verify at minimum:
- Author identified with relevant credentials visible on page
- At least 1 first-hand experience element (case study, screenshot, "we tested")
- All statistics have named sources and dates
- At least 2 references to primary sources (not just other blog posts)
- Published date visible; content updated within 18 months
- No unsupported superlatives ("best", "fastest", "most effective") without evidence
Step 5: SEO Targets
| 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] |
Step 6: Differentiation Angle
The brief must specify what makes this piece better than what already ranks:
- More current: Updated data, recent examples
- More practical: Templates, checklists, step-by-step screenshots
- More comprehensive: Covers subtopics competitors skip
- More specific: Targets a niche the broad pieces miss
- Original data: Survey results, internal data analysis, expert quotes
Pick 1-2 angles. Trying to win on all dimensions produces generic content.
Output Format
Content Brief: [target keyword]
Overview
- Target keyword: [keyword]
- Search intent: [type]
- Content format: [blog post / guide / comparison / etc.]
- Target word count: [range]
- Target audience: [who]
- Business goal: [what readers should do after]
SERP Competitive Landscape [Table from Step 1]
Title Options
- [option 1]
- [option 2]
- [option 3]
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
- First-hand experience demonstrated
- Expert-level depth on core topic
- Authoritative sources cited
- Trust signals included (dates, author, methodology)
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.
How to use brief on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add brief
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches brief from GitHub repository calm-north/seojuice-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate brief. Access the skill through slash commands (e.g., /brief) or your agent's skill management interface.
Security & Verification Notice
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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
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
Competitive Analysis
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
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
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
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ 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.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★73 reviews- ★★★★★Chen Robinson· Dec 28, 2024
brief reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Shikha Mishra· Dec 16, 2024
brief fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Li Okafor· Dec 12, 2024
brief is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Chen Martinez· Dec 12, 2024
Keeps context tight: brief is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Olivia Abebe· Dec 8, 2024
brief fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Layla Smith· Dec 4, 2024
brief is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Diya Choi· Nov 27, 2024
Registry listing for brief matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Sakura Garcia· Nov 23, 2024
Useful defaults in brief — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Charlotte Patel· Nov 23, 2024
Solid pick for teams standardizing on skills: brief is focused, and the summary matches what you get after install.
- ★★★★★Sakura Martin· Nov 23, 2024
I recommend brief for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 73