agentleFS
Sign inStart free
TrueHOOHATrueHOOHA/LLM-Wiki/.agents/skills/llm-wiki-query/SKILL.md

llm-wiki-query

Skill22 starsChanged 4 months agoApache-2.0View on GitHub

Answer operator questions using the LLM Wiki as the primary source of truth, and optionally file reusable syntheses back into the wiki. Use whenever the operator asks a question about wiki content, queries the knowledge base, requests a synthesis across sources, or wants an answer based on what has been ingested.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. gavishap/omnia-vault★ 53same name
    2. dotlabshq/crux★ 4same name

    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 repository3 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Primary-source discipline: Use wiki pages first (wiki/index.md, then linked pages) before external assumptions.

    line 16
  2. Distinctive:

    Conditional filing: Do not file a synthesis page without operator confirmation when framing/reusability is ambiguous.

    line 18
  3. Very specific:

    Append-only log when filing: If a synthesis is filed, append a new date-grouped entry to wiki/log.md only.

    line 19
  4. Very specific:

    Index freshness when filing: If a new synthesis page is created, wiki/index.md must be rebuilt in the same operation.

    line 20

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

LLM Wiki Query Skill

Purpose

Answer operator questions using the wiki as the primary source of truth, with reusable syntheses optionally filed back into the wiki. The wiki is an OKF v0.1 bundle (see SPEC.md); wiki/ is the bundle root.

Preconditions (must pass before analysis)

  1. An operator question is provided.
  2. wiki/index.md exists and is readable as the routing map for relevant pages.

Guardrails

  • Primary-source discipline: Use wiki pages first (wiki/index.md, then linked pages) before external assumptions.
  • Cited answers: Claims in the answer must cite relevant wiki pages via Obsidian wikilinks ([[note]] / [[note|Display]]); external sources use standard markdown links.
  • Conditional filing: Do not file a synthesis page without operator confirmation when framing/reusability is ambiguous.
  • Append-only log when filing: If a synthesis is filed, append a new date-grouped entry to wiki/log.md only; do not edit prior entries (OKF §7).
  • Index freshness when filing: If a new synthesis page is created, wiki/index.md must be rebuilt in the same operation.
  • Single source of truth: The schema is defined in AGENTS.md. This skill enforces it; it never re-defines page types, frontmatter, or sections inline.

Required Step Order (exact)

  1. Read wiki/index.md to discover relevant pages.
  2. Read relevant pages across entities, concepts, sources, and syntheses.
  3. Synthesize answer with citations using Obsidian wikilinks to pages used.
  4. Present answer to operator.
  5. If reusable/new synthesis: file it in wiki/syntheses/ following AGENTS.md § Synthesis Pages (frontmatter with non-empty type plus title/description/question/tags/timestamp; H1 sections including # Citations with numbered wikilinks for source pages and markdown links for external URLs), then rebuild wiki/index.md per the Canonical rebuild procedure in AGENTS.md § Update Rules for Special Files, and append to wiki/log.md a single new ## YYYY-MM-DD entry (OKF §7) with bullets * **Query**: <question> — <summary>., * **Pages touched**: ..., * **Notes**: ..., * **Open questions**: ....

Operator Interaction Prompts

  • Before filing (minimal):
    • "Should I file this answer as a reusable synthesis page in wiki/syntheses/?"
    • "If yes, what exact question/title should the synthesis preserve?"

Done Gate (verify before reporting done)

  • Delivered answer cites wiki pages via Obsidian wikilinks for every claim.
  • If filed: the synthesis page complies with its type contract in AGENTS.md § Synthesis Pages (non-empty type plus title/description/question/tags/timestamp; all REQUIRED H1 sections present — optional sections marked "omit otherwise" in AGENTS.md, e.g. # Comparison Table, may be omitted), uses Obsidian wikilinks for internal links (markdown links only for external URLs), has no legacy updated/source_path fields, wiki/index.md is rebuilt per the Canonical rebuild procedure and lists the new page, and wiki/log.md has a newly appended ## YYYY-MM-DD query entry.

Path Handling Rules

  • Discovery entrypoint: wiki/index.md.
  • Evidence pages: wiki/entities/, wiki/concepts/, wiki/sources/, wiki/syntheses/.
  • Optional filing target: wiki/syntheses/YYYY-MM-DD--<slug>.md.
  • Required bookkeeping on filing: wiki/index.md, wiki/log.md.

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