loop-library — Claude Code plugin: what it does, how to install
Guides you through designing, auditing, and finding repeatable AI agent loops with explicit guardrails and stop conditions. Helpful for managing Claude Code autonomy.
/plugin marketplace add alirezarezvani/claude-skills
/plugin install loop-library@claude-code-skillsWhat loop-library does
The plugin treats agent workflows as bounded feedback loops rather than unchecked autonomous runs. It helps discover repeated project work, structure step-by-step actions, set up verification rules, and define clear handoffs. You invoke it directly via /loop-library with a task description or a draft loop for review.
The 26+ published community recipes do not live inside this repository. They are pulled at runtime from a live database-backed catalog. If that catalog cannot be reached, the tool tells you discovery is unavailable instead of outputting stale memory. Without an active internet connection, you cannot browse existing published recipes.
What it helps with
- turn repeated repository tasks into bounded feedback loops
- audit an existing agent loop to repair only breaking issues
- find a published recipe to keep project documentation fresh
- define explicit verification checks and stopping criteria for agent actions
Example prompts for the agent
- /loop-library Find a published loop for keeping our documentation current.
- /loop-library Analyze this repo for repeated work and turn the best candidate into a loop.
- /loop-library Audit this loop and repair only material problems: [paste loop]
How to install loop-library
Plugin marketplace
/plugin marketplace add alirezarezvani/claude-skills/plugin install loop-library@claude-code-skillsStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about loop-library
How to install loop-library in Claude Code?
Run /plugin marketplace add alirezarezvani/claude-skills to register the catalog, then run /plugin install loop-library@claude-code-skills.
What does loop-library do?
It provides an interactive guide to discover, audit, adjust, and build agent workflows. Each loop defines explicit triggers, steps, verification gates, guardrails, and handoff points to prevent runaway execution.
Why are published recipes missing from the repository?
The 26+ recipes stay in an external database-backed catalog fetched on demand from https://signals.forwardfuture.ai/loop-library/catalog.md. If the server is offline, the tool reports discovery as unavailable so that you never receive outdated patterns.
Source text
loop-library · MIT
# Loop Library (vendored skill) This folder is a **verbatim copy** of the `loop-library` skill from [Forward-Future/loop-library](https://github.com/Forward-Future/loop-library) (`skills/loop-library/`). `SKILL.md`, `agents/openai.yaml`, `references/discover.md`, and `references/audit.md` are unchanged from upstream (byte-for-byte). Licensed under the [MIT License](LICENSE) © Forward Future. ## What this skill is An installable guide that helps an AI agent **discover, find, audit, repair, adapt, or design repeatable agent loops** through conversation. A loop is a bounded feedback system — what to do, how to check it, what to try next, and when to stop — not permission for endless autonomy. Invoke it by describing a task, e.g.: ```text /loop-library Find a published loop for keeping our documentation current. /loop-library Analyze this repo for repeated work and turn the best candidate into a loop. /loop-library Audit this loop and repair only material problems: [paste loop] ``` ## About the published loops The individual published loops (the 26+ practitioner recipes) are **not** stored in this folder, and they are **not** in the upstream Git tree either. Per the upstream README they are "intentionally not committed to GitHub" — they live in the live, database-backed catalog and are fetched at runtime: - Catalog (Markdown): <https://signals.forwardfuture.ai/loop-library/catalog.md> - Catalog (JSON): <https://signals.forwardfuture.ai/loop-library/catalog.json> The skill reads this live catalog as the single source of truth when it recommends a published loop. If the live catalog is unreachable, the skill reports that published-loop discovery is temporarily unavailable rather than substituting stale or memorized content — this is by design, so the catalog is never forked out of date. ## Updating Re-vendor from upstream when the skill changes: ```bash npx skills add Forward-Future/loop-library --skill loop-library --agent claude-code -g -y # or copy skills/loop-library/ from a fresh clone of Forward-Future/loop-library ```
© Alireza Rezvani · MIT · alirezarezvani/claude-skills