new-loop

Solid

Spin up a new loop (domain) in a file-based knowledge base — bootstrap the substrate if it's missing, gather the loop's charter, scaffold domains/<loop>/README.md, then do ONE real test run and record it in the loop's Timeline and LOG.md. Use when the user says "set up a new loop", "create a domain", "start a new beat/workstream", or names a recurring job they want the agent to own.

AI & Automation 1,064 stars 141 forks Updated today

Install

View on GitHub

Quality Score: 83/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
0
Description 5%
100

Skill Content

# new-loop — spin up a new loop A **loop** (a `domain`) is a recurring thread of work the agent owns: a charter, a cadence, and the artifacts it produces. This skill creates one, proves it works with a single real run, and leaves behind a `domains/<loop>/README.md` that is the loop's live state. ## When to use The user wants to stand up a new workstream/beat/job (e.g. "a weekly SEO loop", "a support triage loop", "a competitor-watch loop"). Don't use this for a one-off task — that's a backlog line in an existing domain, or a `doc`/`signal`. ## Inputs to gather (ask only what's missing) Infer from the request; ask a short clarifying round only for what you can't: 1. **name** — kebab-case, the loop's home folder (`domains/<name>/`). Keep it short. 2. **goal** — one line: the outcome this loop drives. 3. **cadence** — `manual` / `daily` / `weekly` / a cron expr. Default `manual`. 4. **what it does** — what it consumes (signals? data? an inbox? a URL?) and produces (signals? docs? a report? code changes shipped via `/verify`?). 5. **tools/data** — sources or credentials it needs (point at a setup skill or `.env`; never inline secrets). If the request is already specific, infer all five and just confirm in your summary. ## Procedure ### 1. Bootstrap the substrate (one-time; skip if already set up) Check the knowledge-base repo root for: - `ARCHITECTURE.md` and `LOG.md`, and - a `CLAUDE.md` that has a "Knowledge base" section. **All present →** the substrate exists; s...

Details

Author
AI-Builder-Club
Repository
AI-Builder-Club/skills
Created
1 months ago
Last Updated
today
Language
Python
License
None

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Listed

loops

The full lifecycle for agentic loops — recurring, scheduled AI agents packaged as a portable LOOP.md (the agenticloops.dev standard: a trigger + skills + a prompt in one file any harness can install and run on a schedule). Use this whenever the user wants to FIND, INSTALL, RUN, or BUILD a loop: "find a loop for X", "is there a loop that…", "install a recurring agent that does X", "run this loop", as well as "create a loop", "make an agentic loop", "write a LOOP.md", "turn this into a recurring agent", "schedule an agent", "set up a cron job for an agent", or any description of a repeating job they want an agent to do on a timer (a daily digest, a competitor watcher, a triage sweep, a report pipeline, "email me X every morning", "check Y every hour") — even if they never say the word "loop". Always search the directory first and install an existing loop when one fits; author a new LOOP.md only when nothing does. This is the loop-level analogue of skill-creator + find-skills combined. For an ad-hoc in-session m

1 Updated today
5dive-ai
Web & Frontend Listed

loop-design

Use when creating OR modifying any recurring loop - a scheduled agent, /loop task, cron job, or hook-driven automation. Enforces the loop conventions in ~/agent-improvement/loops/README.md as required declarations and scaffolds the loop's state files. Also used to apply approved retrospective refinements to an existing loop.

0 Updated 2 days ago
mwgrant21
AI & Automation Listed

loop-designer

Use this skill when the user says turn this into a loop, run this on a schedule, automate this daily, build me a loop, make this recurring, design a loop for a task, or loop this task — any request to make a one-off task a recurring autonomous job. Interviews minimally (goal, sources/inputs, output destination, schedule), then generates a five-part loop spec (Discover, Plan, Execute, Verify with a separate verifier checklist, Stop-or-Repeat), a non-negotiable guardrails block (max-iterations cap, cost ceiling, seen-log cross-run dedup, no-destructive-actions allowlist, completion/trip notification), and two ready-to-paste runners — a Claude Code Routine prompt and a local cron/launchd variant. Do NOT use for improving an existing prompt ("improve this prompt" is prompt-optimizer-loop's job), for one-off tasks, for debugging an already-built loop, or to run something on an interval in the current session — the built-in /loop command does that; this skill designs durable guarded loops, it doesn't run them.

2 Updated 5 days ago
Abhillashjadhav