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

How to give an agent the full catalog in one document with Growth Engineer

Load llms-full.txt, or run the site locally, so an agent can reason over every file.

Who it is forA team lead building an internal agent who needs every company, tool and workflow in one place.

The problemFetching files one at a time is slow, and the agent may miss a tool that fits the job.

The outcomeThe agent has one document with every company, tool and workflow file and can choose which play fits a goal.

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. Fetch the full catalog with curl https://www.growth.engineer/llms-full.txt. (inferred, check the README)
  2. Save the output to a file and attach it to your agent's context or project.
  3. Ask the agent to list the workflows whose inputs you already have. (inferred, check the README)
  4. To run the site locally, run pnpm install and then pnpm dev.
  5. Open http://localhost:3000 and add .md to any company, tool or workflow URL to see the file an agent gets.

Prompt for your agent

Read the catalog at https://www.growth.engineer/llms-full.txt and list every workflow whose inputs match <the inputs you have>. Report the workflow titles and the tools each one uses, and confirm that each title appears in the document before you list it.

Caveat. The full document is generated from the catalog at build time, so it shows the published state of the site and not any unmerged pull request.

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