plugins/lisa-wiki-copilot/skills/lisa-wiki-doctor/SKILL.md
Verify that a wiki is correctly set up and (after migration) fully functional. Runs the deterministic checks plus functional smoke tests, writes a doctor report, and returns an overall verdict. Use as the final gate of /migrate, after /setup, or anytime to confirm wiki health. A repo is not "migrated" until its doctor verdict is READY.
npx skillsauth add codyswanngt/lisa lisa-wiki-doctorInstall 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.
The post-migration / post-setup verification checklist. Orchestrates the deterministic scripts and
functional smoke tests, then writes wiki/state/migration/doctor-report.json and prints the blocking
items.
Each item is PASS | WARN | FAIL | SKIP; overall is READY | READY_WITH_WARNINGS | NOT_READY. In
hard-enforcement mode (--migration after phase 5) WARN on structure/integrity items is not
allowed; earlier phases allow documented legacy warnings. Build checks (group G) are Lisa/release-only
and SKIP in downstream repos.
validate-config.mjs + structure-manifest conformance;
required files present; schemaVersion set and rendered kernelVersion matches the installed
plugin; README mode recorded (never implicit stub).lint-wiki.mjs + diff-guard.mjs; index/log coverage;
state-order invariant; no broken/orphan links; secret/tenant/contamination/sensitivity scans;
memory sources project-scoped only (no global Codex memory / Chronicle).$lisa-wiki-* on
Codex; each config.staff[] role has its doc page + both subagents; MCP doctor passes or connector
cleanly disabled; external-write connectors skipped unless explicit intent./query returns
a cited answer; /lint clean (or expected phase warnings); /onboard-me completes read-mostly with
no PII; bare /ingest --dry-run lists non-external-write sources; /doctor rerun is idempotent.--with-ci; (Lisa
only) bun run build:plugins builds both artifacts and check:plugins passes.scripts/verify-migration.mjs (which emits the JSON report); this
skill adds the functional smoke tests and interprets phase-allowed warnings.lisa-wiki-migrate, lisa-wiki-lint, lisa-wiki-setup.
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