find-loops · diff

git:20260701.f1126df to git:20260703.00f2f74

60 added, 70 removed. Audit A to A.

What this update changes in the checks

No check changed: every fixed check gives the same answer before and after this update.

A tripped check is a label, not a verdict: read the matched text and the lines below. This week's updates that newly trip a check.

---
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.
+ description: Helps users discover and install agentic loops (recurring, scheduled AI agents) when they ask "find a loop for X", "is there a loop that…", "install a recurring agent that does X", "schedule an agent to do X", or want a repeating job run on a timer (a daily digest, a competitor watcher, a triage sweep, an every-morning report) — even if they never say the word "loop". Use this to SEARCH the agenticloops.dev directory and INSTALL an existing loop. This is the loop-level analogue of find-skills. For AUTHORING a new loop when none fits, use the fuller `loops` 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`.
+ This skill helps you discover and install **agentic loops** from the open loops ecosystem — 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.
+ > An agentic loop is an installable, recurring AI agent defined in one file (a `LOOP.md`): a **trigger** (schedule/event), a set of **skills**, and a **prompt**. Any harness (Claude Code, Cursor, Codex, GitHub Actions, a 5dive runtime) can install and run it on a schedule. The standard lives at [agenticloops.dev](https://agenticloops.dev) / [github.com/5dive-ai/loops](https://github.com/5dive-ai/loops).
## 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
+ - Wants a **recurring / scheduled** agent for a job (hourly, daily, on an event)
+ - Describes a repeating job without saying "loop": "email me a digest every morning", "watch our competitors", "triage new PRs each day", "run a security scan nightly", "check Y every hour"
+ - Wants to browse or search the loops directory before building anything
- 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.
+ **Always try to find + install an existing loop before authoring a new one.** If nothing fits, hand off to the `loops` skill (which covers authoring a fresh `LOOP.md`).
- ## What is the agenticloops CLI?
+ ## The loops 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.
+ The package manager for loops is `npx agenticloops`. On a 5dive runtime, the native path is `5dive loop`.
**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/
+ - `npx agenticloops find [query]` — search the agenticloops.dev directory
+ - `npx agenticloops install <owner/loop> --dry-run` — validate + pre-flight, change nothing
+ - `npx agenticloops run <owner/loop> --harness=<id>` — one live run to see it work (optional)
+ - `npx agenticloops install <owner/loop> --yes` — register the recurring job
+ - `npx agenticloops list` / `npx agenticloops update [<slug>]` — manage installed loops
+ - Native on a 5dive box: `5dive loop find|show|install <slug> --onto=<agent> [--cron="…"]`
- ## How to Help Users Find Loops
+ **Browse loops at:** https://agenticloops.dev
- ### Step 1: Understand what they need
+ ## How to Help Users Find a Loop
- 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 1: Understand the Job
- ### Step 2: Browse the directory first
+ Identify:
- 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.
+ 1. The **job** (competitive intel, PR triage, security scan, news digest, report pipeline)
+ 2. The **cadence** (hourly, daily, on an event)
+ 3. Whether it's a single-agent job or a **pipeline** (gather → draft → publish = a multi-agent loop)
- ### Step 3: Search
+ ### Step 2: Search the Directory
```bash
npx agenticloops find <query>
```
- For example:
+ Examples:
- "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:
+ - "morning news digest" → `npx agenticloops find news digest`
- 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.
+ Or browse [agenticloops.dev](https://agenticloops.dev) directly (ci-analyst, intel-brief, autonomous-pr-loop, agentic-security-scanner, daily-news-radar, issue-triage-bot, …).
- ### Step 5: Present options
+ ### Step 3: Vet Before Recommending
- 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.
+ A loop **runs unattended on a schedule**, so vet it harder than a one-shot skill:
- ```
- 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.
+ 1. **Proof, not popularity.** The directory ranks on **verifiable, signed run receipts**, not stars — prefer a loop that emits receipts (proof it actually did the job).
+ 2. **Read the `requires` block** — the trust surface, listed *before* it runs: exactly which `cli` binaries, `secrets` (names only, never values), `mcp` servers, and `network` egress the loop touches. Confirm the user is comfortable with all of it.
+ 3. **Source reputation** — prefer official `5dive-ai/loops` entries over an unknown author.
+ 4. **Can the harness honor the trigger?** A loop needs *scheduling*. A run-only harness (an IDE) can run it once but can't fire it on a timer — target a scheduler (5dive, GitHub Actions, cron). The installer warns otherwise.
- Install it:
- npx agenticloops install 5dive-ai/loops/autonomous-pr-loop --harness=claude-code
+ ### Step 4: Present Options to the User
- Learn more: https://agenticloops.dev/5dive-ai/loops/autonomous-pr-loop
- ```
+ For each relevant loop, show:
- ### Step 6: Offer to install (and test-run first)
+ 1. The loop name + what it does
+ 2. Its **cadence** and whether it emits **run receipts** (proof)
+ 3. Its `requires` trust surface (cli / secrets / mcp / network)
+ 4. The install command
+ 5. A link to learn more on agenticloops.dev
- If the user wants it, dry-run to pre-flight, optionally test one run, then install:
+ ### Step 5: Install (dry-run first)
```bash
- npx agenticloops install <owner/loop> --dry-run # validate + pre-flight, change nothing
+ npx agenticloops install <owner/loop> --dry-run # validate + pre-flight, no changes
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
+ # native on a 5dive box:
+ 5dive loop install <slug> --onto=<agent> [--cron="…"]
```
- Supply any `requires.secrets` host-side at install (the installer prompts) — secrets are names in the file, never values.
+ Supply any `requires.secrets` host-side at install (the installer prompts) — secrets are **names** in the file, never values. `--harness` auto-detects.
- ## Common loop categories
+ ### Step 6: When No Loop Fits
- | 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 |
+ If the directory has nothing for the job:
- ## Tips for effective searches
+ 1. Say so honestly — no existing loop matched.
+ 2. Hand off to the **`loops` skill**, which covers authoring a new `LOOP.md` (the loop-level analogue of skill-creator). Don't hand-roll one here — find-loops is discovery + install; `loops` owns building.
- 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.
+ Example:
- ## When no loop is found
+ ```
+ I searched the loops directory for "xyz" but didn't find a matching recurring agent.
+ I can build you one — a LOOP.md that runs your job on a schedule. Want me to draft it?
+ (That uses the `loops` skill, which handles authoring.)
+ ```
- If nothing fits:
+ ## Tips
- 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.
+ 1. **Search the job, not the tool** — `find pr triage`, not `find github`.
+ 2. **Try alternative terms** — if "deploy" misses, try "release" or "ci-cd".
+ 3. **Prefer receipts + official sources** — a loop runs on its own on a timer; trust matters more than for a one-shot skill.
+ 4. **Confirm the harness can schedule** before promising a recurring install.
- ```
- 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?
- ```
+ Related: the fuller **`loops`** skill (find + install + **build**) and **`orchestrate`** (ad-hoc in-session multi-agent runs). find-loops is the lightweight discovery front door.