← ClaudeAtlas

ki-housekeeping-codexlisted

Governs repository-scoped Codex session acquisition and later housekeeping. Use for "acquire Codex sessions", "import Codex sessions", "audit Codex sessions", "clean up Codex sessions", or "delete old Codex threads". It guides discover, list, faithful read, checkpoint, staging, harvest, and safe later cleanup for one exact physical repository; it performs no automatic retention and never substitutes for portable repository maintenance owned by ki-work-housekeeping.
knowledgeislands/ki-agentic-harness · ★ 0 · AI & Automation · score 76
Install: claude install-skill knowledgeislands/ki-agentic-harness
# Codex session acquisition and housekeeping Govern saved Codex-session acquisition and later cleanup through a review-before-delete workflow. Read the [Codex state standard](references/standards-codex-state.md) for the identity, artifact, and deletion contract. The skill is opt-in while its machine-readable binding uses the experimental Codex app-server. It reads a complete provider payload only for an explicit acquisition operation, never applies automatic retention, and never infers repository ownership from a parent path or symlink alias. The `ki-work-housekeeping` skill continues to own recurring repository-maintenance work. ## AI session acquisition Use the provider-neutral lifecycle: **acquire → stage → harvest → durable knowledge → archive/delete source**. For one exact physical repository, `mcp-housekeeping-codex` exposes read-only `codex_sessions_discover`, `codex_sessions_list`, `codex_session_read`, and `codex_sessions_checkpoint` operations. `list` and `checkpoint` are content-minimised provenance; `read` is the faithful source payload. The MCP does not write Knowledge Islands state. `ki space acquire codex import` will own inbound staging and incremental checkpoint persistence. Do not archive or delete a Codex session until acquisition, review, and harvesting have passed their later safety checkpoint. ## Operating modes With no clear mode, explain the skill and its modes first; in an interactive session, then ask which mode and target to use. `help`, `-h`