competitor-analysis
Analyze competitor website structures, messaging patterns, and unique features. Use when researching competition, identifying gaps, or informing content strategy.
What this skill does
# Competitor Analysis Skill
## Purpose
Analyze top competitors page-by-page to understand their structure, messaging, and features for gap analysis.
## Analysis Framework
### Pages to Analyze
1. **Homepage** - First impression, main value prop
2. **About** - Story, team, credentials
3. **Services/Products** - Offering structure
4. **Pricing** - Pricing model and presentation
5. **Contact** - Conversion points
6. **Blog/Resources** - Content strategy
### Per-Page Breakdown
For each page, extract:
#### 1. Section Structure
Order of sections from top to bottom:
- Hero
- Problem statement
- Value propositions
- Social proof
- Process/How it works
- Pricing teaser
- FAQ
- CTA
#### 2. Headlines & Subheadlines
Capture the exact wording used:
- Main headlines
- Section headlines
- Supporting copy
#### 3. Trust Signals
What builds credibility:
- Review counts
- Star ratings
- Certifications
- Logos (clients, partners)
- Awards
- Guarantees
#### 4. CTAs
Call-to-action patterns:
- Button text
- Placement
- Urgency language
- Form fields
#### 5. Unique Features
What they have that others don't:
- Interactive tools
- Calculators
- Chat widgets
- Video content
- Custom features
## Competitor Ranking
### National Leader
- Highest authority sites
- Largest market share
- Reference for industry best practices
### Regional Top
- Strong in specific markets
- May have niche advantages
### Local Competitor
- Direct competition in service area
- Similar size and offering
### Emerging
- New entrants with interesting approaches
- Potential disruptors
## Gap Analysis Output
After analyzing competitors, identify:
1. **Missing Features** - What do they have that we don't?
2. **Missing Trust Signals** - What credibility markers are we lacking?
3. **Messaging Gaps** - What are they saying that we're not?
4. **Recommendations** - Prioritized action items
## When to Use
- Before website redesign
- When entering new market
- For quarterly competitive review
- Before pricing changes
- When creating new pages
## Integration Points
- `src/lib/agents/competitor-analyzer.ts` - Main agent
- `competitor_analysis` table - Storage
- ConversionCopywritingEngine - Consumer
## Output Format
```json
{
"competitor": "Competitor Name",
"url": "https://competitor.com",
"rank": "national_leader",
"page_structures": {
"homepage": {
"sections": [...],
"headlines": [...],
"ctas": [...]
}
},
"unique_features": [...],
"trust_signals": [...],
"messaging_patterns": {...}
}
```
## Quality Rules
1. **Analyze, don't copy** - Learn patterns, don't plagiarize
2. **Focus on structure** - Why it works, not just what it is
3. **Date your analysis** - Websites change frequently
4. **Note what's missing** - Gaps are opportunities
5. **Prioritize insights** - Not everything matters equally
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.