memory-maintain

Runs a report-only maintenance pass over an Atmina Knowledge Base, proposing merges, repairs, archives, and link fixes.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/latentminds-ai/atmina-plugins --skill memory-maintain-latentminds-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: memory-maintain
Source: https://github.com/latentminds-ai/atmina-plugins/tree/main/plugins/atmina-codex/.agents/skills/memory-maintain
Command: npx skills add https://github.com/latentminds-ai/atmina-plugins --skill memory-maintain-latentminds-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Organizational memory stored in an Atmina Knowledge Base drifts over time: duplicate pages accumulate, evidence pins go stale, contradictions appear, and durable pages are never recalled. This Skill performs an out-of-band, report-only maintenance pass that audits the Knowledge Base and proposes corrections without silently rewriting live claims. ## Core Features & Use Cases - Claim-repair sweep: Walks every durable page under wiki/, re-resolves evidence locators and pins, and proposes re-pointing drifted spans only on exact byte matches. - Dedupe, contradiction, and archive handling: Proposes same-intent merges (confirmed always wins over inferred), flags contradictions, and moves obsolete pages to a KB-root archive/ only when not cited as in-KB evidence. - Health reporting: Reports durable pages never recalled, broken references, and unconnected pages, with every count stating the scope it covered. - Use Case: An operator asks to run an attestation sweep on a Knowledge Base; the agent walks the catalog, flags three drifted evidence pins, archives two obsolete pages, proposes five linkify conversions, and writes a trail report in chronicle/. ## Quick Start Ask the agent to run an out-of-band maintain pass on your Atmina Knowledge Base, for example by saying: run memory maintenance on this Knowledge Base and report what needs repair.

Frequently Asked Questions about memory-maintain

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

FAQPage Schema
How do I run a maintenance pass on an Atmina Knowledge Base?▼

Ask the agent explicitly to maintain the Knowledge Base out of band, for example by requesting an attestation sweep or claim repair. The skill refuses to run during an in-band user task and never runs as another task's finally step.

How does claim repair work for drifted evidence pins?▼

The pass re-reads the pinned version via file_history, compares the pinned span bytes against the current head, and proposes re-pointing the span link only when exactly one byte-identical match exists at a new offset. Zero or multiple matches are flagged for a human, never auto-fixed.

Can the maintain pass delete or rewrite pages in the Knowledge Base?▼

No. It is report-only: it never silently rewords claims, never writes _staged/, and never calls the REST applyReviewedRepairs endpoint. The only writes are archiving obsolete pages via move_file and a short trail report in chronicle/.

When are obsolete pages archived instead of deleted?▼

Obsolete durable pages are moved to a KB-root archive/ directory with move_file, preserving bytes and file_id. Pages still cited as in-KB evidence by other wiki pages are skipped and flagged, and stale_after dates alone never trigger a move.

Why does the health report say a count was not checked?▼

Link health covers content-origin references only and cannot see mirrored content, so every count must state its scope. If the link_health block is absent from get_context, the pass reports not checked rather than claiming zero broken references.