OpenParable
Skip to content
← Back to skills

Vault Maintenance

Productivity
vault-maintenance

Vault Maintenance is an Agent Skill for productivity published in the yogsoth-ai/de-anthropocentric-research-engine repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Tactic for vault health upkeep — lint, orphan resolution, merge candidates, confidence updates. Minimum yield ≥1 issue resolved per invocation.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/yogsoth-ai/de-anthropocentric-research-engine/blob/HEAD/skills/vault-maintenance/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/vault-maintenance, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Vault Maintenance

Vault health upkeep. Called when CC judges the vault has accumulated enough entropy to warrant cleanup, or periodically between research phases.

Available SOPs

  • wiki-lint-fix — run lint checks, identify issues, optionally auto-fix
  • wiki-search — find near-duplicate candidates for merging
  • wiki-graph-query — explore orphan neighborhoods for reconnection
  • wiki-add-edge — reconnect orphans to the graph

Guiding Principles

  • Lint first. Start with vault_lint in report mode to assess current health.
  • Triage by severity. Errors (broken links, missing frontmatter) before warnings (orphans, stale entries).
  • Conservative auto-fix. Only auto-fix safe operations (duplicate edge removal, stale index pruning). Manual intervention for ambiguous cases.
  • Merge, don't delete. Near-duplicate pages should be merged (consolidate content, redirect edges) rather than deleted.
  • Confidence decay. Pages with evidence older than the research horizon may need confidence score updates.

Minimum Yield

Execution Guidance

CC has full autonomy over:

  • Which issues to address and in what order
  • Whether to auto-fix or manually resolve
  • How aggressively to merge near-duplicates
  • When to update confidence scores

Typical flow (reference, not prescription):

  1. Run vault_lint (report mode) — assess issue landscape
  2. Categorize: auto-fixable vs manual
  3. Auto-fix safe issues (duplicate edges, stale index)
  4. For orphans: search for connection candidates, add edges
  5. For near-duplicates: merge content into canonical page, update edges
  6. Re-run vault_lint to confirm resolution

Available SOPs

Optional, no fixed order; the final leaf is always a sop.

SOPWhen to use
wiki-add-edgeSOP wrapping vault_add_edge — create a typed relationship between two vault pages.
wiki-edge-auditSOP for auditing wikilink coverage — scans all edges and reports which source pages are missing [[dir/slug]] wikilinks to their targets.
wiki-graph-querySOP wrapping vault_query_graph — traverse knowledge graph from a node to explore its neighborhood and context.
wiki-lint-fixSOP wrapping vault_lint — run batch validation, report issues, optionally auto-fix safe problems.
wiki-searchSOP wrapping vault_search — BM25 full-text search across vault pages. Returns ranked results with snippets.