# Add to your Claude Code skills
git clone https://github.com/AI-Builder-Club/skillsskills is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by AI-Builder-Club. Codebase harness + loop engineer. It has 769 GitHub stars.
skills's catalog security scan is still queued. You can run an instant dependency and prompt-injection check now with the "Scan for vulnerabilities" button above.
Clone the repository with "git clone https://github.com/AI-Builder-Club/skills" and add it to your Claude Code skills directory (see the Installation section above).
skills is primarily written in JavaScript. It is open-source under AI-Builder-Club on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh skills against similar tools.
No comments yet. Be the first to share your thoughts!
Unlocks once the catalog security scan passes (runs nightly).
The deep catalog scan for this skill is still queued. Run an instant dependency check now instead.
A Claude Code plugin marketplace of the skills we share at AI Builder Club for building loop engineers: agents that get triggered on their own, pick up work, ship it, verify it, and log what they learned, so the work compounds without you prompting every step. It's the productized version of the setup my team runs in production.
Two flagship skill sets (more to come):
The shift: you stop prompting a coding agent task-by-task, and start designing loops.
A loop is an agent that wakes up on a trigger (a cron, a webhook, an incident, another agent), does some investigation and work, and writes what it found and did into a shared, file-based memory. Next run it reads that memory and keeps going. The real power is compounding: many loops (support, SEO, product, ads) read and write the same folders, so a friction the support loop logs can get picked up by the product loop, and a keyword the ads loop finds can feed the SEO loop. One shared brain, many loops.
Building one comes down to four ingredients:
loops skills.codebase-harness skills.This single skills plugin ships both sets — giving you #2 and #4, plus the
scaffolding to add the rest.
Want the full walkthrough of the concept and how my team designs compounding loops? Watch the video:
/plugin marketplace add AI-Builder-Club/skills
/plugin install skills@ai-builder-club
One plugin, all the skills below.
/setup-codebase-harness — make a code repo agent-readyRun it in the code repo your agents work in, so they can run, test, and verify their own work. It orchestrates the harness skills below — pull in only what the repo needs.
/new-loop — build your shared brainRun it where your agent's memory should live. First run bootstraps the knowledge base
(creates ARCHITECTURE.md, LOG.md, the signals/ docs/ domains/ folders, and a knowledge-base
section in your CLAUDE.md); then it scaffolds the loop, does one real test run, and logs it.
Run it again any time to add another loop.
Codebase harness — make a repo agent-ready
| Skill | Use it when… |
|---|---|
setup-codebase-harness |
Onboarding a repo to agent-driven dev — the master that orchestrates the four below. |
dev-local-setup |
You need a one-command local dev stack (scripts/dev-local.sh up). |
e2e-setup |
The repo has no (or weak) e2e — add a real per-PR test gate. |
crabbox-setup |
Loops ship code in parallel — give each agent its own isolated cloud stack (one laptop can't run N). The cloud counterpart to dev-local. |
pr |
A change is ready — a fresh sub-agent proves the feature works, then opens the PR with proof. |
Loops — the shared knowledge base
| Skill | Use it when… |
|---|---|
new-loop |
You want a new loop/workstream the agent owns (bootstraps the knowledge base on first run). |
After setup, each session the agent reads CLAUDE.md + the relevant domain README, does work,
writes artifacts, and appends to LOG.md. For code changes it drives ship-change and ships via /pr.
git. That's the only hard dependency for the knowledge base + harness.crabbox-setup (optional, for parallel cloud boxes) needs the crabbox CLI + a provider
(Daytona: daytona CLI / DAYTONA_API_KEY).skills/ a Claude Code plugin (also a marketplace)
├── .claude-plugin/
│ ├── marketplace.json marketplace: ai-builder-club
│ └── plugin.json plugin: skills (source ".")
└── skills/ top-level skills
├── new-loop/ (loops) — + references/: ARCHITECTURE · LOG · KNOWLEDGE_SETUP · CLAUDE.template
├── setup-codebase-harness/ (harness) — orchestrator
├── dev-local-setup/ (harness)
├── e2e-setup/ (harness)
├── crabbox-setup/ (harness) — isolated cloud box per agent
└── pr/ (harness) — verify-before-ship (+ ship-change.js)
These skills get you the structure. If you want to learn how to actually build agents and run compounding loops for your own business, that's what I go deep on inside AI Builder Club: weekly live builder workshops, courses on production AI agents, AI coding beyond the basics, and building your first LLM apps, plus a community of people building the same way.
Built by Jason Zhou (AI Jason).