research-company
Skill218 starsChanged 47 days agoMITView on GitHub
Research a company from its domain and write its growth.engineer catalog files — companies/<handle>/company.md (who they are and how an agent connects: MCP server, CLI, API) and up to five companies/<handle>/tools/<function>.md (documented go-to-market calls) — from the vendor's own docs, with a source for every fact. Use when asked to add a company or domain to the catalog, to find a company's MCP tools or API endpoints, or to re-check an existing company's files.
- Reads credentials
4 other projects use a version of this.
Adopted by
Most recently taken up by
- CodesWhat/careerrattheir own version, first seen Nov 3, 2026
- spirosbax/insaighttheir own version, first seen Oct 13, 2026
- Ben-Bot-22/job-hunt-kittheir own version, first seen Oct 9, 2026
- sree-data/job-search-agenttheir own version, first seen Sep 11, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- spirosbax/insaight★ 32same name
- CodesWhat/careerrat★ 4same name
- Ben-Bot-22/job-hunt-kit★ 2same name
- sree-data/job-search-agent★ 0same 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 repository3 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- add-workflowSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 3 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
If companies/<handle>/ exists, you are updating it: re-verify every fact.
- Distinctive: line 30
Only official sources count: the vendor's domains, its docs site, its GitHub organization.
- Very specific: line 33
MCP: Search the vendor's docs for "MCP" (WebSearch with allowed_domains: [<domain>, docs.<domain>]).
- Distinctive: line 43
Never write a URL that carries a secret (a per-user MCP link with a token in it).
- Very specific: line 82
Leave out anything you couldn't confirm on an official page.
- Very specific: line 87
Every company needs one. Keep an existing logo: unless it no longer matches the icon the company's own site shows.
- Very specific: line 90
Read the homepage's <link rel="icon"> and apple-touch-icon tags and pick the current icon, not a wordmark: the apple-touch-icon, the …
- Distinctive: line 118
Use a third-party server, wrapper or aggregator as a company's way in.
“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.
Files
Research a company
Turns a domain into catalog files an agent can run. The file format is defined in
companies/README.md — read it first and copy its templates; this skill only says
how to find the facts. Every fact you write must be on a page you fetched.
Input: one or more domains (stripe.com). In bulk mode (the caller says so)
you don't edit tags.yml or workflows/ and you don't run pnpm content:check —
report instead; the caller merges and checks the batch.
Output: the files, a logo, and a report (step 6).
1. Place the company
- The handle is the brand in kebab-case (
stripe,customer-io), following the handle rules incompanies/README.md. - If
companies/<handle>/exists, you are updating it: re-verify every fact. Rename a tool file whose name isn't its function (enrich-contacts.md→enrich-person.md), list the old key underaliases:so its URL redirects, and report the rename. A tool whose call no longer exists getsstatus: deprecated(still visible, with a warning) — never deleted, since its key is a URL — and the report names every workflow step that uses it.
2. Find how an agent connects
Only official sources count: the vendor's domains, its docs site, its GitHub organization. Never blogs, directories, marketplaces or third-party servers.
- MCP. Search the vendor's docs for "MCP" (
WebSearchwithallowed_domains: [<domain>, docs.<domain>]).- The MCP Registry (
https://registry.modelcontextprotocol.io/v0/servers?search=<brand>) can point to a server; an entry counts only when its namespace is the vendor's reverse domain (com.stripe/mcp) or a GitHub org the vendor's docs link to. - Match by domain, never by name:
apolloreturns Apollo GraphQL, not Apollo.io. - The registry is incomplete — no entry doesn't mean no server.
- Record the remote
url(or localcommand), the auth, and the tool names exactly as the vendor lists them. A remote server that takes an API key can't be written yet: note it and use the API. - Never write a URL that carries a secret (a per-user MCP link with a token in it).
- The MCP Registry (
- API. From the API reference: the base
url, the auth (none,oauth,api_keywith theenvvar — the docs' name, else<BRAND>_API_KEY— plusheaderandschemewhen it isn'tAuthorization: Bearer), and thekeyUrlwhere a key is created. A host that differs per account is a snake_case placeholder in braces (https://{subdomain}.zendesk.com/api/v2), and the way'snotessay where the value comes from; Basic auth'snotessay which pair the variable encodes. - Way notes. Anything an agent must know to use a way at all — a setting an
admin turns on first, a regional host — goes in that way's
notes(one line, at most 280 characters). - CLI. From the CLI docs: the
installcommand and thebinary.
3. Choose up to five functions
- Go-to-market work only — what a growth workflow does: find or enrich people and
companies, create or update CRM records, send email or messages, book meetings,
track events, collect payments, research accounts, write copy. Each maps to one
capabilityintags.yml; in bulk mode, propose a new one instead of adding it. - One file = one function. Name the file after it (
create-payment-link.md,enrich-person.md), never after the capability. - For each: the exact call on every way in that has it, as the docs print it — the
MCP tool name, the CLI command (starting with the binary),
METHOD /pathfor the API — anddocs:, the page that names the call. Prefer functions reachable over MCP. - Two tools whose calls are all the same are one tool. A generic MCP tool that
takes the endpoint as an argument (
stripe_api_read) may serve several tools whose API calls differ; each tool'sapi:names the endpoint it runs. - A tool file is its header alone — no body.
summarysays what the call does;notesholds what an agent must know before calling it — an id to fetch first, a result to poll for, a per-call limit, a cost, a side effect — in one line of at most 280 characters. Leavenotesout when there is nothing to know.
4. Write the files
- Copy the templates in
companies/README.md;updatedis today. namesays what the function does, starting with a verb ("Enrich a person", "Search people", "Create or update a contact");summaryis one plain sentence about what the call returns or changes — never "<Company>does this".- Leave out anything you couldn't confirm on an official page. A tool whose call
you couldn't confirm gets
status: draft— it stays out of the site.
5. Logo
Every company needs one. Keep an existing logo: unless it no longer matches
the icon the company's own site shows; then add the current one as a file.
Read the homepage's <link rel="icon"> and apple-touch-icon tags and pick
the current icon, not a wordmark: the apple-touch-icon, the largest square
PNG, or an SVG with fixed colours. Skip SVGs that use prefers-color-scheme:
they turn white for dark-mode viewers. If the homepage only has a tiny
favicon, the login or docs pages often link a 180px or 512px icon. Save it as
companies/<handle>/logo.<ext> (svg, png, jpg or webp): square, at least
64px, under 32 KB. Shrink a big one to 256px (WebP keeps gradients small).
pnpm content:check checks every rule.
A maintainer's pnpm logos:upload moves the file to cdn.growth.engineer and
writes logo: (docs/maintainers/logos.md). If you hold the CDN token, run it
before opening the pull request. If nothing fits, say so in the report.
6. Report
For each company:
- files written, renamed (old key → new key) and deleted
- a table: fact → the official URL it came from, notes included
- drafts, and why
- tags proposed for
tags.yml(namespace, slug, label, synonyms) - anything gated: a sales-only API, a waitlisted or key-only MCP server
Outside bulk mode, finish with pnpm content:check and fix what it lists.
Never
- Invent a call, URL, env var, tool name or fact.
- Use a third-party server, wrapper or aggregator as a company's way in.
- Print or paste an API key.
- Edit rendered output or app code.
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.

