agentleFS
Sign inStart free
juanitourquizajuanitourquiza/shipframe/skills/wiki-query/SKILL.md

wiki-query

Skill4 starsChanged 21 days agoMITView on GitHub

Answer questions from the active project wiki by reading the index and relevant wiki pages.

41 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use wiki-capture, wiki-update 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.
  • jehrhardtSkill

    wiki-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

  • bozhouDevSkill

    wiki-update

    Use when revising existing wiki pages because knowledge has changed, a new piece of information updates or contradicts existing content, or the user wants to directly edit wiki content with LLM assistance.

    Also in 9 projects that use this

  • Ivy-Chen1999Skill

    wiki-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-Chen1999Skill

    wiki-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

  • justvinhhereSkill

    wiki-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

  • nathanadaySkill

    almagest

    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

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 4 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 33 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Before searching, locate the wiki in the current directory.

    line 22
  2. Very specific:

    Look for a wiki/ folder containing an index.md file.

    line 23
  3. Very specific:

    If wiki/index.md is not found, check if there is a CLAUDE.md at the root — it may indicate where the wiki is or what the main folder is …

    line 26
  4. Distinctive:

    If there is no wiki, tell the user: "I can't find a wiki in this folder.

    line 29
  5. Very specific:

    Read wiki/index.md. This file lists all wiki pages with a one-line summary each, organized by category (the wiki subdirectories).

    line 36
  6. Distinctive:

    If a page references another via wikilink and that reference seems important to complete the answer, open it too.

    line 53
  7. Very specific:

    Only go to raw/ if:

    line 73
  8. Distinctive:

    Do not read all pages "just in case": Read the index, identify the relevant ones, and go directly.

    line 89
  9. Distinctive:

    Do not invent information: If it's not in the wiki, say so clearly.

    line 93

“Common” is measured: kept by at least 6 in 10 of the 33 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

wiki-query

Smart search in any LLM wiki vault.

Implements the QUERY flow of the LLM Wiki pattern: find information in the wiki quickly and precisely, without unnecessary traversal.

Works with any vault that follows the standard LLM wiki structure, regardless of the topic (a course, a project, personal notes, etc.).

Step 0 — Discover the wiki

Before searching, locate the wiki in the current directory. Look for a wiki/ folder containing an index.md file. This file is the master catalog and the mandatory entry point.

If wiki/index.md is not found, check if there is a CLAUDE.md at the root — it may indicate where the wiki is or what the main folder is called.

If there is no wiki, tell the user: "I can't find a wiki in this folder. Would you like me to create one?" (and if so, use the wiki-forge skill).

Step 1 — Scan the index

Read wiki/index.md. This file lists all wiki pages with a one-line summary each, organized by category (the wiki subdirectories).

From the index, identify the 1-3 pages most relevant to the user's question. The key: the index already tells you what each page contains. You don't need to open all of them — only the ones that fit.

Step 2 — Read the relevant pages

Open only the pages identified in the previous step. Each page has:

  • YAML frontmatter: tags, type, sources, dates — useful for filtering
  • Content: the text with the information
  • Wikilinks [[page-name]]: links to related pages

If a page references another via wikilink and that reference seems important to complete the answer, open it too. But don't chain long read sequences — 2-3 pages are usually enough.

Step 3 — Synthesize and answer

Answer the user's question citing the wiki pages consulted. Natural and direct format. At the end, include the sources as references:

Sources: [[page-name-1]], [[page-name-2]]

When to go to the original sources

Many wikis have a raw/ folder with raw materials (transcripts, articles, original documents). These are immutable.

Only go to raw/ if:

  • The user asks for an exact verbatim quote
  • The wiki doesn't have enough detail to answer
  • You need to verify something specific

Pages in the sources/ subfolder of the wiki are summaries of each original source — they work as a bridge between the processed wiki and the raw material. Check them first before going directly to raw/.

What NOT to do

  • Do not grep or launch agents. The index exists precisely to avoid brute-force searches. Use it.
  • Do not read all pages "just in case". Read the index, identify the relevant ones, and go directly.
  • Do not answer without consulting the wiki. The purpose of this skill is that the answer comes from the pages, not from general knowledge.
  • Do not invent information. If it's not in the wiki, say so clearly. You can suggest the user ingest new information with wiki-forge.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free