Install the skill by copying its directory into the appropriate location inside your repository or home directory. The skill directory itself is never modified by the workflow — all task artifacts are written into the target repository.
Project skill locations
Install as a project skill at:.agents/skills/repo-task-proof-loop/
SKILL_PATH when running the bundled scripts:SKILL_PATH=.agents/skills/repo-task-proof-loop
Install as a project skill at:.claude/skills/repo-task-proof-loop/
SKILL_PATH when running the bundled scripts:SKILL_PATH=.claude/skills/repo-task-proof-loop
Personal skill locations
You can also install the skill once in your home directory and use it across multiple repositories.
$HOME/.agents/skills/repo-task-proof-loop/
~/.claude/skills/repo-task-proof-loop/
.agents/skills/repo-task-proof-loop/ ← Codex project skill
.claude/skills/repo-task-proof-loop/ ← Claude Code project skill
init, it writes repo-local workflow files into the target repository — not into the skill directory — so both installations can safely share the same task artifacts under .agent/tasks/.
The SKILL_PATH variable
All bundled scripts use a path relative to the skill root. Before running any script, set SKILL_PATH to the installed skill directory:
SKILL_PATH=.agents/skills/repo-task-proof-loop
python3 "$SKILL_PATH/scripts/task_loop.py" init --task-id my-task
Smoke test
After installing the skill, run the bundled smoke test to verify the skill structure and confirm the initialization scripts work correctly:
python3 "$SKILL_PATH/scripts/verify_package.py"
After install: Claude Code session note
In Claude Code, if init creates or refreshes .claude/agents/* during a running session, start a new Claude Code session before expecting those updated agents to appear. Use /agents to inspect the available Claude agents after the new session starts.
init run that refreshes the agent files.