Agent skill
codex-symphony
Install and operate a portable OpenAI Symphony + Linear orchestration setup in any Git repository. Use when the user wants a one-command local Symphony runner, a reusable WORKFLOW template, background launch scripts, or a Codex wrapper that restarts Symphony automatically when reopening the CLI.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/codex-symphony
SKILL.md
Codex Symphony
Use this skill when the user wants to install or operate a local OpenAI Symphony setup for a repository.
When to Use
Use this skill when the user asks to:
- install Symphony into a repo
- restart Symphony after reopening Codex
- add a reusable
codex-symphonycommand - bootstrap Linear-driven agent orchestration
- create a portable Symphony package for another machine or repo
- diagnose why Symphony is not starting
- initialize repo-local Symphony env files safely
Core Rule
Do not assume a fixed repository path.
Always resolve the target repo by:
- explicit argument, if the user gave one
git rev-parse --show-toplevel, if running inside a repo- otherwise ask for the repo path
Install
Run the bundled installer:
bash scripts/install.sh [optional-repo-path]
The installer will:
- copy
WORKFLOW.symphony.md - copy
scripts/symphony/* - copy
.env.symphony.example - enable
./scripts/symphony/init.shfor.env.symphony.local - enable
./scripts/symphony/doctor.shfor readiness checks - append
.symphony/to.gitignoreif missing - install
~/.local/bin/codex-symphony - link this skill into
~/.codex/skills/codex-symphony
Operate
After install, the normal commands are:
./scripts/symphony/init.sh
./scripts/symphony/doctor.sh
codex-symphony
./scripts/symphony/logs.sh
./scripts/symphony/restart.sh
./scripts/symphony/start-background.sh
./scripts/symphony/status.sh
./scripts/symphony/stop.sh
Required Env
The target repo must provide:
LINEAR_API_KEYLINEAR_PROJECT_SLUGSOURCE_REPO_URLSYMPHONY_WORKSPACE_ROOT
Optional:
GH_TOKENSYMPHONY_PORT
Expected Help Pattern
When helping the user:
- run the installer if the repo is not bootstrapped yet
- prefer
./scripts/symphony/init.shover manual env editing - run
./scripts/symphony/doctor.shbefore starting if setup looks incomplete - tell the user which env vars or tools are still missing
- start Symphony only after the repo is configured
- report dashboard URL and log path only
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?