New Loop
Spin up a new loop (domain) in a file-based knowledge base, bootstrap the substrate if...
Install
npx skills add AI-Builder-Club/skills --skill new-loop -g -a claude-code -y- Repository
- AI-Builder-Club/skills1.3k
- Category
- Testing
- Updated
- 2mo ago
- License
- See repository
- Context cost
- Lightabout 1,123 tokens
- Runs scripts
- No, instructions only
What it does
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.
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:
- name, kebab-case, the loop's home folder (
domains/<name>/). Keep it short. - goal, one line: the outcome this loop drives.
- cadence,
manual/daily/weekly/ a cron expr. Defaultmanual. - what it does, what it consumes (signals? data? an inbox? a URL?) and produces (signals?
docs? a report? code changes shipped via
/verify?). - 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.mdandLOG.md, and- a
CLAUDE.mdthat has a "Knowledge base" section.
All present → the substrate exists; skip to Step 2.
Anything missing → read references/KNOWLEDGE_SETUP.md and follow it, it copies in
ARCHITECTURE.md + LOG.md, creates signals/ docs/ domains/ with their README schemas, and
injects the knowledge-base section into CLAUDE.md (or scaffolds one from
references/CLAUDE.template.md). It's idempotent: it only creates what's missing.
(Read references/ARCHITECTURE.md once if you haven't, it's the model this skill instantiates.)
