| name | link-health |
| description | Use at the start of Link work when readiness is unclear, after installs or upgrades, and before repairs; verify health, inspect interrupted writes, back up, and repair generated indexes without MCP. |
Link Health
Use the lnk CLI. Load this skill before trusting a new or changed Link wiki, after installs/upgrades, and before broad repair or restore work. In a source checkout, replace lnk with python3 link.py. MCP and the local web viewer are optional; lnk serve is only for humans to browse the wiki.
- Check readiness first:
lnk health [link-root]
- If the output mentions interrupted or stale operations, inspect them before repair:
lnk operations [link-root]
- Before broad repairs, migrations, or restore work, create a backup:
lnk backup [link-root]
- Repair only generated or structural state that Link reports as safe:
lnk doctor --fix [link-root]
lnk rebuild-index [link-root]
lnk rebuild-backlinks [link-root]
- Validate before saying the wiki is healthy:
lnk validate [link-root]
lnk health [link-root]
If the user asks whether MCP is ready, run lnk verify-mcp [link-root]. Do not start lnk serve for MCP or CLI work.
To check whether optional local semantic recall is active (lexical is always the fallback):
lnk semantic [link-root]
It reports the provider tier, model, and index state, and prints the exact setup command when the layer is available but not yet enabled.
