compounding-setup
/compounding-setup
Install and configure the compounding kit on this machine (store, CLAUDE.md, memory folder, headless auth, cron). Use when the user says "set up the compounding kit", "install the loops", "compounding setup", or right after the plugin was installed.
- Author
- byODCUS ↗
- Repository
- odcus-compounding-kit ↗
- Licence
- MIT
- Last repository change
- 09.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 09.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Install and configure the compounding kit on this machine (store, CLAUDE.md, memory folder, headless auth, cron). Use when the user says "set up the compounding kit", "install the loops", "compounding setup", or right after the plugin was installed.
Triggers from the description
Original author description
Install and configure the compounding kit on this machine (store, CLAUDE.md, memory folder, headless auth, cron). Use when the user says "set up the compounding kit", "install the loops", "compounding setup", or right after the plugin was installed.
How it works
- 1. Run the setup script
- 2. CLAUDE.md
- 3. Memory folder
- 4. Headless auth for jobs
- 5. Schedule
- 6. Verify
SKILL.md preview
---
name: compounding-setup
description: Install and configure the compounding kit on this machine (store, CLAUDE.md, memory folder, headless auth, cron). Use when the user says "set up the compounding kit", "install the loops", "compounding setup", or right after the plugin was installed.
---
# Compounding setup
Goal: after this skill the four loops run on this machine (learning loop, follow-ups, memory review, run log). Do the steps in order. Verify each one before you move on; never report a step as done that you did not see succeed.
## 1. Run the setup script
```bash
bash "${CLAUDE_PLUGIN_ROOT}/scripts/setup.sh"
```
Read its output. Every `[todo]` line becomes a step below. It never overwrites existing files; it puts a `.template` copy next to them.
## 2. CLAUDE.md
Open `~/.claude/CLAUDE.md`. If it was just created from the template, fill the three marked sections with the user. Ask at most three questions with AskUserQuestion, one at a time:
1. Response style: how long and how technical should chat replies be?
2. Definition of done: what must be true before Claude says "done"? (Offer the template's list as the default.)
3. Autonomy: what may Claude do unasked, what always needs a question?
If a CLAUDE.md already existed, show the user the template sections that are missing from it (learning loop line, follow-up rule, memory rules) and propose them as additions. Never rewrite their text.
## 3. Memory folder
Find the memory folder Claude Code loads for the user's main project: `ls ~/.claude/projects/`. The one matching their work folder is `MEMORY_DIR`. If `MEMORY.md` there has no index yet, copy the structure from `~/.compounding/MEMORY.md.example` (headings only, no content).
## 4. Headless auth for jobs
Jobs run `claude -p` without a terminal. They need a long-lived token:
1. The user runs `claude setup-token` in their own terminal (OAuth login, cannot be done by Claude).
2. They store the result as one line `export CLAUDE_CODE_OAUTH_TOKEN=...` in `~/.config/compounding/claude-auth.env`, `chmod 600`. The `export` is required.
3. Record the expiry date (one year) as a follow-up: `followup.sh add "renew claude setup-token" <date>`.
The token never goes into a repo, a synced folder or a script.
## 5. Schedule
Show the crontab lines the setup script printed. The user picks which loops to run (recommend all four: memory review nightly, follow-ups daily, learning review weekly, plus their own jobs wrapped in run-logged.sh). They paste the lines into `crontab -e` themselves. On a Mac that sleeps, point them to `templates/launchd.example.plist` instead, or run the jobs on a small always-on server (see docs/jobs.md).
## 6. Verify
- `bash "${CLAUDE_PLUGIN_ROOT}/scripts/learning.sh" list` runs without error.
- Start a new session: the learning-loop line appears at session start.
- `MEMORY_DIR=... bash "${CLAUDE_PLUGIN_ROOT}/scripts/memory-review.sh"` runs once by hand (needs the token) and writes to the run log.
- `/compounding-status` shows the smoke-test run.
Report in five lines: what runs, what the user still has to do by hand (token, crontab), and the link to docs/playbook.md.
Versions
The database has no other skills named compounding-setup.
Database snapshot: 13.11.2026 · package version a8252b16ad83 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100setup
Adopt the Memory Kit in THIS repository — scaffold the memory layers, decide how the kit coexists with Claude Code's native auto memory, and install safe permission rails (`/memory-kit:setup rails` re-runs only the rails step on an adopted repo; `/memory-kit:setup adopt` after… - 100compounding-preflight
Scan a change-set against docs/compounding.md before review, PR creation, or release. Use when reviewing or creating a PR, when asked to "run the preflight" or "check against the gotchas", and as the publish-release runbook's compound step. Reports violations with the entry each… - 90kit-setup
Install, update or check the bdt-kit on this machine — merge the kernel into ~/.claude/CLAUDE.md with a diff, check that skills and agents are linked, and optionally enable the opt-in hooks. Use when the user asks to install, update, uninstall or check bdt-kit, or when kit skills seem missing. - 100setup
Adopt the Memory Kit in THIS repository — scaffold the memory layers, decide how the kit coexists with Claude Code's native auto memory, and install safe permission rails (`/memory-kit:setup rails` re-runs only the rails step on an adopted repo). Use when the user says… - 90compounding-operating-system
Analyze strategic decisions and opportunities for long-term compounding across wealth, knowledge, health, relationships, freedom, reputation, and impact. Use when the user asks for the Compounding Operating System or a strategic decision through a compounding lens. - 100memory-setup
Use when installing, repairing, or verifying the two-store agent-memory architecture on a machine — a code-graph store (codebase-memory-mcp) for structural truth plus an experience store (Hindsight) for decisions and outcomes. Triggers on "set up two-store memory", "install…