company research

Other Community

Skill notes

Pipeline Overview

Follow these 5 steps in order. Do not skip steps or reorder. Company Research — Deeply understand the user's company, product, and who they sell to Depth Mode Selection — Choose research depth based on how many targets they want Discovery — Find target companies using diverse search queries Deep Research & Scoring — Research each company, score ICP fit

Step 0: Setup Output Directory

Before starting, create the output directory on the user's Desktop: Replace {company_slug} with the user's company name (lowercase, hyphenated) and {YYYY-MM-DD} with today's date. Pass {OUTPUT_DIR} (as a full literal path, not with ~) to all subagent prompts so they write research files there. Also clean up discovery batch files from prior runs:

Step 1: Deep Company Research

This is the most important step. The quality of everything downstream depends on deeply understanding the user's company. Ask the user for their company name or URL Check for an existing profile: List files in {SKILL_DIR}/profiles/ (ignore example.json) If a matching profile exists → load it, present to user: "I have your profile from {researched_at}. Still accurate?" If yes → skip to Step 2.

Step 2: Depth Mode Selection

Mode · Research per company · Best for quick · Homepage + 1-2 searches · ~100 companies, broad scan deep · 2-3 sub-questions, 5-8 tool calls · ~50 companies, solid research deeper · 4-5 sub-questions, 10-15 tool calls · ~25 companies, full intelligence

Step 3: Discovery

Formula: ceil(requested_companies / 35) search queries needed. Over-discover by ~2-3x because filtering typically drops 50-70%. Generate search queries with these patterns: Industry + company stage + geography ("fintech startups series A Bay Area") Technology stack + use case ("companies using Selenium for web scraping") Competitor adjacency ("alternatives to {known company in ICP}")

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@browserbase · no license declared
Token usage
Heavy
Setup complexity
Manual integration
External API key
Required · Vendor-specific
Operating systems
macOS · Linux · Windows
Runtime requirements
Node.js · Bun
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
  • Env read
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview company-research.preview
# Step 0: Setup Output Directory

OUTPUT_DIR=~/Desktop/{company_slug}_research_{YYYY-MM-DD}
mkdir -p "$OUTPUT_DIR"

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.