checkpoint
Save current progress to memory-keeper to prevent work loss.
What this skill does
# Checkpoint Skill Automatically checkpoint current progress to memory-keeper to prevent catastrophic work loss when context is exhausted. ## When to Use - Every 5-10 tool calls during implementation - After completing a significant piece of work - Before starting a large operation - When switching tasks - Before ending a session - When explicitly requested via `/checkpoint` ## Checkpoint Actions ### 1. Gather Current State Collect the following information: - Current task description from todo list - List of files modified this session - Implementation progress (percentage or phase) - Current blockers or issues - Next action to take ### 2. Save to Memory-Keeper ``` context_save(key: "current-task", value: "<task description>", category: "progress", priority: "high") context_save(key: "files-modified", value: "<comma-separated file list>", category: "progress") context_save(key: "implementation-progress", value: "<percentage or phase>", category: "progress") context_save(key: "next-action", value: "<exact next step>", category: "progress", priority: "high") ``` ### 3. Create Named Checkpoint ``` context_checkpoint( name: "checkpoint-<timestamp>", description: "Task: <task>, Progress: <progress>, Files: <count>, Next: <action>" ) ``` ### 4. Prepare for Compaction (if context is large) ``` context_prepare_compaction() ``` ## Checkpoint Frequency Guidelines | Activity | Checkpoint Frequency | |----------|---------------------| | File creation/modification | After every file | | Running tests | After each test run | | Research/exploration | Every 10 tool calls | | Debugging | After each hypothesis tested | | Multi-step implementation | After each step | ## Key Items to Always Save | Key | Description | Priority | |-----|-------------|----------| | `current-task` | What you're currently working on | high | | `files-modified` | All files touched this session | normal | | `implementation-progress` | How far along (%, phase) | normal | | `next-action` | Exact next step to take | high | | `blockers` | Current issues/blockers | high | | `todo-state` | Serialized todo list | normal | ## Checkpoint Output After checkpointing, confirm with: ``` Checkpoint saved: - Task: <current task> - Progress: <progress> - Files modified: <count> - Next action: <next step> ``` ## Recovery Reference If context is lost, use `/recover` to restore state from checkpoints.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.