agentleFS
Sign inStart free
VladTheProgrammerVladTheProgrammer/claude-asimov/.claude/skills/wiki-query/SKILL.md

wiki-query

Skill0 starsChanged 4 months agoMITView on GitHub

Answer a question from the wiki, grounded in its pages with [[wikilink]] citations, and optionally save the answer as a new page. Usage: /wiki-query {question}

41 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

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

  • bozhouDevSkill

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

  • 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

6 rules. 0 are common, 2 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 33 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read wiki/SCHEMA.md for layout and conventions.

    line 6
  2. Very specific:

    Read wiki/index.md to find the pages relevant to the question.

    line 13
  3. Very specific:

    Read the targeted pages (follow [[wikilinks]] to related pages as needed).

    line 18
  4. Very specific:

    Every claim should be traceable to a page — cite with [[wikilinks]].

    line 19
  5. Distinctive:

    If the wiki cannot answer:

    line 24
  6. Very specific:

    If the synthesized answer is novel and durably useful (not a one-off), offer to save it as a new wiki/concepts/ page (via the capture flow) …

    line 30

“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

Read wiki/SCHEMA.md for layout and conventions.

The whole point: answer from the compiled wiki, not by re-deriving from scratch or re-reading raw sources every time. Cite the pages you used.

Phase 1 — Orient

Read wiki/index.md to find the pages relevant to the question. Prefer concepts/, decisions/, and experiments/; fall back to sources/ and raw/ only when the wiki doesn't yet cover it.

Phase 2 — Read & synthesize

Read the targeted pages (follow [[wikilinks]] to related pages as needed). Synthesize a direct answer. Every claim should be traceable to a page — cite with [[wikilinks]]. If pages disagree, surface the conflict rather than papering over it (and flag it for /wiki-lint).

Phase 3 — Gaps

If the wiki cannot answer:

  • Say so plainly. Do not invent.
  • Point to what would fill the gap: a source to /wiki-ingest, or a concept/decision to /wiki-capture.

Phase 4 — Optionally compound

If the synthesized answer is novel and durably useful (not a one-off), offer to save it as a new wiki/concepts/ page (via the capture flow) so the knowledge compounds instead of being re-derived next time.

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