DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to add a company and its tools to the catalog with Growth Engineer

Open a pull request that adds a company file and its tool files, checked by pnpm.

Who it is forA developer or go-to-market engineer who uses a vendor tool that the catalog does not yet cover.

The problemAn agent cannot call a tool that has no file, and the vendor's docs do not say which key, endpoint or MCP server to use.

The outcomeA pull request that adds a validated company file and tool files, with each tool linking the docs page that documents its call.

What you need first

  • An AI agent that can add an MCP server or paste in a text file, such as Claude, Claude Code, ChatGPT, Codex or Cursor
  • Accounts and credentials for any vendor tool a workflow uses, since each company file names the credential it needs
  • For contributing: a GitHub account, Node 22+ and pnpm 11 (corepack enable installs the pinned version)

Steps

  1. Run pnpm install in your clone of the repository.
  2. Use the research-company skill in .agents/skills/research-company/SKILL.md, or follow companies/README.md, to write companies/<key>/company.md and tools/<key>.md.
  3. Link the vendor docs page that documents each tool's call.
  4. Run pnpm content:check and fix every problem it reports, with each one tied to its file.
  5. Open a pull request, since CI runs the same check.

Prompt for your agent

In the growth-engineer repository, use the research-company skill to add a company file and its tool files for <vendor>, citing the vendor's own documentation for each tool. Run pnpm content:check and report the result, and do not finish until it passes.

Caveat. The README says facts come from each vendor's own documentation, so an entry is only as current as the docs page it links.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page