# The awesome-llm-apps catalogue has two install recipes and one CI gate

> This is a directory of more than a hundred runnable LLM templates split across twelve category folders, published under Apache-2.0 by a maintainer who also runs a commercial tutorial site. The agent skills have a documented one-command install and a stated security and eval gate, while the starter agents are single-file Streamlit scripts whose run recipe appears exactly once in the README.

**Shubhamsaboo/awesome-llm-apps** — GitHub describes it as 100+ AI Agents, Agent Skills and RAG Apps - Free and Open Source.. The repository metadata lists Python as its primary language. The metadata lists the Apache-2.0 license. This article stays within the project description and details documented in the GitHub repository README.

- Repository: https://github.com/Shubhamsaboo/awesome-llm-apps
- Website: https://www.theunwindai.com
- Stars: 140,206 · Forks: 20,593
- Language: Python
- License: Apache-2.0
- Published: 2026-08-13 · Updated: 2026-08-18 · Language: en
- Canonical page: https://hysenlabs.com/projects/shubhamsaboo-awesome-llm-apps

## The skills install from a subdirectory URL, the agents install from a clone

Two different mechanisms, and the README shows each exactly once.

For an agent skill, a coding agent gets a new capability with one command.

```bash
npx skills add https://github.com/Shubhamsaboo/awesome-llm-apps/tree/main/agent_skills/project-graveyard
```

Then you ask it a plain English question, and the example given is asking why you never finish your side projects. The URL points at a subdirectory rather than the repository root, so the unit of distribution is one skill folder.

For a starter agent, you clone and run it locally.

```bash
git clone https://github.com/Shubhamsaboo/awesome-llm-apps.git
cd awesome-llm-apps/starter_ai_agents/ai_travel_agent
pip install -r requirements.txt
streamlit run travel_agent.py
```

Three lines after the clone, and the working directory is a single template folder. The practical consequence is that the catalogue is not one installable thing. Most of the twelve top-level directories have no run command anywhere in the README, so for anything outside these two examples you are reading the folder yourself.

## The security and eval gate is scoped to agent_skills, not to the agents

The strongest claim in the README is attached to one category. The agent skills are introduced as giving your coding agent new abilities, one command to install and plain English to use, and the statement is that every skill ships real code and passes a security plus eval CI gate. It names Claude Code, Codex, Cursor and other coding agents as the targets.

Nothing equivalent is said about the starter agents. They are introduced differently, as single-file agents that run with just an API key and described as a good place to start. That is a claim about convenience, not about review.

The gap matters because the two sets have different blast radius. A skill that inspects a diff or a manifest runs against text in your repository. One of the starter agents drives a real browser rather than an image API, and another is an agent with a wallet that pays per call for the data it needs, which means executing it moves money. A CI gate scoped to one directory does not cover the other, so the category you install from tells you how much review to expect before you press enter.

## Single-file means no shared library, so a provider break is your problem in every copy

The starter agents are described as single-file agents that run with just an API key. That is a deliberate simplicity, and it is also the architecture with the sharpest long-term cost once you have adopted more than one.

There is no shared package in the description and none in the install recipe. Each template is a directory with a requirements.txt, and the recipe installs into whatever environment is active. So if a model provider changes a response shape, a tool call signature or an SDK interface, there is no one place to fix it. Every copy you have vendored into a project is a separate edit, and the count of edits is the number of templates you took rather than the number of bugs.

The upside is real and worth keeping in view. A single file with one requirements.txt is something you can read end to end before running, which is more than you can say about most agent frameworks, and a template you have read is the fastest way to understand a pattern. The catalogue is a good teacher and a poor dependency.

## The provider-neutral headline is not what individual templates do

The top of the README says the templates work with Claude, Gemini, GPT, DeepSeek, Llama, Qwen and other open-source models. That is a statement about the catalogue.

Inside it, the templates name providers, SDKs and in one case three specific model versions. The Advisor Orchestrator Worker is described as a meta loop with Claude Fable 5.1 as advisor, GPT-6 Astra as orchestrator and Gemini 3.8 Flash as worker. The medical imaging agent does diagnostic analysis of X-rays and scans with Gemini. The finance agent does real-time stock analysis powered by Grok. The research agent is multi-agent topic research with the OpenAI Agents SDK.

So the neutrality is a property of the shelf, not of each box. What you actually get is whatever that template's requirements.txt and code assume, and because the install is a bare pip install into your active environment, the provider choice is made by the template rather than by you. The Dependency Doctor skill in the agent set, which checks a manifest for unpinned entries, duplicate constraints and yanked releases, is pointed at exactly the kind of manifest the install recipe hands you.

## An Apache-2.0 catalogue that routes to a commercial newsletter

The licence is Apache-2.0, and the README states it twice, once as a licence and once as a promise: clone it, ship it, sell it, 100% free and open-source. Apache-2.0 permits commercial redistribution, so the promise is consistent with the terms, subject to preserving the licence and copyright notices and any NOTICE file in the copies you ship.

The commercial shape sits alongside it. The repository homepage is theunwindai.com, the README links to step-by-step tutorials there, and the line under the run command says new templates drop weekly and offers to get them in your inbox on Unwind AI. The sponsor block at the top carries a TinyFish link with affiliate tracking parameters baked into the URL.

None of that makes the templates worse. It does mean the cadence and the incentive are aligned with publishing more, not with maintaining what is published. A catalogue that adds templates weekly, with no releases and no per-template version markers, gets longer faster than any individual entry gets revised.

## Twelve top-level folders, and the README groups them three ways

The repository root is a set of category directories with nothing else in it: agent_skills/, starter_ai_agents/, advanced_ai_agents/, advanced_llm_apps/, always_on_agents/, generative_ui_agents/, mcp_ai_agents/, rag_tutorials/, voice_ai_agents/ and ai_agent_framework_crash_course/, plus docs/ and the .github directory.

The README presents three of these as browsable groups and leaves the rest to the directory listing. Agent skills come first, then the starter agents as the single-file tier, then advanced agents described as production-style agents with tools, memory and multi-step reasoning.

That three-tier shape is the actual selection guide, and the tiers are defined by depth rather than by topic. A tier-one agent is one file. A tier-three agent has tools and memory. Nothing in between is spelled out, and the categories that get no section at all, including the always-on agents, the RAG tutorials and the MCP agents, are the ones where you have no idea from the README whether you are looking at a one-file demo or a service with a database.

Pick by opening the folder. That is the honest procedure and the README does not offer another.

## A template that writes for a spouse, a fraud investigation, and a medical scan, in one list

Read the starter list as a whole and the catalogue's range becomes clear, because these are adjacent entries.

An agent team that talks you through the post-breakup spiral sits between a blog-to-podcast converter and an agent that asks questions of any CSV or Excel file. Further down, the list has diagnostic analysis of X-rays and scans with Gemini, an agent that makes memes by driving a real browser, an agent that pays per call for data with no API keys, and multi-agent topic research with the OpenAI Agents SDK.

None of this is a criticism of the templates. A collection meant to be cloned and run has no reason to be narrow, and the breakup agent is a small multi-agent pattern that happens to be about feelings. But the list is a demonstration shelf, and the description of it, hand-built and tested end-to-end, describes how the entries were built rather than how far you should trust them in production.

The medical imaging and fraud investigation entries are the ones to treat with the most care, because their output is a diagnosis and an accusation, and nothing in the repository is a clinical or compliance review.

## Conclusion

Use it as a source of runnable starting points when you want to see one working implementation of an agent pattern, and read the file before you run it. Do not treat it as a library, because the starter agents are single-file scripts with no shared package, so a provider API break means editing every copy you adopted, and do not assume the security and eval gate covers everything, because that claim is scoped to the agent skills. Before you run anything from the starter set, check whether the template spends money on your behalf, since one of them is an agent with a wallet that pays per call, and pin your checkout by commit because the repository has no releases and templates arrive weekly.

## FAQ

### How do I run one of the apps in awesome-llm-apps?

Clone the repository, change into one template folder, install its dependencies and start the app. The README's recipe uses starter_ai_agents/ai_travel_agent with pip install -r requirements.txt and streamlit run travel_agent.py, and the starter tier is described as single-file agents that run with just an API key.

### How do I add a skill from awesome-llm-apps to my coding agent?

Run npx skills add with the URL of one skill subdirectory, for example the tree/main/agent_skills/project-graveyard path, and then ask the agent a plain English question. The skills are described as working with Claude Code, Codex, Cursor and other coding agents, and every one of them is stated to ship real code and pass a security and eval CI gate.

### What licence is awesome-llm-apps under?

Apache-2.0. The README states it in the subtitle line describing more than a hundred open-source agents, agent skills and RAG apps, and again in the licence line, and it says you can clone it, ship it and sell it with no cost.

### What categories does awesome-llm-apps cover?

The root holds agent_skills/, starter_ai_agents/, advanced_ai_agents/, advanced_llm_apps/, always_on_agents/, generative_ui_agents/, mcp_ai_agents/, rag_tutorials/, voice_ai_agents/ and ai_agent_framework_crash_course/. The README browses the first three in detail, describing the starter tier as single-file agents and the advanced tier as production-style agents with tools, memory and multi-step reasoning.

### Does awesome-llm-apps work with any model provider?

The README says the templates work with Claude, Gemini, GPT, DeepSeek, Llama, Qwen and other open-source models. Individual templates are not provider-neutral: the medical imaging agent uses Gemini, the finance agent is powered by Grok, the research agent uses the OpenAI Agents SDK, and the Advisor Orchestrator Worker names three specific model versions as advisor, orchestrator and worker.

## Sources

- [Official documentation](https://www.theunwindai.com)
- [Official README](https://github.com/Shubhamsaboo/awesome-llm-apps#readme)
- [Project repository](https://github.com/Shubhamsaboo/awesome-llm-apps)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/shubhamsaboo-awesome-llm-apps