company-research
Deep research and ICP fit scoring for target companies.
Developer Setup
Setup & Installation
npx skills add https://github.com/browserbase/skills --skill company-researchnpx skills add https://github.com/browserbase/skills --skill company-researchOverview
What This Skill Does
Automates target company discovery, details extraction, fit assessment, and generates structured PDF and CSV reports.
Application
When to use this Skill
- When you need to discover new lead companies matching a specific Ideal Customer Profile (ICP).
- When performing deep, multi-source research on target company products, pricing, and messaging.
- When you want to automate prospect qualification and ICP fit scoring.
- When compiling comprehensive prospect research reports with structured data (CSVs, tables).
- When you need to scale up outbound lead research without manual Google searching.
Documentation
Show Skills.md file
Company Research
Discover and deeply research companies to sell to. Uses Browserbase Search API for discovery and a Plan→Research→Synthesize pattern for deep enrichment — outputting a scored research report and CSV.
Required: BROWSERBASE_API_KEY env var and browse CLI installed.
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 auto-approve for the session. To permanently approve, add these to your ~/.claude/settings.json under permissions.allow:
"Bash(browse:*)", "Bash(bunx:*)", "Bash(bun:*)", "Bash(node:*)",
"Bash(cat:*)", "Bash(mkdir:*)", "Bash(sed:*)", "Bash(head:*)", "Bash(tr:*)", "Bash(rm:*)"
Path rules: Always use the full literal path in all Bash commands — NOT ~ or $HOME (both trigger "shell expansion syntax" approval prompts). Resolve the home directory once and use it everywhere. When constructing subagent prompts, replace {SKILL_DIR} with the full literal path.
Output directory: All research output goes to ~/Desktop/{company_slug}_research_{YYYY-MM-DD}/. This directory contains one .md file per researched company plus a final .csv. The user gets both the scored spreadsheet and the full research files on their Desktop.
CRITICAL — Tool restrictions (applies to main agent AND all subagents):
- All web searches: use
browse cloud search. NEVER use WebSearch. - All page content extraction: use
node {SKILL_DIR}/scripts/extract_page.mjs "<url>". This script fetches viabrowse cloud fetch --output, parses title + meta tags + visible body text, and automatically falls back tobrowse get markdownwhen fetch fails or returns thin JS-rendered content. NEVER hand-roll abrowse cloud fetch | sedpipeline — it strips meta tags and doesn't parse the stdout JSON envelope. NEVER use WebFetch. - All research output: subagents write one markdown file per company to
{OUTPUT_DIR}/{company-slug}.mdusing bash heredoc. NEVER use the Write tool orpython3 -c. Seereferences/example-research.mdfor the file format. - Report + CSV compilation: use
node {SKILL_DIR}/scripts/compile_report.mjs {OUTPUT_DIR} --open— generates HTML report and CSV in one step, opens overview in browser. - URL deduplication: use
node {SKILL_DIR}/scripts/list_urls.mjs /tmpafter discovery. - Subagents must use ONLY the Bash tool. No other tools allowed.
- Main agent NEVER reads raw discovery JSON batch files. Use
list_urls.mjsfor dedup.
Recommendations