wiki-query
Skill9 starsChanged 7 months agoMITView on GitHub
Answer a Roblox/Luau question by reading the wiki. Starts from wiki/index.md, follows wikilinks to related pages, synthesizes an answer with citations, and optionally files the answer back as a new wiki page. Use whenever you need deep knowledge about a Roblox service, a Luau feature, an exploit, a pattern — the wiki is the source of truth.
42 other projects use a version of this.
Adopted by
Most recently taken up by
- tboome33/obsidian-mcp-routertheir own version, first seen Nov 15, 2026
- Ar9av/obsidian-wikitheir own version, first seen Nov 8, 2026
- barakgut/llm-wikitheir own version, first seen Nov 1, 2026
- chobizzy/llm-wikitheir own version, first seen Nov 1, 2026
- wareagledusty/wiki-federation-starter-kittheir own version, first seen Nov 1, 2026
- ProduktEntdecker/enterprise-memory-startertheir own version, first seen Nov 1, 2026
Used with
Projects with it also use wiki-capture, wiki-setup and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
jehrhardtSkillwiki-capture
Quickly capture raw thoughts, links, images, or notes to today's Obsidian daily note from anywhere in Pi. Use when the user wants to jot something down for later wiki processing.
Also in 6 projects that use this
Ivy-Chen1999Skillwiki-setup
Initialize a new Obsidian wiki vault with the correct structure, special files, and configuration. Use this skill when the user wants to set up a new wiki from scratch, initialize the vault structure, create the .env file, or says things like "set up my wiki", "initialize obsidian", "create a new vault", "get started with the wiki". Also use when the user needs to reconfigure their existing vault or fix a broken setup.
Also in 5 projects that use this
Ivy-Chen1999Skillwiki-research
Autonomously research a topic via multi-round web search, synthesize findings, and file structured results into the Obsidian wiki. Use this skill when the user says "/wiki-research [topic]", "research X", "find everything about Y", "do a deep dive on Z", "autonomous research on X", or wants comprehensive, web-sourced knowledge on a topic filed directly into their wiki.
Also in 4 projects that use this
bozhouDevSkillwiki-init
Use when bootstrapping a new personal wiki for any knowledge domain — research, codebase documentation, reading notes, competitive analysis, or any long-term knowledge accumulation project.
Also in 7 projects that use this
justvinhhereSkillwiki-review
Use when the user runs /review, says "show pending changes", "what's uncommitted", or wants an audit of uncommitted wiki edits before they land in history. Narrates uncommitted changes, flags structural issues scoped to those changes, and commits them with a conventional subject. Fully automatic.
Also in 8 projects that use this
nathanadaySkillalmagest
Orient in the Almagest vault, say what waits for the user, do the work a request asks in a linked repository, and route any other request to the skill that owns it. Use for /almagest, what is going on, status, what waits for me, where do I work on X, work on X, fix this, implement, build, note this, remember to, publish my journal, what is in my journals, and any request when the right skill is not clear. Keeping part of this conversation is wiki-save; files to learn from are wiki-ingest.
Also in 3 projects that use this
- +5 more from Ivy-Chen1999
Other versions42 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 42
- AgriciDaniel/claude-obsidian★ 16ksame name
- Ar9av/obsidian-wiki★ 3.7ksame name
- rohitg00/pro-workflow★ 2.9ksame name
- kfchou/wiki-skills★ 189same name
- bozhouDev/bozhou-skills★ 78same name
- vanillaflava/llm-wiki-skills★ 65same name
- cookyman74/llmwiki-harness★ 34same name
- Ivy-Chen1999/llm-wiki-kit★ 21same name
- CarbeneAI/Forge★ 9same name
- crabin/llm-wiki★ 8same name
32 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository51 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- asset-auditSkill
- asset-from-imageSkill
- balance-checkSkill
- brainstormSkill
- bug-reportSkill
- changelogSkill
- code-reviewSkill
- datastore-reviewSkill
- design-reviewSkill
- design-systemSkill
- doctorSkill
- economy-auditSkill
- estimateSkill
- exploit-checkSkill
- gate-checkSkill
- gddSkill
- generate-assetSkill
- hotfixSkill
- launch-checklistSkill
- luau-lintSkill
- map-systemsSkill
- milestone-reviewSkill
- monetization-modelSkill
- onboardSkill
- patch-notesSkill
- perf-profileSkill
- project-stage-detectSkill
- prototypeSkill
- publish-reviewSkill
- release-checklistSkill
- remotes-auditSkill
- retention-analysisSkill
- retrospectiveSkill
- reverse-documentSkill
- scope-checkSkill
- sprint-planSkill
- startSkill
- studio-inspectSkill
- studio-screenshotSkill
- studio-testSkill
- team-combatSkill
- team-economySkill
- team-polishSkill
- team-releaseSkill
- team-uiSkill
- tech-debtSkill
- wiki-ingestSkill
- wiki-lintSkill
- wiki-seedSkill
- wiki-updateSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. 0 are common, 9 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 34 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 42
Read each candidate page fully.
- Very specific: line 49
If a candidate page's Related section points to other pages that look relevant, read those too.
- Distinctive: line 55
Write a focused answer that:
- Distinctive: line 58
Shows code: when code is the best answer (copy from the wiki page)
- Distinctive: line 59
Notes uncertainty: if sources disagree or information is sparse
- Distinctive: line 95
If the wiki doesn't have the answer:
- Very specific: line 104
If wiki/raw/ has captured sources not yet ingested, offer to read them directly (not through the curated wiki) and give the user a …
- Distinctive: line 108
If the answer is substantive and would be useful to someone else asking the same question in the future, offer:
- Very specific: line 112
If approved, create the new page via the /wiki-update workflow and log it as a query-generated contribution:
- Very specific: line 136
Check wiki/services/X.md, wiki/concepts/x.md, wiki/luau/x.md
- Distinctive: line 137
Read the page → synthesize summary
- Very specific: line 141
Check wiki/concepts/, wiki/patterns/, wiki/anti-patterns/, wiki/exploits/
- Distinctive: line 157
Read the wiki concept page(s) the rule points to
- Very specific: line 163
Citations are mandatory: every non-trivial claim has [[wikilink]]
- Distinctive: line 164
Code over prose: when code is clearer
“Common” is measured: kept by at least 6 in 10 of the 34 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/wiki-query — Ask the Wiki
Delegate to: wiki-curator
Arguments
<question>— a natural-language question (e.g., "what's the safest way to handle trading with session locks", "how do I prevent speed hacks", "what are the DataStore budget limits")
Prerequisites
- Wiki has been seeded (
wiki/index.mdexists) - The question is relevant to Roblox/Luau knowledge (not project-specific — those go to domain skills)
Workflow
1. Understand the Question
Parse what the user is asking:
- Factual (what is X?): usually answerable from a single page
- How-to (how do I do X?): usually answerable from a concept or pattern page
- Comparative (X vs Y?): requires reading multiple pages
- Synthesis (what's the best way to X?): requires reading multiple pages and integrating
2. Read the Index
Load wiki/index.md fully. This is the content catalog — scan for candidate pages that might contain the answer.
3. Identify Candidate Pages
Based on the question, pick 3-10 candidate pages from the index. Prefer:
- Direct matches (question mentions "DataStoreService" →
wiki/services/DataStoreService.md) - Relevant concepts (question mentions "trading" →
wiki/patterns/atomic-trading.md,wiki/concepts/session-locking.md) - Related anti-patterns or exploits (question about security →
wiki/exploits/*.md)
4. Read the Candidate Pages
Read each candidate page fully. Note:
- What it answers directly
- What links it points to (for follow-up)
- What
sources:it cites (in case the user wants to go deeper)
5. Follow Related Links
If a candidate page's Related section points to other pages that look relevant, read those too. Stop when:
- You have enough to answer the question confidently
- You've read > 10 pages (signal the question is too broad)
6. Synthesize the Answer
Write a focused answer that:
- Directly addresses the question (don't meander)
- Cites every claim by
[[wikilink]]to the page where it's supported - Shows code when code is the best answer (copy from the wiki page)
- Notes uncertainty if sources disagree or information is sparse
- Recommends deeper reading by listing 2-3 Related pages
Structure:
# Answer: <short question restatement>
**Short answer:** 1-2 sentences.
## Details
<full explanation with [[wikilink]] citations to every claim>
## Code
<relevant code example from the wiki>
## Caveats
<edge cases, gotchas, "but if..." clauses>
## Sources (wiki pages read)
- [[Page 1]]
- [[Page 2]]
- [[Page 3]]
## Related (you may want to read next)
- [[Related Page 1]]
- [[Related Page 2]]7. Handle Missing Information
If the wiki doesn't have the answer:
Option A — partial answer + flag gap:
"The wiki has
<partial info>from [[Page]], but doesn't cover<specific aspect>. You can either:
- Run
/wiki-ingeston a source that covers it (checkwiki/raw/for candidates)- Create a new page via
/wiki-update- Accept the partial answer"
Option B — search raw sources:
If wiki/raw/ has captured sources not yet ingested, offer to read them directly (not through the curated wiki) and give the user a raw-source-backed answer with the caveat "this is from uncurated raw content."
8. Offer to File the Answer Back
If the answer is substantive and would be useful to someone else asking the same question in the future, offer:
"This answer would make a good wiki page at
[[<proposed-page-name>]]. Should I file it?"
If approved, create the new page via the /wiki-update workflow and log it as a query-generated contribution:
## [YYYY-MM-DD] query | <short question>
- Pages read: [[page1]], [[page2]], [[page3]]
- Answer filed: [[new-page]]This is how the wiki compounds — good answers become new pages.
9. Log the Query
Whether or not the answer was filed:
## [YYYY-MM-DD] query | <short question>
- Pages read: [[list]]
- Answer: <1-line summary or "filed as [[new-page]]">
- Gap found: <if any — describe and recommend>Query Patterns
"What is X?"
- Check
wiki/services/X.md,wiki/concepts/x.md,wiki/luau/x.md - Read the page → synthesize summary
- Usually answerable from 1-2 pages
"How do I do X safely?"
- Check
wiki/concepts/,wiki/patterns/,wiki/anti-patterns/,wiki/exploits/ - Read 3-5 pages
- Answer combines "the pattern to follow" + "the anti-pattern to avoid"
"Why is X slow?"
- Check
wiki/performance/*.md - Also check
wiki/services/<X>.mdfor budget/limits - Answer cites concrete numbers
"Is X an exploit risk?"
- Check
wiki/exploits/*.md - Check
wiki/concepts/server-authority.md,wiki/concepts/rate-limiting.md - Answer lists the attack vectors and mitigations
"What does the rule Y mean?"
- Read
.claude/rules/Y.md - Read the wiki concept page(s) the rule points to
- Answer explains "what the rule says" + "why it exists"
Output Discipline
- Short > long: answer what was asked, not everything you know
- Citations are mandatory: every non-trivial claim has
[[wikilink]] - Code over prose when code is clearer
- Honest uncertainty: say "the wiki doesn't cover X" when it doesn't
Anti-Patterns
- ❌ Do not fabricate Roblox APIs
- ❌ Do not answer from general Lua knowledge — use the wiki (or say you can't)
- ❌ Do not skip citations
- ❌ Do not read > 10 pages for one question (signal the question is too broad and ask user to narrow)
- ❌ Do not file every answer back — only substantive, reusable ones
- ❌ Do not silently create wiki pages without user approval
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

