Agent skill · marketing growth · sickn33
competitor-analysis
Research competitors with Browserbase discovery, enrichment lanes, screenshots, matrices, and HTML reports.
Why this skill is useful
Adds specific commands and structured workflows for competitor analysis using Browserbase that the AI wouldn't generate on its own.
What it needs
Requires browse installed locally. Requires browserbase account access. About 11k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Competitor Analysis When to Use Use when the user needs structured competitor research with Browserbase discovery, enrichment lanes, screenshots, comparison matrices, and a final HTML report. Source: browserbase/skills (MIT). Analyze a user's competitors. Uses Browserbase Search API for discovery and a 4-lane Plan→Research→Synthesize pattern for enrichment — outputting an HTML report with overview, per-competitor deep dives, a side-by-side feature/pricing matrix, and a chronological mentions feed. Required: BROWSERBASEAPIKEY env var and the browse CLI installed (npm install -g browse). First-run setup: On the first run you'll be prompted to approve browse cloud fetch, browse cloud search, cat, mkdir, sed, etc. Select "Yes, and don't ask again for: browse cloud fetch:\" (or equivalent) for each. To permanently approve, add these to your ~/.claude/settings.json under permissions.allow: Path rules: Always use full literal paths in Bash — NOT ~ or $HOME. Resolve the home directory once and use it everywhere. When building subagent prompts, replace {SKILLDIR} with the full literal path. Output directory: All output goes to ~/Desktop/{companyslug}competitors{YYYY-MM-DD}/. This directory contains one .md file per competitor plus the generated HTML views and CSV. CRITICAL — Tool restrictions (applies to main agent AND all subagents): All web searches: use browse cloud search. NEVER WebSearch. All page fetches: use browse cloud fetch --allow-redirects (returns markdown by default; add --format raw if you need the original HTML, then pipe through sed ... tr -s ' \n' to extract text). NEVER WebFetch. 1 MB response limit — fall back to browse get markdown (after browse open <url> --remote) for JS-heavy pages. All research output: subagents write one markdown file per competitor to {OUTPUTDIR}/{competitor-slug}.md using bash heredoc. NEVER use the Write tool or python3 -c. See references/example-research.md for the file format. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/competitor-analysis