How do I install the Lisa Wiki Query skill?

Run npx skillmds@latest add codyswanngt/lisa-wiki-query-3 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Lisa Wiki Query skill do?

Answer a question from the LLM… It is listed under AI & ML on SkillMD.

Is Lisa Wiki Query safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Lisa Wiki Query?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Lisa Wiki Query free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Lisa Wiki Query?

codyswanngt (@codyswanngt) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Lisa Wiki Query by codyswanngt — Agent Skill

Name: Lisa Wiki Query
Author: codyswanngt

File contents

lisa-wiki-query

Answer from the wiki, with citations, without changing it (by default).

Workflow

Resolve the wiki root. Run the bundled resolver from the installed Lisa wiki plugin, not from the consumer repository's scripts/ directory:
```
node "${PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT:-${CURSOR_PLUGIN_ROOT:-$(npm root)/@codyswann/lisa/plugins/lisa-wiki}}}/scripts/ensure-wiki.mjs" --json
```
Use the returned wikiRoot as the base for every read below — never assume wiki/. A local wiki resolves instantly (no-op); a wiki whose .lisa.config.json declares wiki.source.url is mirrored and refreshed transparently first. The script is offline-tolerant (it proceeds with the existing mirror and warns rather than blocking), so freshness is guaranteed here and the caller never has to think about it.
Read <wikiRoot>/index.md to locate candidate pages; consult <wikiRoot>/start-here.md for orientation.
Drill into the relevant synthesis pages and their cited source notes.
Synthesize an answer. Every claim cites its wiki page and/or source note. If the wiki does not support an answer, say so plainly rather than inventing one; suggest an /ingest that would fill the gap. Only record the gap in wiki/open-questions/ if the user explicitly asks (that is a writeback — see step 4); never write it silently.
Writeback (opt-in only): if — and only if — the user explicitly asks to persist new synthesis discovered during the query, route it through the ingest pipeline so provenance/index/log/state stay consistent, and log it as a QUERY operation. Never write back silently.

Rules

Read-only by default. No page edits, index/log changes, state advancement, or PRs unless the user explicitly requests writeback.
Prefer the wiki's own content over outside knowledge; distinguish wiki-sourced facts from your own reasoning.
Surface contradictions or stale claims you encounter as /lint-style findings rather than silently picking one.

lisa-wiki-ingest, lisa-wiki-lint, lisa-wiki-usage.

---name: lisa-wiki-query-3description: Answer a question from the LLM…---# lisa-wiki-queryAnswer from the wiki, with citations, without changing it (by default).## Workflow0. **Resolve the wiki root.** Run the bundled resolver from the installed Lisa wiki plugin, not from the consumer repository's `scripts/` directory: ```bash node "${PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT:-${CURSOR_PLUGIN_ROOT:-$(npm root)/@codyswann/lisa/plugins/lisa-wiki}}}/scripts/ensure-wiki.mjs" --json ``` Use the returned `wikiRoot` as the base for every read below — never assume `wiki/`. A local wiki resolves instantly (no-op); a wiki whose `.lisa.config.json` declares `wiki.source.url` is mirrored and refreshed transparently first. The script is offline-tolerant (it proceeds with the existing mirror and warns rather than blocking), so freshness is guaranteed here and the caller never has to think about it.1. Read `<wikiRoot>/index.md` to locate candidate pages; consult `<wikiRoot>/start-here.md` for orientation.2. Drill into the relevant synthesis pages and their cited source notes.3. Synthesize an answer. **Every claim cites its wiki page and/or source note.** If the wiki does not support an answer, say so plainly rather than inventing one; suggest an `/ingest` that would fill the gap. Only record the gap in `wiki/open-questions/` if the user explicitly asks (that is a writeback — see step 4); never write it silently.4. **Writeback (opt-in only):** if — and only if — the user explicitly asks to persist new synthesis discovered during the query, route it through the ingest pipeline so provenance/index/log/state stay consistent, and log it as a `QUERY` operation. Never write back silently.## Rules- **Read-only by default.** No page edits, index/log changes, state advancement, or PRs unless the user explicitly requests writeback.- Prefer the wiki's own content over outside knowledge; distinguish wiki-sourced facts from your own reasoning.- Surface contradictions or stale claims you encounter as `/lint`-style findings rather than silently picking one.## Related`lisa-wiki-ingest`, `lisa-wiki-lint`, `lisa-wiki-usage`.

Frequently asked questions

Lisa Wiki Query