What problem does it solve? Outdated or superseded knowledge cards clutter a personal knowledge base, but deleting them outright would break existing connections and lose historical context. This Skill retires cards safely by marking them archived while preserving their graph connections. ## Core Features & Use Cases - Dependency-aware archival: Checks whether other cards reference the target via connects_to, connections.json edges, or publish/ documents, and warns the user before proceeding. - Supersession tracking: Prompts for a replacement card and records it in the supersedes field so knowledge lineage stays intact. - CLI-enforced contracts: Delegates the actual file mutation to construct knowledge card archive, which updates lifecycle, preserves connections, and logs the archive_card event automatically. - Use Case: A user realizes their card on an old API version is outdated. They say "archive the legacy API card", review the warning about three connected cards, confirm, and the card is archived with all connections preserved as historical record. ## Quick Start Tell the agent to archive a specific knowledge card by name or ID, for example by saying "archive card legacy-auth-notes".
