knowledge-maintainlisted

This skill should be used when the user asks to fix, repair, or tidy one or more SPECIFIC named notes — 'fix these notes', 'fix the issues in [note]', 'add the missing relations to [note]', 'tidy up [note]', 'fix orphan [note]', 'apply the gardener findings for [note]'. Applies structural fixes (missing sections, relation-verb drift, frontmatter case) directly and inline, and confirms content-level changes (prose rewrites, merges, archival) with the user before applying them. NOT for read-only auditing (use /knowledge-garden), NOT for creating new notes (use /intel), and NOT for graph-wide or autonomous remediation ('fix the whole audit', 'remediate the graph', research-and-document sweeps) — those belong to the knowledge-maintainer agent, which this skill delegates to when invoked broadly.
voxpelli/vp-claude · ★ 3 · AI & Automation · score 73

Install: claude install-skill voxpelli/vp-claude

# Knowledge Maintain Apply targeted fixes to Basic Memory notes — missing sections, relations, structural tidies, archival — with the user confirming changes inline. This is the scoped, interactive sibling of the `knowledge-maintainer` agent: it owns the common case (repair a few named notes, where being in the main session means the user sees each edit) and delegates heavy, autonomous remediation to the agent. **Write discipline (non-negotiable):** - `edit_note` with `find_replace` ONLY. Never `append` with `section=` — it appends to end-of-**file**, not end-of-section, the documented BM footgun. - `write_note` and `delete_note` are intentionally excluded. Create new notes via `/intel`; archive via `move_note` to `archive/`. - Read the live note before every edit (verify-before-fix). A flagged issue may be a parse artifact, or the note may already be correct. - One `edit_note` per note per message — issue same-note edits sequentially and re-read before re-anchoring after any lands (concurrent same-note edits are a precautionary hazard; see `intel`'s `note-write-mechanics.md` single-writer rule). - `schema_validate` after every edit. If its output appears to repeat the same value, trust the note body (`read_note` JSON) as the source of truth rather than inferring a duplication from the validator response alone. ## 1. Decide venue (scoped inline vs delegate) Classify the request first: **Delegate to the agent** when the work is heavy or autonomous — any of: