ce-setup

Diagnose and configure compound-engineering CLI tools, agent skills, and repo-local config.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/Norfolk-Group/marcela-norfolk-ai --skill ce-setup-norfolk-group
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-setup
Source: https://github.com/Norfolk-Group/marcela-norfolk-ai/tree/main/skills/compound-engineering/skills/ce-setup
Command: npx skills add https://github.com/Norfolk-Group/marcela-norfolk-ai --skill ce-setup-norfolk-group

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Setting up the compound-engineering environment requires verifying many CLI tools, agent skills, and repo-local config files by hand, which is error-prone and tedious. This Skill automates the diagnosis and guides you through fixing every gap interactively. ## Core Features & Use Cases - One-pass health check: Runs a bundled script that reports the status of CLI tools (agent-browser, gh, jq, vhs, silicon, ffmpeg, ast-grep), agent skills, and repo-local config in a single formatted report. - Guided installation: Presents missing tools and skills as a pre-selected multi-select list, shows each install command, asks for approval, and verifies the installation afterward. - Repo config bootstrapping: Cleans up obsolete compound-engineering.local.md files, creates .compound-engineering/config.local.yaml from a template, and ensures it is safely gitignored. - Use Case: After cloning a project that uses compound-engineering, run this Skill to confirm every dependency is installed, refresh the example config, and install anything missing before starting work. ## Quick Start Ask the assistant to run the compound-engineering setup check and fix any missing tools or config in this repository.

Frequently Asked Questions about ce-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check my compound-engineering environment setup?

Run the ce-setup skill, which executes a bundled health-check script that reports the status of all CLI tools, agent skills, and repo-local config in one pass. It flags missing items in yellow and summarizes the total issues found.

How do I install missing CLI tools like gh, jq, or ast-grep?

The skill presents missing tools as a pre-selected multi-select list with install commands from the diagnostic output. After you approve each command, it runs the installation and verifies success with a command-existence check.

Does ce-setup work outside of Claude Code?

Yes, it supports Claude Code, Codex, Gemini, and Pi by using each platform's blocking question tool such as AskUserQuestion or request_user_input. It detects Claude Code via the plugin root variable and only mentions /ce-update when that platform is active.

What is the .compound-engineering/config.local.yaml file used for?

It stores machine-local compound-engineering preferences such as work delegation and product pulse settings. The skill creates it from a template on approval, refreshes the committed example file, and offers to add a .gitignore entry so local settings are never committed.

Why does ce-setup flag compound-engineering.local.md as an issue?

That file is obsolete because review-agent selection is now automatic and machine-local state moved to .compound-engineering/config.local.yaml. The skill explains this and asks whether to delete the legacy file from the repository root.