new-looplisted

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-Builder-Club/skills · ★ 1,211 · AI & Automation · score 78

Install: claude install-skill AI-Builder-Club/skills

# 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