agentleFS
sree-datasree-data/job-search-agent/.claude/skills/research-company/SKILL.md

research-company

Skill0 starsChanged 2 months agoMITView on GitHub

Build a short company brief for outreach and interview prep. Usage /research-company <company name>

4 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions4 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 4

    1. GetBrew/growth-engineer★ 218same name
    2. spirosbax/insaight★ 32same name
    3. CodesWhat/careerrat★ 4same name
    4. Ben-Bot-22/job-hunt-kit★ 2same name

    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 repository7 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 1

    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. Very specific:

    Use web search and web fetch.

    line 10
  2. Distinctive:

    Do not make anything up. If a section has nothing verifiable, say so in one line and move on.

    line 20

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

Research company

Argument: company name (or a job id from pipeline/jobs.csv).

Use web search and web fetch. Spend at most 6 to 8 searches. Write the brief to drafts/research/<company-slug>.md and print it.

Cover, in this order, each in two or three lines:

  1. What they do and roughly how big the data/engineering org is.
  2. Data stack. Look at their engineering blog, job postings, conference talks, GitHub, and tech-stack sites. Name the actual tools (Snowflake, Databricks, Azure, dbt, Airflow, Power BI, etc.). Mark anything unverified as such.
  3. Recent news that a data engineer would care about: a migration, a platform build-out, an acquisition, a new product, layoffs or hiring pushes.
  4. Sponsorship: any public evidence they sponsor H1B (public disclosure data, their own postings, Glassdoor-style reports). Say "no evidence found" if none.
  5. Hooks: three specific things Alex could reference in a message. A named project, a talk by a named engineer, a blog post, a public problem they've described. Each hook needs a URL.
  6. Fit: one honest line on why Alex is or isn't a good match, based on profile/background.md.

Do not make anything up. If a section has nothing verifiable, say so in one line and move on.

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.