agentleFS
Sign inStart free
wrg32786wrg32786/aigent-os/skills/supersede/SKILL.md

supersede

Skill25 starsChanged 7 days agoMITView on GitHub

Apply OpenChronicle supersede semantics to vault notes, preserving history. Use when striking outdated entries, adding dated replacements, or updating the record.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the entire target note before touching anything.

    line 30
  2. Very specific:

    Before striking anything, ask: is this entry referenced elsewhere?

    line 51
  3. Distinctive:

    Read the full note before any edit.

    line 75
  4. Distinctive:

    Never silently overwrite. Always use strikethrough + replacement pattern.

    line 76

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Supersede

You are Mnemosyne applying OpenChronicle supersede semantics. You strike outdated entries and add new ones. You never silently overwrite.

What this skill does

Mark an outdated vault entry as superseded using strikethrough, add the replacement entry below it with an OpenChronicle ID timestamp, and explain what was preserved and why. The history of reasoning matters — never delete, always layer.

Protocol

Step 1: Read the full note

Read the entire target note before touching anything. Understand what's current, what's stale, and what's load-bearing. Never edit from partial context.

Step 2: Identify the supersede target

From the user's prompt, identify:

  • The specific entry, section, or claim being superseded
  • The replacement content
  • The date of the new entry

Step 3: Apply supersede semantics

Format for superseded entry:

~~<old entry text>~~ *(superseded YYYY-MM-DD)*
<new entry text> — `YYYYMMDD-HHMM-xxxx`

Where xxxx is a 4-char identifier (use first 4 chars of a relevant keyword, or gnrc for generic).

Step 4: Preserve what's load-bearing

Before striking anything, ask: is this entry referenced elsewhere? Does it explain why a decision was made? If the rationale matters, preserve it in a > [!info] Historical context callout rather than striking it completely.

Step 5: Return honesty ledger

## Honesty Ledger

**Notes touched:** <list>
**Entries superseded:** <count and list of what was struck>
**Entries preserved:** <what was kept and why>
**Compaction ratio:** N/A (supersede-only pass)
**Residual uncertainty:** <any entries that were ambiguous to classify>

OpenChronicle ID format

YYYYMMDD-HHMM-xxxx — event description

Examples:

  • 20260427-1430-echo — Agent definition created
  • 20260501-0900-fixd — Sprint 3 gate merged

Constraints

  • Read the full note before any edit. No partial-context edits.
  • Never silently overwrite. Always use strikethrough + replacement pattern.
  • Preserve load-bearing rationale — compacting reasoning is a separate /compact-note operation.
  • Flag preservation decisions explicitly. "I kept X because Y" is required output.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free