find-loops · git:20260701.f1126df · 2026-07-01 · sha256 4a13ed7287ed3c3e
find-loops git:20260701.f1126dfA
Immutable. This exact content never changes and is served at /api/v1/blob/4a13ed7287ed3c3e.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_ybbceuwfdtuvv6mi/4a13ed7287ed3c3eeb1e51e7f22364356c50cc5ba1588285faacc5b16ec456fb.json
Then /plugin install find-loops@markdownregistry-ybbceuwfdtuvv6mi in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
--- name: find-loops description: Helps you discover and install agentic loops — recurring, scheduled AI agents packaged as a LOOP.md — when the user asks "find a loop for X", "is there a loop that…", "install a recurring agent that does X", "what loops exist for Y", or wants to automate a repeating job on a timer with an existing loop instead of building one. Use this whenever the user is looking for an off-the-shelf recurring agent (a daily digest, a competitor watcher, a triage/scan/report job) or wants to browse, search, or install from the agenticloops directory. This is the loop-level analogue of find-skills. To AUTHOR a new loop instead of installing one, use the loop-creator skill. --- # Find Loops This skill helps you discover and install **agentic loops** from the open [agenticloops.dev](https://agenticloops.dev) directory — the loop-level analogue of `find-skills`. > An agentic loop is an installable, recurring AI agent defined in one `LOOP.md`: a trigger, a set of skills, and a prompt. It runs on a schedule and completes a whole job on any harness. ## When to Use This Skill Use this skill when the user: - Says "find a loop for X" or "is there a loop that does X" - Wants a recurring/scheduled agent for a repeating job (a daily digest, a competitor watcher, a triage sweep, a report pipeline) - Asks "what loops exist for Y" or wants to browse the directory - Wants to install, update, or manage a loop they already know - Describes an ongoing job they'd rather adopt than build from scratch If the user wants to **author** a new loop, use `loop-creator` instead. If they want an ad-hoc in-session multi-agent run (spawn/verify/panel), use the `loops` skill. ## What is the agenticloops CLI? `npx agenticloops` is the installer for the agentic-loops ecosystem. A loop is a single `LOOP.md` (frontmatter manifest + prompt) that any harness can install and run on a schedule. **Key commands:** - `npx agenticloops find <query>` — search the public directory by keyword - `npx agenticloops install <owner/loop> [--harness=<id>]` — fetch, validate, install its skills, pre-flight `requires`, and register the recurring job - `npx agenticloops list` — show loops installed on this machine + install counts - `npx agenticloops update [<slug>]` — re-fetch + re-install (all, or one) - `npx agenticloops run <owner/loop|path>` — execute a loop's chain once now (what a schedule fires) — good for a test run before scheduling **On a 5dive runtime**, the native path is `5dive loop install <slug> --onto=<agent>` (and `5dive loop show <slug>` to peek). **Browse loops at:** https://agenticloops.dev/ ## How to Help Users Find Loops ### Step 1: Understand what they need Identify the **job** (competitive intel, PR triage, security scan, news digest), the **cadence** (hourly, daily, on an event), and whether it's a single-agent job or a pipeline (gather → draft → publish, a multi-agent loop). ### Step 2: Browse the directory first Check [agenticloops.dev](https://agenticloops.dev) — it lists the current loops (ci-analyst, intel-brief, autonomous-pr-loop, agentic-security-scanner, daily-news-radar, issue-triage-bot, and more). If a well-known loop already covers the job, start there. ### Step 3: Search ```bash npx agenticloops find <query> ``` For example: - "watch our competitors" → `npx agenticloops find competitive intel` - "triage new PRs" → `npx agenticloops find pr triage` - "daily security scan" → `npx agenticloops find security` ### Step 4: Verify before recommending **Don't recommend a loop on the search hit alone.** A loop *runs unattended on a schedule*, so vet it harder than a skill: 1. **Proof, not popularity.** The directory ranks on **verifiable, signed run receipts**, not stars — prefer a loop that emits receipts (shows it actually ran the job) over one that's merely listed. 2. **Read the `requires` block.** It's the trust surface: exactly which `cli` binaries, `secrets` (names), `mcp` servers, and `network` egress the loop touches — *before* it ever runs. Make sure the user is comfortable with all of it. 3. **Source reputation.** Official `5dive-ai/loops` entries are more trustworthy than an unknown author's repo. 4. **Can your harness honor the trigger?** A loop needs *scheduling* — a run-only harness (an IDE) can run it once but can't fire it on time. The installer warns; target a scheduler (5dive, GitHub Actions, cron) for a real recurring loop. ### Step 5: Present options Show the user: the loop's job + tagline, its trigger (schedule), what it `requires`, the install command, and a link to its page on agenticloops.dev. ``` Found one: "autonomous-pr-loop" — reviews every new PR, leaves inline comments, and re-checks after pushes. Trigger: on pr-opened. Requires: gh CLI. Ranks on signed review receipts. Install it: npx agenticloops install 5dive-ai/loops/autonomous-pr-loop --harness=claude-code Learn more: https://agenticloops.dev/5dive-ai/loops/autonomous-pr-loop ``` ### Step 6: Offer to install (and test-run first) If the user wants it, dry-run to pre-flight, optionally test one run, then install: ```bash npx agenticloops install <owner/loop> --dry-run # validate + pre-flight, change nothing npx agenticloops run <owner/loop> --harness=<id> # optional: one live run to see it work npx agenticloops install <owner/loop> --yes # register the recurring job ``` Supply any `requires.secrets` host-side at install (the installer prompts) — secrets are names in the file, never values. ## Common loop categories | Category | Example queries | | --- | --- | | Research / intel | competitive intel, market briefing, news radar | | Code / PRs | pr review, pr triage, issue triage, ci failure | | Security | security scan, malicious-code scan, SOC alert triage | | Ops / DevOps | devops supervisor, accessibility review, performance | | Digests / briefings | daily digest, personal briefing, research brief | ## Tips for effective searches 1. **Search by the job, not the tool** — "competitor watcher" beats "scraper". 2. **Try alternate terms** — "intel" / "research" / "market"; "triage" / "review". 3. **Prefer the official directory** — `5dive-ai/loops` entries are validated against the spec. ## When no loop is found If nothing fits: 1. Say so plainly — no forced match. 2. Offer to do the job directly with your general capabilities. 3. If it's a recurring need, offer to **author a new loop** with the `loop-creator` skill — that's the create side of this pair, and the new loop can be published back to the directory. ``` No existing loop matched "xyz". I can do the job directly now — or, since it's recurring, author a purpose-built loop for it with loop-creator and schedule it. Want me to build one? ```