Menu
Runtime assets (codex-companion.mjs, prompts, schema) backing the catalog's /codex:* commands. Not directly invocable.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | codex-companion-scripts |
| description | Runtime assets (codex-companion.mjs, prompts, schema) backing the catalog's /codex:* commands. Not directly invocable. |
| user-invocable | false |
| disable-model-invocation | true |
This skill is not meant to be invoked. It exists only to carry the codex-companion.mjs runtime, its lib/ helpers, prompt templates, and the review-output schema to a stable deployed path: ~/.claude/skills/codex-companion-scripts/.
The catalog's commands/status.md, setup.md, rescue.md, cancel.md, review.md, result.md, adversarial-review.md reference ${CLAUDE_PLUGIN_ROOT}/scripts/codex-companion.mjs. Since those commands are deployed as plain files (not as an installed Claude Code plugin), CLAUDE_PLUGIN_ROOT is never set by Claude Code itself for them. CLAUDE_PLUGIN_ROOT is instead defined as a global default in ~/.claude/settings.json env, pointing at this skill's deployed directory.
Source: vendored from openai/codex-plugin-cc/plugins/codex/{scripts,prompts,schemas} at the commit pinned when this skill was added. Re-sync manually from that upstream path if the companion script changes; there is no APM dependency tracking for this content because APM only resolves skills/ subpaths, not arbitrary plugin directories.
Route work in the `~/.apm` global APM workspace: decide what owns a change, which path is the source of truth, and which APM rollout / `mise` task to run. Use for skill update and redistribution requests (`skillアップデートして再配布して`, `再配布`), `apm.yml` / `apm.lock.yaml` and managed catalog rollout, manual-skills package state, orphaned APM packages, checked-out external dependency repositories, optional repository-scoped skill packages, and `apmのバージョンあげて` / pinned `apm` source checks. For skill body, description, script, reference, or asset design itself, coordinate with `skill-creator`; for general mise usage outside the APM workspace (including `mise upgrade TOOL` and `minimum_release_age`), use `mise`.
Use when deciding whether to install, enable, or troubleshoot Headroom context compression for local AI agent workflows, especially MCP, proxy, or agent-wrap usage.
Use when adding or reviewing CI-stability hooks and gates: Lefthook/pre-commit/pre-push configuration, aligning local push gates with GitHub Actions, deciding commit-vs-push gate scope, or migrating pre-commit to Lefthook. For mise task design itself, use `mise`; for debugging failing PR checks, use `gh-fix-ci`.
Curate external agent collections into this APM workspace. Use when evaluating whether an outside agent repository can be installed through APM, importing selected agents into catalog/agents, recording provenance, or refreshing curated agents from upstream.
Use when creating, rebuilding, or updating a Google Forms survey from a Markdown survey spec such as SURVEY_QUESTIONS.md, especially when the form should stay synchronized with question text, required flags, Google Forms item types, scale labels, and removed-question notes.
Slack app management knowledge for app settings, manifests, OAuth installs, scopes, bot users, Marketplace settings, App Home, display names, sender names, mrkdwn message formatting, and safe workspace-visible changes. Use when diagnosing or changing a Slack app, installed app, bot user, app label, DM header, chat sender, message text decoration, Slack links, block quotes, app approval/install state, token impact, Slack API app settings, Slack Marketplace settings, or stale Slack app name propagation.
