graph-hygiene
SolidLogseq knowledge-graph maintenance lint. scans 7 categories (stale pages, orphans, missing properties, dead links, missing compiled-truth/timeline structure, tag inconsistency, duplicate near-names), emits severity-tagged findings. Never auto-deletes. flags for /review only. Read by graph-hygiene-weekly cron.
Install
Quality Score: 79/100
Skill Content
Details
- Author
- 0xUrsanomics
- Repository
- 0xUrsanomics/utopia-os
- Created
- 5 days ago
- Last Updated
- today
- Language
- Python
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
system-health
Preventive hygiene audit of your own Claude Code configuration — memory files, project context (CLAUDE.md), rules, permissions, skills — a deterministic scan of sizes / broken links / stale entries / excessive permissions / junk + interpretation + targeted fixes by agreement. Keeps the setup from rotting before it breaks. Triggers — "check the system", "system health", "workflow hygiene", "what to clean up", "audit memory", "optimize the system".
wiki-lint-semantic
Run the judgement-requiring health checks on the KB — whether a comparison truly covers the key difference dimensions (L4), whether cross-page conclusions contradict, whether recent kb-save output adds real value (Q2) — emitting Review-Queue proposals only, never editing any wiki page. Use when the user says "do a semantic health check / check for contradictions / see whether the comparison pages are complete". Deterministic lint (L1/L2/L3/L5/L6/broken-links/duplicates) is handled by scripts/pipeline.py lint, not here.
kg-maintain
Knowledge graph maintenance — a bounded, resumable pass that pays down the graph's DEBT line (rendered after HEALTH in every kg_read). Run it when invoked, when DEBT shows HIGH, or as a dispatched maintenance subagent. Always-on reactive triggers (no pass needed, act mid-conversation): User correction → update the stale node before continuing. Node just proved useful → add one edge to current context. Gist feels vague after using it → sharpen while context is live. Just saved a node → check: duplicate? adjacent nodes need updating? Archival is automatic and reversible — leave archived nodes alone. Deletion is a last resort, only for the factually wrong and unfixable.