agentleFS
Sach1ngSach1ng/PM-operating-OS/.agents/skills/company-researcher/SKILL.md

company-researcher

Skill3 starsChanged 23 days agoMITView on GitHub

Research a company using public sources and summarize strategy plus product signals. Use when the user says "research company X", "company research", "LinkedIn and strategy for X", or when onboarding needs company context.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    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 the latest 10-K or annual report, earnings materials, investor relations pages, LinkedIn company overview, and recent press.

    line 18
  2. Distinctive:

    Look at job postings, LinkedIn Jobs, Reddit, and app-store signals when relevant.

    line 21
  3. Distinctive:

    Keep the summary factual and neutral.

    line 27
  4. Distinctive:

    Prefer primary or near-primary sources.

    line 38
  5. Distinctive:

    Treat job-posting inference as signal, not ground truth.

    line 39
  6. Distinctive:

    If the company name is missing, ask for it before researching.

    line 40

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “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 Researcher

Research a company end-to-end and return a merged summary that combines strategy with product signals.

Inputs

  • Company name, exactly as given by the user
  • Optional role or product focus to emphasize

Workflow

  1. Research company strategy:
    • Use the latest 10-K or annual report, earnings materials, investor relations pages, LinkedIn company overview, and recent press.
    • Focus on company overview, strategy, priorities, and named products or tiers.
  2. Research product signals:
    • Look at job postings, LinkedIn Jobs, Reddit, and app-store signals when relevant.
    • Infer product areas and goals from job descriptions, and label those as inferred from job postings.
  3. Merge the result:
    • Overview and strategy first.
    • Product features and goals second.
    • Source hints last.
  4. Keep the summary factual and neutral.

Output format

  • 1-2 sentences on what the company does and where it sits in the market.
  • 1-2 short paragraphs on strategy, current initiatives, and priorities.
  • Product features and goals: bullet list.
  • Source hints: short list of the sources used, including the fiscal year for any 10-K.

Rules

  • Prefer primary or near-primary sources.
  • Treat job-posting inference as signal, not ground truth.
  • If the company name is missing, ask for it before researching.

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.