Menu
Use ControlKeel proof bundles, typed memory, workspace snapshots, transcript summaries, and resume packets before closing or resuming work. Activate this when you need durable evidence or historical context.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Run objective, repeatable improvement work under an immutable verifier and hard iteration, cost, time, and no-progress limits. Use for approved experiments with an automated metric and sandboxed worker.
Write concise, calm technical responses whose structure matches the decision, evidence, or sequence being communicated. Use when drafting substantial plans, reviews, findings, documentation, or completion summaries.
Operate inside a ControlKeel-governed session. Use this before code edits, shell execution, delegation, deploy work, or any task that needs CK validation, findings, budget, proof, or routing context.
Keep a governed session within budget. Use this before long-running agent work, bulk processing, or any task where spend pressure could change the plan.
Close a governed work session with validation, proof, findings, budget, digest, learning, and handoff checks. Use when the user asks to wrap up, stop for the day, or leave work ready for another agent.
Audit tests that may pass without proving the claimed behavior. Use for periodic test-quality reviews or when coverage looks healthy but regressions still escape.
| name | proof-memory |
| description | Use ControlKeel proof bundles, typed memory, workspace snapshots, transcript summaries, and resume packets before closing or resuming work. Activate this when you need durable evidence or historical context. |
| when_to_use | Activate before closing a session, resuming previous work, or when the user says 'remember this', 'save proof', 'snapshot state', or references prior decisions. |
| argument-hint | [checkpoint label or context to preserve] |
| license | Apache-2.0 |
| compatibility | ["codex","claude-standalone","claude-plugin","copilot-plugin","github-repo","open-standard","cline-native","cursor-native","windsurf-native","continue-native","letta-code-native","pi-native","roo-native","goose-native","opencode-native","gemini-cli-native","kiro-native","kilo-native","amp-native","augment-native","hermes-native","multica-native","openclaw-native","devin-terminal-native","warp-native","droid-bundle","forge-acp"] |
| metadata | {"author":"controlkeel","version":"2.0","category":"proof","ck_mcp_tools":["ck_observability","ck_context","ck_memory_search","ck_memory_record","ck_memory_archive","ck_regression_result"]} |
Use this skill when you need the durable system-of-record view instead of only the live session state.
ck_context.proof_summary, memory_hits, workspace_context, context_reacquisition, instruction_hierarchy, recent_events, and resume_packet.ck_memory_search when prior decisions, checkpoints, or findings need explicit retrieval instead of relying only on passive memory hits.ck_memory_record to preserve new decisions or operator intent that future agents should recover explicitly.ck_memory_archive to retire stale or superseded memories so retrieval quality does not decay.When closing or resuming work, include local observability loop evidence when relevant: saved evals, benchmark drafts, materialized scenarios, generated benchmark history, and advisory promotion candidates. Prefer the read-only ck_observability MCP surface for summaries and record durable checkpoints with ck_memory_record; do not treat advisory promotion candidates as executed changes.