openinterpreter Wiki Lint
Use this skill for maintenance and health checks.
Start with the vault tool
Run interpreter_vault with action="lint" first. That report is the structural source of truth for:
- orphan notes
- isolated notes
- dangling links
- repeated missing-page candidates
- tag coverage summary
You may also use:
interpreter_vaultwithaction="search_notes"for follow-up explorationinterpreter_vaultwithaction="note_context"for notes that need closer inspectioninterpreter_vaultwithaction="notes_with_tag"when a tag cluster looks under-maintained
Lint workflow
- Run the structural vault lint.
- Prioritize the biggest maintenance issues first.
- If the user asked for semantic review, inspect the most relevant pages for contradictions or stale synthesis.
- Return a prioritized list of findings and next actions.
- Do not auto-fix unless the user asked for fixes.
Hard rules
- Treat the vault lint output as the graph baseline.
- Be explicit about what is structural fact versus semantic judgment.
- If you claim a contradiction, cite both sides.
- If you suspect a stale page but cannot prove it from the files you read, label it as a review candidate rather than a confirmed issue.