new-loop
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.
npx skills add AI-Builder-Club/skills --skill new-loop --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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
- When to use
- Inputs to gather (ask only what's missing)
- Procedure
- 1. Bootstrap the substrate (one-time; skip if already set up)
- 2. Scaffold the loop README
- 3. Do ONE real test run
- 4. Report back
- Notes
What does the new-loop skill do?
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.
How do I install it?
Run `npx skills add AI-Builder-Club/skills --skill new-loop --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From AI-Builder-Club/skills, a repository with 1,147 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.