Lore Check

Read ${CLAUDE_PLUGIN_ROOT}/reference/lore-spec.md first — the entry-meta format, the "What lore is / isn't" boundary test, and the feedback-log format all come from there.

When to use

When you want to know whether a project's lore is healthy and actually pulling its weight: on an explicit request ("how healthy is our lore?", "is the lore still useful?"), or as a periodic check. Only meaningful when the repo has a docs/lore/ folder — if there is none, say so briefly and suggest lore-init, rather than reporting an empty audit.

This skill is read-only. It never edits, marks, or deletes anything — it produces a report and hands the fixes off.

Procedure

Run all seven checks, then produce one report. Use your file tools directly (Read, Grep, checking that paths exist) — there is no script to run.