plugins/lisa-wiki-copilot/skills/lisa-wiki-status/SKILL.md
Report Lisa wiki source freshness across enabled ingestion connectors. Reads wiki config, log, source notes, and state cursors, then renders a concise read-only freshness table with skipped/blocker reasons and exact next actions. Use when maintainers ask whether the wiki sources are fresh, stale, skipped, blocked, or need targeted ingest.
npx skillsauth add codyswanngt/lisa lisa-wiki-statusInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Render the Lisa wiki source freshness report without changing the repository.
This skill answers a narrower question than lisa-wiki-doctor or lisa-wiki-lint: whether each enabled, non-external-write ingestion connector has current source evidence and what the operator should do next.
Read these repository files as the source of truth:
wiki/lisa-wiki.config.json for enabled connectors and wiki root.wiki/log.md for latest ingest, skip, and blocker notes.wiki/sources/** for reader-safe source notes.wiki/state/** for connector state cursors and source-note references.Resolve the wiki root from wiki/lisa-wiki.config.json, unless --wiki or --config is passed.
Run the bundled deterministic renderer:
node plugins/lisa-wiki/scripts/wiki-status.mjs $ARGUMENTS
If running from the source plugin tree before distribution, use plugins/src/wiki/scripts/wiki-status.mjs.
Report the rendered connector table. Preserve connector verdicts exactly:
fresh, stale, never_ingested, skipped, or blocked.
Include the evidence paths, last observed date, skip/blocker reason when present, and exact next action for each non-fresh connector.
Mention lisa-wiki-lint only as a separate integrity follow-up. Do not conflate freshness with broken links, stale claims, or structure linting.
lisa-wiki-ingest refreshes sources, lisa-wiki-lint checks wiki integrity, and lisa-wiki-doctor verifies setup/readiness.
tools
--- name: harper-realtime description: This skill should be used when adding or troubleshooting Harper (HarperDB/Fabric) real-time behavior: MQTT topics, WebSocket resource subscriptions, resource publish/subscribe handlers, SSE-style streaming routes, and local subscriber verification. Pairs with harper-resources, harper-config-yaml, harper-schema-graphql, and harper-build-and-deploy. --- # Harper Realtime ## Overview Harper exposes live data through the same Resource model used for REST and
tools
--- name: harper-realtime description: This skill should be used when adding or troubleshooting Harper (HarperDB/Fabric) real-time behavior: MQTT topics, WebSocket resource subscriptions, resource publish/subscribe handlers, SSE-style streaming routes, and local subscriber verification. Pairs with harper-resources, harper-config-yaml, harper-schema-graphql, and harper-build-and-deploy. --- # Harper Realtime ## Overview Harper exposes live data through the same Resource model used for REST and
tools
--- name: harper-realtime description: This skill should be used when adding or troubleshooting Harper (HarperDB/Fabric) real-time behavior: MQTT topics, WebSocket resource subscriptions, resource publish/subscribe handlers, SSE-style streaming routes, and local subscriber verification. Pairs with harper-resources, harper-config-yaml, harper-schema-graphql, and harper-build-and-deploy. --- # Harper Realtime ## Overview Harper exposes live data through the same Resource model used for REST and
tools
--- name: harper-realtime description: This skill should be used when adding or troubleshooting Harper (HarperDB/Fabric) real-time behavior: MQTT topics, WebSocket resource subscriptions, resource publish/subscribe handlers, SSE-style streaming routes, and local subscriber verification. Pairs with harper-resources, harper-config-yaml, harper-schema-graphql, and harper-build-and-deploy. --- # Harper Realtime ## Overview Harper exposes live data through the same Resource model used for REST and