Ce Setup
Copy and tune Compound Engineering local YAML so Codex delegation and product-pulse analytics match how your indie product is measured.
Overview
Ce-setup is an agent skill for the Build phase that documents optional Compound Engineering config.local.yaml settings for Codex delegation and product-pulse metrics.
Install
npx skills add https://github.com/everyinc/compound-engineering-plugin --skill ce-setupWhat is this skill?
- Template for .compound-engineering/config.local.yaml with commented optional keys
- Work delegation block: work_delegate (codex|false), consent, sandbox (yolo|full-auto), model and effort overrides
- Product pulse settings: pulse_product_name, lookback (1h|24h|7d|30d), primary/value/completion events
- Optional pulse_quality_scoring and dimension for AI-product quality signals
- Documents defaults and invalid-value fallback behavior for Compound Engineering CLI
- Documents pulse_lookback_default options: 1h, 24h, 7d, 30d
- pulse_completion_events supports comma-separated list of 0–3 events
Adoption & trust: 1.6k installs on skills.sh; 20.5k GitHub stars; 1/3 security scanners passed (skills.sh audits).
What problem does it solve?
You enabled Compound Engineering but do not know which YAML keys control Codex delegation, sandbox mode, or pulse event names for your product.
Who is it for?
Solo builders already using the Compound Engineering plugin who want declarative control over Codex delegation and pulse dashboards.
Skip if: Projects not using Compound Engineering, or teams that need runtime setup without editing repo-local YAML.
When should I use this skill?
First-time Compound Engineering install or when re-tuning Codex delegation, sandbox mode, or product-pulse event names in config.local.yaml.
What do I get? / Deliverables
You have a commented local config template with your delegation and pulse events defined so Compound Engineering behaviors match your repo and analytics schema.
- .compound-engineering/config.local.yaml tailored to delegation and pulse settings
Recommended Skills
Journey fit
Build/agent-tooling is where you configure agent plugins, delegation, and observability hooks in the repo. Agent-tooling covers .compound-engineering/config.local.yaml and optional Codex work-delegate settings.
How it compares
Local plugin config reference—not an MCP server and not a substitute for /ce-product-pulse interactive setup when you want a guided interview.
Common Questions / FAQ
Who is ce-setup for?
Indie developers and small teams running the Compound Engineering plugin who prefer checking in or copying a documented config.local.yaml beside their codebase.
When should I use ce-setup?
Use it during Build agent-tooling setup when first enabling work_delegate to Codex, choosing sandbox strictness, or mapping pulse_primary_event and pulse_value_event to your analytics.
Is ce-setup safe to install?
Delegation and sandbox settings can allow automated Codex work—review the Security Audits panel on this Prism page, keep work_delegate_consent accurate, and avoid yolo sandbox on sensitive repos until you understand the blast radius.
SKILL.md
READMESKILL.md - Ce Setup
# Compound Engineering -- local config # Copy to .compound-engineering/config.local.yaml in your project root. # All settings are optional. Invalid values fall through to defaults. # --- Work delegation (Codex) --- # work_delegate: codex # codex | false (default: false) # work_delegate_consent: true # true | false (default: false) # work_delegate_sandbox: yolo # yolo | full-auto (default: yolo) # work_delegate_decision: auto # auto | ask (default: auto) # work_delegate_model: gpt-5.4 # any valid codex model (omit to use ~/.codex/config.toml default) # work_delegate_effort: high # minimal | low | medium | high | xhigh (omit to use ~/.codex/config.toml default) # --- Product pulse --- # Settings written by /ce-product-pulse first-run interview. Re-run the skill with # argument `setup` or `reconfigure` to edit interactively. # pulse_product_name: "Spiral" # used in report titles (no default) # pulse_lookback_default: 24h # 1h | 24h | 7d | 30d (default: 24h) # pulse_primary_event: "session_started" # the event that means "user showed up" # pulse_value_event: "task_completed" # the event that means "user got value" # pulse_completion_events: "onboarded,first_purchase" # comma-separated, 0-3 events # pulse_quality_scoring: false # true | false (default: false; AI products only) # pulse_quality_dimension: "answer accuracy" # dimension scored 1-5 when pulse_quality_scoring is true # pulse_analytics_source: posthog # posthog | mixpanel | custom (no default) # pulse_tracing_source: sentry # sentry | datadog | custom (no default) # pulse_payments_source: stripe # stripe | custom (no default) # pulse_db_enabled: false # true | false (default: false; read-only DB if true) # pulse_metric_sources: "retention_d7=posthog,nps=delighted" # strategy-metric -> source overrides; comma-separated 'metric=source' pairs; unlisted metrics fall back to pulse_analytics_source # pulse_pending_metrics: "retention_d7,nps" # comma-separated strategy metrics awaiting instrumentation; render as 'no data' # pulse_excluded_metrics: "north_star" # comma-separated strategy metrics intentionally not in pulse # --- Output format --- # Per-skill output format default. Selects the exclusive format the artifact # is written in: `md` produces a markdown file, `html` produces a single # self-contained HTML file. The two are mutually exclusive -- there is no # sibling artifact. See DESIGN.md or your agent instructions to influence # HTML styling. CLI arguments override these defaults; pipeline contexts # (e.g., LFG, disable-model-invocation) always force `md` regardless. # plan_output: html # md | html (default: md) # brainstorm_output: html # md | html (default: md) # --- ce-promote --- # Written automatically when you decline the Spiral setup offer in /ce-promote. # Suppresses that one-time setup nudge in this project. Remove the key to re-enable. # ce_promote_spiral_optout: true # true | (absent) (default: absent -- offer once) #!/usr/bin/env bash # Compound Engineering environment health check # Outputs a formatted diagnostic report in one pass set -o pipefail # ===================================================== # Dependency config # ===================================================== # Format: name|tier|install_cmd|url # Tiers: recommended (flagged if missing), optional (noted if missing) # To add a dependency: add a line here. No other changes needed. deps=( "agent-browser|recommended|CI=true npm install -g agent-browser --no-audit --no-fund --loglevel=error && agent-browser install && npx skills add https://github.com/vercel-labs/agent-browser --skill agent-browser -g -y|https://github.com/vercel-labs/agent-browser" "gh|recommended|NONINTERACTIVE=1 H