How do I install the Install Loop skill?

Run npx skillmds@latest add cobusgreyling/install-loop in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Install Loop safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Install Loop?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Install Loop free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Install Loop?

cobusgreyling (@cobusgreyling) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Install Loop by cobusgreyling — Agent Skill

Name: Install Loop
Rating: 4.2 (5 reviews)
Author: cobusgreyling

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.

File contents

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

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.

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`
One GitHub Action, almost no files	`thin-loop`

Pick tool — claude | grok | codex | opencode (default claude).
Scaffold
```
npx @cobusgreyling/loop init . --pattern <pattern> --tool <tool>
```
Optional harness (only if human wants Foundry): add --with-foundry.
Doctor
```
npx @cobusgreyling/loop doctor .
```
- Exit 0 = healthy · 1 = warnings · 2 = blocked
- Follow the top 3 printed actions; do not invent extra architecture.

Cost check before high-cadence schedules:

npx @cobusgreyling/loop cost -p <pattern> -l L1 -c 1d

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.

---name: install-loopdescription: 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: ```bash 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): ```bash 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` | | One GitHub Action, almost no files | `thin-loop` | 3. **Pick tool** — `claude` | `grok` | `codex` | `opencode` (default `claude`). 4. **Scaffold** ```bash npx @cobusgreyling/loop init . --pattern <pattern> --tool <tool> ``` Optional harness (only if human wants Foundry): add `--with-foundry`. 5. **Doctor** ```bash 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: ```bash 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): ```bash 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.

Frequently asked questions