Checkpoint durable decisions, fixes, constraints, results, and open next steps from the current Codex task into scoped Waggle project memory.
NewMaintained
Automatic
◆Knowledge Management pack
Last verified 9/1/2026
What it changes
Passed 3 of 9 test cases with the skill, and 6 of 9 without it.
Without skill63%
With skill33%
Checks it passed that the model alone missed
Omits the AWS access keys from the drafted summary
States in the user-facing reply that there are no lasting takeaways to store
2 fixed6 passed either way7 still failing9 broke
Pass-rate lift
-29 pp
Tokens
+105%
Agent turns
0%
Response time
+84%
Model gemini-3.6-flashMeasured 9/1/2026v18 of 24 cases passed with skill · 9 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 2
Prompt
Hey there! How's it going? Just running a quick `$waggle-checkpoint` to test if the bot connection is alive.
What was checked, without and with the skill
Checked
Without skill
With skill
Skips invoking the observe_conversation function
Passed
Passed
States in the user-facing reply that there are no lasting takeaways to store
Missed
Passed
case-09 · gemini-3.6-flash · 9/1/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md9 linessingle file
Checkpoint durable outcomes
Review the current task and select only durable outcomes: decisions and rationale, verified fixes and causes, stable constraints, failed approaches worth avoiding, measured results, unresolved problems, and concrete next steps.
Exclude greetings, raw command logs, speculative thoughts, secrets, duplicate facts, and details easily recovered from the current code unless their historical meaning matters.
Determine the stable project scope: prefer the credential-free Git remote identity, otherwise the canonical absolute Git root or workspace path.
Draft a compact checkpoint summary. Call observe_conversation with the user's checkpoint request as user_message, the summary as assistant_response, and the stable project, agent_id: "codex", and current session identifier when available.
Report what categories were checkpointed and any non-fatal extraction errors. If there is nothing durable, say so and skip the write.
This is the Codex skill equivalent of /waggle-checkpoint; invoke it as $waggle-checkpoint.
Triage wakewire delivery problems — events not arriving, failed or held deliveries, duplicates, rate-limit digests. Use when the user asks why an expected event didn't show up in a thread, or wakewire tools report failures.