skills/general/analyze-competitors/SKILL.md
Conduct competitor analysis for product design. Load when user says 'analyze competitors', 'competitor research', 'competitive analysis', 'check how [competitor] does this'. Guides exploration of Zapier, n8n, Lindy, Relevance.ai and other automation platforms.
npx skillsauth add beam-ai-team/beam-next-skills analyze-competitorsInstall 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.
Systematically research competitor products to identify feature implementations, UX patterns, gaps, and opportunities.
Before saving competitor analysis, show the feature or market scope, competitors, research sources, destination path, and any assumptions that rely on non-public access. Require explicit user approval in the current turn before writing files or sharing the analysis. Do not scrape behind logins, bypass access controls, or publish competitive findings externally from this skill.
This skill is the second step in the design cycle. It:
- [ ] Load requirements from previous step
- [ ] Identify relevant competitors for this feature
- [ ] Research each competitor (hands-on exploration)
- [ ] Document findings per competitor
- [ ] Identify patterns, gaps, opportunities
- [ ] Create analysis summary
Load the requirements synthesis from Step 1:
02-resources/requirements-synthesis.md
Identify the core feature/functionality to research.
Mark this todo complete before proceeding.
Present the known competitor list from references/competitor-list.md:
Which competitors should we analyze for this feature?
Automation Platforms:
1. Zapier
2. n8n
3. Make (Integromat)
AI Agent Platforms:
4. Lindy
5. Relevance.ai
6. Crew.ai
Other:
7. Custom competitor (specify)
Select by number (e.g., "1, 2, 4") or "all"
Mark this todo complete before proceeding.
For each selected competitor, guide the user through exploration:
Let's analyze {COMPETITOR}.
Please navigate to {competitor URL} and explore how they implement {feature}.
When ready, describe what you see or share a screenshot. I'll help document:
- How they approach this feature
- Key UI elements and patterns
- User flow steps
- What works well / what doesn't
Documentation template per competitor:
## {Competitor Name}
### Feature Implementation
- How it works: {description}
- Entry point: {where users access it}
- Key steps: {1, 2, 3...}
### UI Patterns
- Layout: {sidebar, modal, wizard, etc.}
- Components used: {buttons, cards, inputs}
- Visual style: {minimal, feature-rich, etc.}
### Strengths
- {what they do well}
### Weaknesses
- {pain points or gaps}
### Screenshots/Notes
- {user observations}
Repeat for each competitor.
Mark this todo complete after ALL competitors are researched.
Analyze findings across all competitors:
Common Patterns (most competitors do this):
Differentiators (unique approaches):
Gaps (nobody does this well):
Opportunities (how we can be better):
Mark this todo complete before proceeding.
Generate the final analysis document:
# Competitor Analysis: {Feature Name}
## Executive Summary
{2-3 sentence overview of findings}
## Competitors Analyzed
| Competitor | Focus Area | Account Type |
|------------|------------|--------------|
| Zapier | {area} | Free/Premium |
| ... | ... | ... |
## Feature Comparison Matrix
| Capability | Zapier | n8n | Lindy | Ours |
|------------|--------|-----|-------|------|
| {cap 1} | Yes | Yes | No | TBD |
| ... | ... | ... | ... | ... |
## Key Findings
### What Works Well (Industry Standard)
{patterns to adopt}
### Gaps & Opportunities
{where we can differentiate}
### Recommended Approach
{synthesis for wireframing}
## Detailed Analysis
{per-competitor sections}
## References
- Screenshots: {location}
- Research date: {date}
Save to: 02-resources/competitor-analysis.md
Mark this todo complete before proceeding.
Competitor analysis complete!
Key insights:
- {insight 1}
- {insight 2}
- {insight 3}
Ready to create wireframes?
Say 'create wireframe' or 'continue design cycle'
competitor-list.md - Known competitors with URLs and account statusanalysis-framework.md - What to look for when analyzingdocumentation-template.md - Standard format for capturing findingscompetitor-analysis-template.md - Full template for analysis outputAbout Account Access:
About Screenshots:
tools
Build a Palantir-shape, PDF-native use-case proposal document for a sophisticated enterprise account: research-grounded use cases (each with description, challenge, impact, value), an operating-graph ontology page, a recommended PoC with a week-by-week plan, and a closing page that asks for one decision. Load when a client asks us to 'propose high-impact use cases', requests a use-case presentation/catalog for a function (finance, HR, ops), or when a technical evaluation team will review candidates to pick a PoC. NOT for single-account cold outreach (use prospect-brief), full process diagnostics (use operating-diagnostic), or priced proposals (use proposal-creation).
development
Convert Beam Figma slide designs into high-fidelity, editable HTML presentation decks. Use when Codex is asked to audit Figma slides, extract slide templates, rebuild Beam slides as HTML decks, decide whether Figma imagery should be exported or rebuilt in HTML/CSS, create Beam/Prism-compatible deck templates, or improve fidelity of existing Beam HTML slide rebuilds.
development
Use the Beam AI reusable slide library: individual HTML slide templates extracted from Beam Figma rebuilds, kept separate from deck themes and full deck templates. Load when the user asks for a slide library, specific Beam slide patterns, reusable Figma-inspired slides, Prism slide-library items, or slide-level HTML templates.
development
Use Beam AI deck and report design packs, HTML templates, and curated examples to create sales decks, customer intro decks, RPO decks, and DIN A4 use-case proposal reports. Load when the user asks for Beam-branded presentation templates, Prism-compatible deck templates, Beam report templates, customer intro decks, commercial proposals, or reusable HTML deck/report examples.