setup-multi-agent

/setup-multi-agent — Bootstrap a new project

Drop the AGENTS.md + CLAUDE.md pair into a target project so all three coding CLIs (Claude Code, Codex CLI, Antigravity CLI) load the same canonical project context. AGENTS.md is the canonical source; CLAUDE.md is a 1-line @AGENTS.md import so Claude Code (which doesn't yet natively read AGENTS.md) gets the same content.

Prerequisites

The cc-templates repo must be available locally. The skill reads three files from its templates/ directory:

• templates/AGENTS.md.template
• templates/CLAUDE.md.template
• templates/gitignore-additions.txt

Step 0 below locates that directory. If any of the three files is missing after resolution, fail loudly and stop.

Steps

0. Locate the templates directory

This skill is usually invoked from a symlinked install at the skill directory (via symlink chain) that points back into the cct repo, so templates/ is NOT a sibling of SKILL.md. Resolve the real cct repo root by following the skill's own symlink and walking up three levels.

The harness reports the skill's base directory at invocation. Pass that path through readlink -f and ascend three directories — the skill lives at <cct-repo>/.agents/skills/setup-multi-agent/, so up-three lands at <cct-repo>:

# Replace <skill-base-dir> with the path the harness reported at invocation.
SKILL_DIR_RESOLVED="$(readlink -f "<skill-base-dir>")"
CCT_ROOT="$(readlink -f "${SKILL_DIR_RESOLVED}/../../..")"
TEMPLATES_DIR="${CCT_ROOT}/templates"

# Verify the three template files exist; fail loudly if any are missing.
missing=0
for f in AGENTS.md.template CLAUDE.md.template gitignore-additions.txt; do
  if [ ! -r "${TEMPLATES_DIR}/${f}" ]; then
    echo "ERROR: Missing template at ${TEMPLATES_DIR}/${f}" >&2
    missing=1
  fi
done
[ "${missing}" -eq 0 ] || exit 1

echo "Templates dir resolved: ${TEMPLATES_DIR}"

Use the resolved ${TEMPLATES_DIR} (or the absolute path the snippet prints) in all subsequent steps. This works whether the skill is invoked from a symlinked install or directly from inside the cct repo; the readlink -f step is what lets symlinked installs resolve to the real cct repo root instead of the symlink path.