Yifan Yang
f9db99853b
Restructure into plugins/{claude-code,codex,copilot}/ — one engine, three thin
shells, all calling the shared plugins/run-sleep.sh -> python -m skillopt_sleep.
- claude-code/: existing plugin moved here; runner delegates to the shared
launcher (fixes repo-root resolution after the move).
- codex/: ~/.codex/prompts/sleep.md custom prompt + ~/.agents/skills SKILL.md +
install.sh + AGENTS.md hint — Codex's documented, stable extension surfaces.
- copilot/: a stdlib-only MCP server (mcp_server.py) exposing sleep_* tools,
plus mcp-config.example.json and a copilot-instructions snippet. Verified end
to end (initialize -> tools/list -> tools/call returns real engine output).
- plugins/README.md overview table; main README News + a dedicated SkillOpt-Sleep
section; pyproject lists skillopt_sleep as a first-class package.
Decoupling emphasized throughout: open-source tool (skillopt_sleep/) with zero
dependency on the research package. 29 tests pass; all three shells resolve.
Co-Authored-By: Claude Opus 4 <noreply@anthropic.com>
22 lines
916 B
Markdown
22 lines
916 B
Markdown
# /sleep — SkillOpt-Sleep for Codex
|
|
#
|
|
# Custom prompt: copy this file to ~/.codex/prompts/sleep.md and invoke with
|
|
# `/sleep` in the Codex CLI. ($ARGUMENTS is the text after /sleep.)
|
|
|
|
Run the SkillOpt-Sleep offline self-evolution cycle. Action: $ARGUMENTS
|
|
(empty → "status").
|
|
|
|
Use the bundled runner via shell:
|
|
|
|
bash "${SKILLOPT_SLEEP_REPO:?set SKILLOPT_SLEEP_REPO to the repo root}/plugins/run-sleep.sh" $ARGUMENTS --project "$(pwd)"
|
|
|
|
Then:
|
|
- For `run`/`dry-run`: read the staged `report.md` and show the held-out
|
|
baseline → candidate score and the proposed edits. `run` only stages a
|
|
proposal; nothing live changes until `adopt`.
|
|
- For `adopt`: confirm which files were updated and that a backup was written.
|
|
- Never edit the user's AGENTS.md / skills yourself; only `adopt` does that.
|
|
|
|
Default backend is `mock` (no API spend). Add `--backend codex` for real
|
|
improvement on the user's Codex budget.
|