curare

Prune stale entries and replace the current-state note at wrap-ups.

Updated May 20, 2026
One-click install
npx skills add https://github.com/watmin/datamancy.dev --skill curare
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: curare
Source: https://github.com/watmin/datamancy.dev/tree/main/curare
Command: npx skills add https://github.com/watmin/datamancy.dev --skill curare

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Curare helps you tend the recovery record to ensure future self can recover from the work. It enforces a single current-state note, prunes stale entries, and maintains trust in the externalized memory across a gap.

Core Features & Use Cases

  • Maintains a single live current-state note, replacing it in place at wrap-ups.
  • Prunes outdated records to keep the recovery trail concise and trustworthy.
  • Keeps domain or substrate knowledge in its own documents outside the recovery record.

Quick Start

Run curare at the end of each wrap-up to refresh the current state and prune stale entries.

Frequently Asked Questions about curare

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I maintain a recovery record for workflow documentation?

To maintain a recovery record, enforce a single current-state note and prune stale entries at wrap-ups. This ensures future workflow documentation remains trustworthy and allows quick recovery across work gaps.

What is the best way to prune outdated notes during a debugging session?

The best way to prune outdated notes is to apply in-place replacement at debugging pauses. This removes stale entries from the recovery record, preserving orientation without embedding domain knowledge in the notes.

When do I need to refresh my current-state note for record-keeping?

You need to refresh your current-state note at wrap-ups, debugging sessions, or design pauses. Running this record-keeping process at these moments maintains a single live state and prunes outdated records.

Should I keep domain knowledge inside my recovery record?

No, you should not keep domain knowledge inside your recovery record. Domain or substrate knowledge must stay in its own separate documents outside the record to preserve orientation and keep the recovery trail concise.

How does in-place replacement work for workflow recovery notes?

In-place replacement works by overwriting the single existing current-state note during a wrap-up. This workflow recovery mechanism enforces a single source of truth and prunes outdated entries automatically.

Can I use this record-keeping approach for design pauses?

Yes, you can use this record-keeping approach for design pauses. Applying it at design pauses refreshes the current state and prunes stale entries, ensuring the recovery record stays trustworthy for future continuation.