/install-loop
Install Loop Engineering into a project via the unified CLI front door (@cobusgreyling/loop). Prefer this over invoking loop-init / loop-audit separately. Week-one is report-only; never enable auto-merge or unattended fixes unless the human explicitly asks and doctor is healthy.
$ npx -y skills add cobusgreyling/loop-engineering --skill install-loop --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/install-loop
Context preview
The summary Claude sees to decide when to auto-load this skill.
Install Loop Engineering into a project via the unified CLI front door (@cobusgreyling/loop). Prefer this over invoking loop-init / loop-audit separately. Week-one is report-only; never enable auto-merge or unattended fixes unless the human explicitly asks and doctor is healthy.
SKILL.md
install-loop.SKILL.mdname: install-loop
description: >
Install Loop Engineering into a project via the unified CLI front door
(@cobusgreyling/loop). Prefer this over invoking loop-init / loop-audit
separately. Week-one is report-only; never enable auto-merge or unattended
fixes unless the human explicitly asks and doctor is healthy.
Install Loop Engineering
Goal
Leave the repo with a scaffolded **report-only** loop, a **Loop Ready** score, and clear next actions — using the **single** CLI:
npx @cobusgreyling/loop
Do **not** deprecate or remove existing `loop-init` / `loop-audit` usages you find; both doors stay valid. Prefer `loop` for new work.
Steps
1. **Detect context**
- If `LOOP.md` or `STATE.md` already exists, run doctor only (skip init unless human asks to re-scaffold):
npx @cobusgreyling/loop doctor . --json
npx @cobusgreyling/loop status .- Otherwise continue.
2. **Pick pattern** (default: `daily-triage`) | Pain | Pattern | |------|---------| | Morning chaos / unclear priorities | `daily-triage` | | PRs stalling | `pr-babysitter` | | CI red / flakes | `ci-sweeper` | | CVE / Dependabot noise | `dependency-sweeper` | | Post-merge TODOs | `post-merge-cleanup` | | Stale release notes | `changelog-drafter` | | Noisy issues | `issue-triage` |
3. **Pick tool** — `grok` | `claude` | `codex` | `opencode` (default `grok`).
4. **Scaffold**
npx @cobusgreyling/loop init . --pattern <pattern> --tool <tool>
Optional harness (only if human wants Foundry): add `--with-foundry`.
5. **Doctor**
npx @cobusgreyling/loop doctor .
- Exit `0` = healthy · `1` = warnings · `2` = blocked
- Follow the **top 3** printed actions; do not invent extra architecture.
6. **Cost check** before high-cadence schedules:
npx @cobusgreyling/loop cost -p <pattern> -l L1 -c 1d
7. **Week-one rule**
- Report only. No auto-fix, no auto-merge.
- Tell the human the first `/loop` or scheduler command from init output.
- Suggest badge only when score is strong: `npx @cobusgreyling/loop badge .`
Compatibility
These remain fully supported (do not rewrite existing docs/scripts unless asked):
npx @cobusgreyling/loop-init .
npx @cobusgreyling/loop-audit . --suggest
Stop conditions
- Stop after doctor + first-run instructions unless the human asks for L2+.
- Never expand into fleet/memory/foundry unless score ≥ 80 **and** human opts in.
Read more
name: install-loop description: > Install Loop Engineering into a project via the unified CLI front door (@cobusgreyling/loop). Prefer this over invoking loop-init / loop-audit separately. Week-one is report-only; never enable auto-merge or unattended fixes unless the human explicitly asks and doctor is healthy.
Install Loop Engineering
Goal
Leave the repo with a scaffolded **report-only** loop, a **Loop Ready** score, and clear next actions — using the **single** CLI:
npx @cobusgreyling/loop
Do **not** deprecate or remove existing `loop-init` / `loop-audit` usages you find; both doors stay valid. Prefer `loop` for new work.
Steps
1. **Detect context**
- If `LOOP.md` or `STATE.md` already exists, run doctor only (skip init unless human asks to re-scaffold):
npx @cobusgreyling/loop doctor . --json
npx @cobusgreyling/loop status .- Otherwise continue.
2. **Pick pattern** (default: `daily-triage`) | Pain | Pattern | |------|---------| | Morning chaos / unclear priorities | `daily-triage` | | PRs stalling | `pr-babysitter` | | CI red / flakes | `ci-sweeper` | | CVE / Dependabot noise | `dependency-sweeper` | | Post-merge TODOs | `post-merge-cleanup` | | Stale release notes | `changelog-drafter` | | Noisy issues | `issue-triage` |
3. **Pick tool** — `grok` | `claude` | `codex` | `opencode` (default `grok`).
4. **Scaffold**
npx @cobusgreyling/loop init . --pattern <pattern> --tool <tool>
Optional harness (only if human wants Foundry): add `--with-foundry`.
5. **Doctor**
npx @cobusgreyling/loop doctor .
- Exit `0` = healthy · `1` = warnings · `2` = blocked
- Follow the **top 3** printed actions; do not invent extra architecture.
6. **Cost check** before high-cadence schedules:
npx @cobusgreyling/loop cost -p <pattern> -l L1 -c 1d
7. **Week-one rule**
- Report only. No auto-fix, no auto-merge.
- Tell the human the first `/loop` or scheduler command from init output.
- Suggest badge only when score is strong: `npx @cobusgreyling/loop badge .`
Compatibility
These remain fully supported (do not rewrite existing docs/scripts unless asked):
npx @cobusgreyling/loop-init . npx @cobusgreyling/loop-audit . --suggest
Stop conditions
- Stop after doctor + first-run instructions unless the human asks for L2+.
- Never expand into fleet/memory/foundry unless score ≥ 80 **and** human opts in.
Stop prompting. Design the loop. Get a score. loop init (or loop-init) scaffolds skills, state, and budget files, then prints your Loop Ready score and first loop command. loop doctor combines audit + sync + file checks into top-3 next actions.
Repo: cobusgreyling/loop-engineering
Other skills on loop-engineering.
- /budget-negotiator
An advanced skill for L3 autonomous loops. When the token budget nears exhaustion, the agent analyzes its ROI and autonomously drafts a negotiation request for a budget increase rather than silently failing.
Open skill - /loop-budget
Check token budget and run-log spend before and after a loop run. Enforces early exit when over budget or when there is no actionable work.
Open skill - /loop-constraints
Read loop-constraints.md at the start of every run and enforce every rule. This skill runs BEFORE triage or any action skill. Constraints are binding.
Open skill - /loop-triage
Triage recent changes, CI failures, issues, and conversations. Produces a concise, actionable findings report suitable for a loop to consume. Writes structured output to a state file or Linear board.
Open skill - /loop-verifier
Independent verification agent for loop-produced changes. Finds reasons to reject. Runs tests. Confirms diff scope. Use after minimal-fix or any implementer sub-agent — never in the same role as the implementer.
Open skill - /minimal-fix
Produce the smallest possible code change that fixes a specific, well-scoped issue (CI failure, reviewer comment, typo). Use only when the fix target is explicit. Never refactor unrelated code.
Open skill