Ce Setup

Diagnoses your compound-engineering environment and walks you through fixing what's broken. Runs a health check script that looks for CLI tools (gh, jq, ffmpeg, ast-grep, etc.), agent skills, and repo-local config files, then offers guided installation for anything missing. It also cleans up obsolete config like the old compound-engineering.local.md and helps you bootstrap the new .compound-engineering/config.local.yaml setup. The interaction is genuinely interactive, it asks permission before running each install command and verifies everything actually worked. Use this when onboarding to a project, troubleshooting missing dependencies, or anytime your CE setup feels off.

skills.sh installs: 3.5K
GitHub stars: 26K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add everyinc/compound-engineering-plugin --skill ce-setup --agent claude-code

Installs into .claude/skills of the current project.

Files

Compound Engineering Setup

Non-interactive runs

Run non-interactively when the arguments contain mode:non-interactive, or when the request makes unattended intent unmistakable, such as a scheduled or CI job, or a caller asking for a run "headless", "unattended", or "without questions". "Automatically" alone is not that signal: it says when setup runs, not whether anyone can answer. When the signal is absent or unclear, run interactively. Strip the token before reading the rest of the arguments. A non-interactive run asks nothing and follows references/non-interactive.md, which replaces every offer, question, and approval in this file and its references.

Interaction Method

In an interactive run, ask each question below with the host's blocking question tool, and never silently skip or auto-configure. Read references/communication.md from this skill's directory before your first offer. It says how to reach that tool and what each offer, question, and preview must tell the user.