agentleFS
andrew-shwetzerandrew-shwetzer/career-ops-plugin/skills/research/SKILL.md

research

Skill501 starsChanged 7 months agoMITView on GitHub

Research a company before applying or interviewing. Get an intelligence brief with culture, financials, recent news, team structure, key contacts, and smart interview questions. Use when someone says 'research this company', 'tell me about', 'what do you know about', or 'prep me for my interview at'.

189 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use daily-arxiv, exp-eval 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.
  • LambenthanSkill

    daily-arxiv

    每日从 arXiv 拉取新论文,过滤相关性,auto-ingest 高优先级论文,检测 SOTA 更新

    Also in 5 projects that use this

  • LambenthanSkill

    exp-eval

    实验判决门:Review LLM 独立评判实验结果 → 4 种判决路径 → 自动更新 claims confidence、ideas status、graph edges

    Also in 5 projects that use this

  • truongtv22Skill

    Problem-Solving Techniques

    Apply systematic problem-solving techniques for complexity spirals (simplification cascades), innovation blocks (collision-zone thinking), recurring patterns (meta-pattern recognition), assumption constraints (inversion exercise), scale uncertainty (scale game), and dispatch when stuck. Techniques derived from Microsoft Amplifier project patterns adapted for immediate application.

    Also in 5 projects that use this

  • liufeng1976Skill

    setup-ts-deep-modules

    Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.

    Also in 43 projects that use this

  • skyllwtSkill

    exp-pilot-eval

    Pilot result evaluation — read pilot results, apply success criteria, update idea page (pilot_result, failure_reason if failed), generate PILOT_VERDICT_REPORT. Called by /ideate Phase 5 after /exp-pilot-run.

    Also in 4 projects that use this

  • skyllwtSkill

    exp-pilot-run

    Pilot experiment execution — read Pilot Spec YAML, write pilot code, run experiment(Confirm with the user before operation and require the applicant to conduct manual inspection), return results. Called by /ideate Phase 5. Does NOT modify wiki pages or judge pass/fail.

    Also in 4 projects that use this

  • +5 more from Lambenthan
  • +1 more from skyllwt

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 168 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use WebSearch to find:

    line 20
  2. Distinctive:

    If WebSearch is unavailable:

    line 32
  3. Distinctive:

    Search for likely hiring contacts:

    line 41
  4. Very specific:

    Read data/evaluations/ for any evaluation at this company.

    line 53

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

Build an intelligence brief on a target company.

Step 1: Gather Data

Use WebSearch to find:

  1. Company basics: What they do, size, founded, HQ, funding/revenue
  2. Recent news (last 6 months): Product launches, layoffs, acquisitions, leadership changes, funding rounds
  3. Culture signals: Glassdoor rating + recurring themes, any "best places to work" lists or notable controversies
  4. Team/department: Who leads the department you'd join? Likely hiring manager? Team size?
  5. Tech/tools/methodology: What does this team use? (Check job postings, tech blog, team member LinkedIn profiles via web search)

If WebSearch is unavailable:

"I can share what I know about {company}, but for the latest info (recent news, Glassdoor reviews, team changes), enable web search in your settings. Here's what I can tell you from general knowledge:"

Then provide what you know, clearly labeled as potentially outdated.

Step 2: Find Contacts

Search for likely hiring contacts:

  • Hiring manager (head of the relevant department)
  • Recruiter (search "{company} recruiter {department}")
  • Team members (potential peers for informational outreach)

For each contact found: Name, Title, and where you found them.

Note: Do NOT scrape LinkedIn profiles directly. Use web search results and public company pages only.

Step 3: Check for Existing Evaluation

Read data/evaluations/ for any evaluation at this company. If found, reference it to add context to the brief.

Step 4: Output

## Company Brief: {Company Name}

### Overview
| Field | Detail |
|---|---|
| **Industry** | {industry} |
| **Size** | {employee count range} |
| **Founded** | {year} |
| **HQ** | {location} |
| **Revenue/Funding** | {if available} |
| **Website** | {URL} |

### Recent News (Last 6 Months)
- {headline} ({source}, {date})
- ...
(If no news found: "No major recent news found.")

### Culture Snapshot
**Glassdoor:** {rating}/5 ({review count} reviews)
**Positive themes:** {what employees like}
**Negative themes:** {common complaints}
**Work style:** {remote/hybrid/in-office, hours culture}

### Key Contacts
| Name | Title | Source |
|---|---|---|
| {name} | {title} | {where found} |

### Interview Intelligence
- **Company values/mission:** {what they emphasize}
- **Current priorities:** {what they're working on now}
- **Smart questions to ask:**
  1. {question based on recent news or strategy}
  2. {question about team/culture}
  3. {question about role's impact}
- **Topics to handle carefully:** {any sensitive items}

Step 5: Save

Write to data/research/{company-slug}.md.

"Research saved. You can reference it anytime.

Want me to:

  • Draft outreach to one of these contacts?
  • Evaluate a role at this company? Paste the job posting.
  • Prepare interview stories specific to this company?"

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.