agentleFS
Sign inStart free
spiralcrew-ouspiralcrew-ou/profilespider-agent-skills/company-research/SKILL.md

company-research

Skill9 starsChanged 5 months agoMITView on GitHub

Turns company records into structured company research summaries. Use when the user provides company names or records and wants a consistent overview, market position, and relevance assessment.

31 other projects use a version of this.

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

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

  • 0

    Common

    Most of the 23 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use only supplied information and clearly marked context.

    line 46
  2. Distinctive:

    Do not invent financials, headcounts, or customers.

    line 47
  3. Distinctive:

    Keep the structure identical across companies.

    line 50

“Common” is measured: kept by at least 6 in 10 of the 23 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

Purpose

Turn company records into a structured research summary: overview, market position, and relevance.

When to use this skill

  • Building account research before outreach
  • Producing comparable company profiles at scale
  • Summarizing a target account list
  • Flagging what still needs manual research

When not to use this skill

  • The records contain no usable company signal
  • You need real-time financials or news the data lacks
  • You want verified contact details rather than a profile

Required inputs

  • Company names or records

Optional inputs

  • Your offering or angle for relevance scoring
  • Industries of interest
  • Fields you want prioritized

Rules

  1. Use only supplied information and clearly marked context.
  2. Do not invent financials, headcounts, or customers.
  3. Separate facts from inferences.
  4. List research gaps rather than filling them.
  5. Keep the structure identical across companies.

Process

  1. Parse each company record.
  2. Summarize overview, industry, offering, and customers.
  3. Assess market position from available signal.
  4. List research gaps.
  5. Assess relevance to the stated goal.

Output format

Return one profile per company with the following fields:

  • company_overview
  • industry
  • products_or_services
  • target_customers
  • market_position
  • research_gaps
  • relevance_assessment

Validation

  • Confirm each field is supported or marked as a gap.
  • Confirm no invented figures appear.
  • Confirm relevance ties to the stated goal.

Limitations

  • Profiles are only as current as the input data.
  • Market position is an interpretation, not a ranking.

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.

Check your setup, free