company-research
Skill1 starsChanged 3 months agoMITView on GitHub
Research a company before applying or interviewing — from a quick pre-application summary to a full interview-prep dossier (4-track web sweep). On demand, and MANDATORY at deep level once an interview process starts.
33 other projects use a version of this.
Adopted by
Most recently taken up by
- carriegale2710/resume-tailortheir own version, first seen Nov 16, 2026
- chezou/skillstheir own version, first seen Nov 15, 2026
- thesun4sky/jobstacktheir own version, first seen Nov 10, 2026
- AgnesAI-Labs/agnet-skills-cntheir own version, first seen Nov 1, 2026
- MoizIbnYousaf/marketing-clitheir own version, first seen Nov 1, 2026
- pueo-labs/primrtheir own version, first seen Nov 1, 2026
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.
nandanosqlSkillbusiness-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-StudioSkillderisk-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-StudioSkillorganic-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
nandanosqlSkillprioritization-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
Other versions33 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 33
- deanpeters/Product-Manager-Skills★ 8ksame name
- browserbase/agent-browse★ 3.7ksame name
- simonlin1212/Vibe-Research★ 3.7ksame name
- simonlin1212/vibe-astock★ 1ksame name
- stophobia/deerflow2.0-enhanced★ 821same name
- claude-office-skills/skills★ 433same name
- thesun4sky/jobstack★ 216same name
- liangdabiao/exa-research-mcp-skill★ 104same name
- exa-labs/agent-skills★ 67same name
- MoizIbnYousaf/marketing-cli★ 33same name
23 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- cover-letterSkill
- cv-tailorSkill
- interview-coachSkill
- job-scoutSkill
- learnSkill
- negotiatorSkill
- network-mapperSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-exploreSkill
- openspec-proposeSkill
- openspec-sync-specsSkill
- openspec-update-changeSkill
- outreach-drafterSkill
- setupSkill
- submitSkill
- trackerSkill
- upskillSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 25 edited versions we read keep these.
1
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
- Distinctive: line 56
Public-cover discipline: only publicly sourced facts enter the dossier → everything in it is safe to say aloud.
“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.
Files
company-research
Two levels. Pick by stage:
- Level 1 — quick scan (pre-application, feeds
cover-letterand thejob-scoutfit-check): the lightweight summary below. - Level 2 — deep dossier (an interview process exists): the 4-track sweep below.
Gate rule: a process folder is not prep-ready until its dossier exists. If the
private repo is synced (
private/), the canonical protocol lives atprivate/processes/_company-research-protocol.md— follow that version if present; this file is the public, generic mirror.
Inputs
Company name / URL, the JD, web search — in English AND the company's home-market language. Optionally Harmonic MCP (enrich_company) if connected.
Level 1 output — quick scan
- What they do and how they make money (plain language)
- Recent news / trajectory / funding or earnings signal
- Culture signals (from JD language, reviews, public posts)
- JD decoding (hiring-side inversion): read
writing-job-descriptionslogic to tell what a requirement really signals vs. boilerplate — what they're actually anxious about. - 3-5 things to reference in a cover letter or interview
Level 2 — deep dossier (4-track parallel web sweep)
Fan out four research tracks (parallel agents if available), each returning dated facts with source URLs:
- Business trajectory — history, funding, ownership, growth datapoints over time (AUM/revenue/users), headcount, layoffs/expansions, awards, leadership changes, strategy statements, negative coverage.
- Products & releases — product ladder evolution, launch dates and volumes, partnerships, pricing, app-store presence + review themes (PM-interview gold), tech stack from job ads, category/market context.
- Communications — the company's own channels (podcast/blog/webinars), every findable exec interview 2–3 years back with each person's RECURRING MESSAGES synthesized, PR coverage arc by year, last-6-months news (freshest = best in the room).
- Retrospective counterpart — the candidate's current/former employer's PUBLIC trajectory, so any contrast narrative rests entirely on citable sources.
Dossier structure (one file per process, beside the role-prep notes; in the synced
private repo: private/processes/<company>/company-research.md):
corrections-vs-prior-beliefs → timeline → business performance table → products &
releases → competitive context → communications layer → people (public layer) →
employer retrospective → interview ammo (talking points, smart questions, a speakable
60-second company story) → morning-of verification list.
Rules:
- Public-cover discipline: only publicly sourced facts enter the dossier → everything in it is safe to say aloud. Mark facts that independently confirm something known from confidential sources as [PUBLIC COVER]; confidential material never migrates in.
- Namesake check first — verify the name isn't shared with an unrelated firm before trusting aggregators.
- Single-source numbers are flagged "don't assert," never averaged. Registry > press > review portals > data vendors.
- Refresh before every human round; keep a short list of volatile facts to re-verify the morning of.
Feeds cover-letter, interview-coach, and the fit-check in job-scout.
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
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.

