agentleFS
Sign inStart free
designhousemedesignhouseme/AdvancedSkills/skills/company-research/SKILL.md

company-research

Skill1 starsChanged 34 days agoCC-BY-4.0View on GitHub

Produces verifiable research on a specific company. Confirms its identity, scope of services, customer voice and trust signals, and records every fact with a source and date. Use when someone asks to research a company, vet a client or contractor, find out "what we know about company X", or prepare for a meeting or proposal. If someone wants a whole website for the company, use business-website, which runs this research. Not for market or competitor analysis, and not for a single fact such as a tax ID alone.

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

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

  • 0

    Common

    Most of the 23 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“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.

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