find-skills

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 / github.com/5dive-ai/loops.

• Says "find a loop for X" or "is there a loop that does X"
• 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

loops

LOOP.md

npx agenticloops

5dive loop

• 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="…"]

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)

npx agenticloops find <query>

• "watch our competitors" →

  npx agenticloops find competitive intel

• "triage new PRs" →

  npx agenticloops find pr triage

• "daily security scan" →

  npx agenticloops find security

• "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 (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.

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

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.

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.)

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.

loops

orchestrate