ce-setup

Diagnoses CE environment and bootstraps missing components via guided workflow.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/yxc023/agent-config-studio --skill ce-setup-yxc023
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-setup
Source: https://github.com/yxc023/agent-config-studio/tree/main/.opencode/skills/ce-setup
Command: npx skills add https://github.com/yxc023/agent-config-studio --skill ce-setup-yxc023

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires agent-browser, gh, jq, vhs, silicon, ffmpeg, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Compound Engineering Setup diagnoses the health of your local CE environment, checks CLI dependencies, the plugin version, and repo-local config, then offers guided installation for missing tools to streamline onboarding and troubleshooting.

Core Features & Use Cases

  • Interactive environment health checks that detect missing tools and misconfigurations.
  • Automatic discovery and validation of repo-local CE settings, and guidance to bootstrap configuration templates.
  • Project onboarding and maintenance workflows: ensure tools and config templates are present for consistent CE behavior across workspaces.

Quick Start

Run ce-setup to diagnose your environment and bootstrap repository-local CE configuration.

Frequently Asked Questions about ce-setup

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

FAQPage Schema
How do I diagnose missing dependencies and bootstrap a local development environment setup?

To diagnose a local development environment setup, you can run an interactive health check that evaluates missing dependencies, plugin versions, and repo-local config to generate a guided remediation plan.

What is a Compound Engineering setup and when do I need to configure it?

A Compound Engineering setup is a local project configuration requiring specific CLI tools, plugin versions, and repo-local config templates to ensure consistent environment health and workflow automation across workspaces.

How do I troubleshoot environment health issues and missing CLI tools during project onboarding?

Troubleshooting environment health issues involves running an automated check that detects missing CLI tools, validates repo-local config templates, enforces safe gitignore rules, and yields a guided installation plan.

Do I need specific CLI dependencies installed before diagnosing my environment configuration?

You do not need all dependencies pre-installed to diagnose your environment configuration; the tool checks for presence of required CLI dependencies and offers guided installation steps for any missing components.

What's the best way to ensure tools and config templates are present for consistent project onboarding?

The best way to ensure tools and config templates are present for project onboarding is to run an environment health check that validates CLI tool presence, discovers repo-local settings, and bootstraps missing configuration templates.

Why does my environment health check fail when repo-local config is missing or misconfigured?

An environment health check fails on missing repo-local config because the setup requires validated config templates and safe gitignore enforcement to guarantee consistent CE workflow behavior and proper tool integration.