agentleFS
palashjain95palashjain95/jobhunter/.claude/skills/company-research/SKILL.md

company-research

Skill2 starsChanged 8 months agoMITView on GitHub

This skill should be used when the user asks to "research [company]", "tell me about [company]", "company research", or "what should I know about [company]". Produces a deep company intel brief: business model, recent news, culture signals, competitive landscape, and smart questions to ask.

33 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

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

  • 0

    Common

    Most of the 25 edited versions we read keep these.

  • 2

    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:

    If URL provided, fetch the company website and careers page.

    line 31
  2. Distinctive:

    Use web search for current info — never rely on stale data

    line 110

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

Usage

/company-research <company name>
/company-research <company name> <role title>

Inputs

  • Company name and role title (from user)
  • Optional: interview type (recruiter-screen / technical / HM / final)
  • knowledge/profile.md — to map company priorities to candidate
  • knowledge/stories/ — to identify relevant stories

If URL provided, fetch the company website and careers page.

Produce

1. Company Snapshot

What they do (one sentence), business model, stage (headcount, revenue, funding), key customers, founding team.

2. Recent News + Signals (last 90 days)

Product launches, funding, leadership changes, press, controversies. What is the company focused on RIGHT NOW?

3. The Role in Context

Why is this role open? What problem does this hire solve? What does year 1 success look like?

4. Candidate's Angle

Which stories from knowledge/stories/ map to their priorities? What unique insight can the candidate bring?

5. Competitive Landscape

Main competitors, differentiation, biggest threat, industry tailwinds vs headwinds.

6. Culture + Values Intel

Public messaging, Glassdoor/Blind/LinkedIn signals, what the interview process signals about values.

7. Smart Questions to Ask (8-10)

Grounded in actual research:

Q: [question] Why ask it: [what it signals about you] Best moment: [which interview stage / interviewer]

8. "What Do You Know About Us?" Answer

One paragraph. Grounded in research. Ends with why the candidate is excited about THIS moment in the company's journey.

Output Format

## [Company Name] — Intel Brief

### Snapshot
[One paragraph: what they do, business model, stage]

### Recent News (last 90 days)
- [news item — date]
- [news item — date]
**Right now they're focused on:** [key theme]

### This Role
**Why it's open:** [growth/replacement/new initiative]
**Year 1 success:** [what great looks like]

### Your Angle
- Story: "[story name]" maps to their priority of [X]
- Unique insight: [observation about their space]

### Competitive Landscape
| Competitor | Differentiation | Threat Level |
|------------|----------------|--------------|
| [name] | [how they differ] | High/Med/Low |

### Culture Intel
**Green flags:** [positive signals]
**Watch for:** [concerns or unknowns]

### Questions to Ask
1. [question] — *signals [what]*

### "What Do You Know About Us?"
> [One paragraph answer — ready to use]

If Something Goes Wrong

  • Company is too small/new for public info: Note what's missing. Suggest: "Can you share anything they sent you? Internal docs help fill gaps."
  • News is stale (nothing in 90 days): Widen to 6 months but flag: "Limited recent activity — could signal stability or stagnation."
  • Can't determine why role is open: Say so. Suggest asking in the interview.

After Output

  • "Ready to prep for the interview? /interview-prep"
  • "Want to practice? /mock-interview for a simulated interview"

Rules

  • Use web search for current info — never rely on stale data
  • Flag anything that changed recently
  • Be specific: "they launched X in February" beats "they're growing"
  • Connect every insight to interview strategy

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.