codyswanngt/lisa-wiki-setup
plugins/lisa-wiki-copilot/skills/lisa-wiki-setup/SKILL.md
Scaffold, repair, verify, or upgrade a project's LLM Wiki from its config. Use when setting up the wiki in a new repo, fixing a broken/incomplete structure, or upgrading to a newer kernel version. Asks the wiki's purpose and README mode, renders the contract snapshot, scaffolds the canonical folders, and seeds the staff roster. Idempotent and non-destructive.
$ install --global
skillsauthnpx skillsauth add codyswanngt/lisa lisa-wiki-setupInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 6, 2026, 3:46 AM274.1s1 file scanned
SKILL.md
- name:
- lisa-wiki-setup
- description:
- Scaffold, repair, verify, or upgrade a project's LLM Wiki from its config. Use when setting up the wiki in a new repo, fixing a broken/incomplete structure, or upgrading to a newer kernel version. Asks the wiki's purpose and README mode, renders the contract snapshot, scaffolds the canonical folders, and seeds the staff roster. Idempotent and non-destructive.
lisa-wiki-setup
Bring a repo's wiki/ into conformance with the canonical structure from
wiki/lisa-wiki.config.json. Safe to re-run: it creates what is missing and repairs drift, but
never overwrites human-authored content.
When to use
- First-time setup of the wiki in a repo.
- Repairing a wiki that fails
/doctorstructural checks. - Upgrading after a new
lisa-wikirelease (--upgrade): re-render the contract snapshot and run a compatibility report before writing. --with-ci: also install the optional GitHub Action validator (ci/lisa-wiki-validate.yml).
Workflow
- Config. Read
wiki/lisa-wiki.config.json, or create it interactively. Ask for:org,displayName,purpose(one paragraph — what this wiki is for),mode(embedded|wrapper|standalone|subdir),categories, source layout, connectors, sensitivity,sourceRetention, and the README mode (richdefault |stub|preserve— always ask; never selectstubimplicitly). Ifstaffis absent, seed the standard roster (below) as the default — every wiki gets the standard operating team unless the user opts out or edits it. Union each role's owned categories intoconfig.categories. Validate withscripts/validate-config.mjs. - Structure. Scaffold the canonical tree per
schema/wiki-structure.schema.json:wiki/{index.md, log.md, start-here.md, schema/, sources/, state/, staff/, <category dirs>}. Create only what is missing. - Contract. Render
wiki/schema/llm-wiki-contract.mdfrom the plugin templates + config viascripts/render-contract.mjs, stamping thekernelVersion. This snapshot keeps the wiki self-describing without the plugin installed. - Gitignore. Merge the lisa-wiki gitignore block into the project's
.gitignoreviascripts/ensure-gitignore.mjs. The block (delimited by# BEGIN: AI GUARDRAILS WIKI/# END: AI GUARDRAILS WIKI) covers transient per-session worktrees and Lisa backup snapshots (.claude/worktrees/,.codex/worktrees/,.lisabak/). Idempotent: re-running produces no diff once the block is present. The block coexists with the base lisa plugin's# BEGIN: AI GUARDRAILSblock — both can be installed without overwriting each other because the copy-contents strategy keys on the marker suffix. Wiki-wrapper repos (modewrapper/standalone) typically don't enable the base lisa plugin, so this step is the only path by which they get the worktree-ignore patterns. - Pointers. Ensure
AGENTS.md/CLAUDE.mdpoint at the contract + plugin (thin pointers only). - Staff. For each
config.staff[]entry (the standard roster by default), generate the role'swiki/staff/<role>.mdpage and its dual-runtime subagents by delegating tolisa-wiki-add-role(running the subagents is out of scope). - README. Apply the chosen README mode (ingest the old README first;
richkeeps install/usage + adds the onboarding line;stubis the minimal pointer;preserveleaves it). - Verify. Run
lisa-wiki-doctorand report the verdict + any blocking items.
Standard roster
The default operating team seeded into config.staff[] for every new wiki (Chief of Staff plus six
domain agents). Each role becomes a wiki/staff/<id>.md page and a dual-runtime subagent; the human
owner talks to Chief, who routes to the others. Owned categories are unioned into config.categories.
| id | role | owns (categories) | sensitivity |
|---|---|---|---|
| chief | Chief of Staff | projects, decisions, playbooks, open-questions | confidential |
| sally | Sales | sales | internal |
| mark | Marketing | marketing | internal |
| felix | Finance | finance | confidential |
| casey | Customer Success | customers | internal |
| parker | People | people | confidential |
| lex | Legal & Compliance | legal | confidential |
Projects may add, remove, or rename roles afterward; the standard roster is the starting point, not a constraint.
Rules
- Idempotent; re-running produces no spurious changes.
- Never overwrite human content; only create/repair structure and the rendered snapshot. The README is
rewritten only after its old content has been ingested, and only per the chosen
readme.mode. - Project-scoped only; never stage secrets/OAuth artifacts; honor
modesafety (wrapper/standalone).
Related
lisa-wiki-add-role, lisa-wiki-doctor, lisa-wiki-migrate, lisa-wiki-usage.
Related Skills
codyswanngt/plugins/src/harper-fabric/skills/harper-realtime
tools
VerifiedTrustedCommunity
--- 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
1SKILL.mdUpdated Jun 13, 2026
codyswanngt/plugins/lisa-harper-fabric/skills/harper-realtime
tools
VerifiedTrustedCommunity
--- 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
1SKILL.mdUpdated Jun 13, 2026
codyswanngt/plugins/lisa-harper-fabric-cursor/skills/harper-realtime
tools
VerifiedTrustedCommunity
--- 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
1SKILL.mdUpdated Jun 13, 2026
codyswanngt/plugins/lisa-harper-fabric-copilot/skills/harper-realtime
tools
VerifiedTrustedCommunity
--- 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
1SKILL.mdUpdated Jun 13, 2026