agentleFS
simonstrumsesimonstrumse/vibelabs-skills/skills/company-research/SKILL.md

company-research

Skill0 starsChanged 9 months agoMITView on GitHub

Company research using Exa search. Finds company info, competitors, news, tweets, financials, LinkedIn profiles, builds company lists.

32 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use business-health-diagnostic, derisk-measurement-advisor and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • nandanosqlSkill

    business-health-diagnostic

    Run a comprehensive business health check across revenue, unit economics, product metrics, and market position — identifying strengths, weaknesses, and the single most important metric to fix.

    Also in 4 projects that use this

  • DIAL-StudioSkill

    derisk-measurement-advisor

    Identify what to measure, test, or track to de-risk a product or AI idea. Use when stress-testing an idea across internal (DUFV) and external (PESTEL) dimensions.

    Also in 3 projects that use this

  • DIAL-StudioSkill

    organic-growth-advisor

    Identify which organic growth path to pursue — new segments, geographies, channels, or products. Use when diagnosing where a growth constraint lives and which McKinsey growth level to act\

    Also in 3 projects that use this

  • nandanosqlSkill

    prioritization-advisor

    Guide PMs in choosing the right prioritization framework — RICE, ICE, Kano, MoSCoW, Value vs Effort, Cost of Delay — by asking adaptive questions about product stage, team context, and data availability.

    Also in 4 projects that use this

  • +8 more from nandanosql

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 24 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    ONLY use web_search_advanced from Exa.

    line 13
  2. Distinctive:

    Never run Exa searches in main context.

    line 17
  3. Distinctive:

    No hardcoded numResults. Tune to user intent:

    line 26
  4. Distinctive:

    Use appropriate Exa category:

    line 43

“Common” is measured: kept by at least 6 in 10 of the 24 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Company Research

Tool Restriction (Critical)

ONLY use web_search_advanced from Exa. Do NOT use web_search_exa or any other Exa tools.

Token Isolation (Critical)

Never run Exa searches in main context. Always spawn Task agents:

  • Agent runs Exa search internally
  • Agent processes results using LLM intelligence
  • Agent returns only distilled output (compact JSON or brief markdown)
  • Main context stays clean regardless of search volume

Dynamic Tuning

No hardcoded numResults. Tune to user intent:

  • User says "a few" → 10-20
  • User says "comprehensive" → 50-100
  • User specifies number → match it
  • Ambiguous? Ask: "How many companies would you like?"

Query Variation

Exa returns different results for different phrasings. For coverage:

  • Generate 2-3 query variations
  • Run in parallel
  • Merge and deduplicate

Categories

Use appropriate Exa category:

  • company → homepages, gargantuan amount of metadata such as headcount, location, funding, revenue
  • news → press coverage
  • tweet → social presence
  • people → LinkedIn profiles (public data)

LinkedIn

Public LinkedIn via Exa: category "people", no other filters Auth-required LinkedIn → use Claude in Chrome browser fallback

Browser Fallback

Auto-fallback to Claude in Chrome when:

  • Exa returns insufficient results
  • Content is auth-gated
  • Dynamic pages need JavaScript

Models

  • haiku: fast extraction (listing, discovery)
  • opus: synthesis, analysis, browser automation

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.