Menu

Individual skill

waggle-checkpoint

Checkpoint durable decisions, fixes, constraints, results, and open next steps from the current Codex task into scoped Waggle project memory.

plugins/Abhigyan-Shekhar/Waggle-mcp/skills/waggle-checkpoint/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,537
Repository last updated
Nov 7, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Checkpoint durable outcomes

1. 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.
2. Exclude greetings, raw command logs, speculative thoughts, secrets, duplicate facts, and details easily recovered from the current code unless their historical meaning matters.
3. Determine the stable project scope: prefer the credential-free Git remote identity, otherwise the canonical absolute Git root or workspace path.
4. 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.
5. 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`.