query
/query
Answer a question about a client project or about cross-client knowledge from the vault, starting from the canonical sources and declaring the basis of every statement. Use when the user asks what was decided, what the status is, how something works in a project, or what the vault knows about a topic.
- Author
- jvbeat ↗
- Repository
- consulting-llm-wiki ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Answer a question about a client project or about cross-client knowledge from the vault, starting from the canonical sources and declaring the basis of every statement. Use when the user asks what was decided, what the status is, how something works in a project, or what the vault knows about a topic.
Original author description
Answer a question about a client project or about cross-client knowledge from the vault, starting from the canonical sources and declaring the basis of every statement. Use when the user asks what was decided, what the status is, how something works in a project, or what the vault knows about a topic.
How it works
SKILL.md has no level-two headings · 12 lines, 177 words
SKILL.md preview
--- name: query description: Answer a question about a client project or about cross-client knowledge from the vault, starting from the canonical sources and declaring the basis of every statement. Use when the user asks what was decided, what the status is, how something works in a project, or what the vault knows about a topic. --- # Query 1. Read the project's `_curated/current-state.md`. It says what holds today and points to the canonical document of each domain. 2. Read the row of the "Canonical sources" table in the project's `CLAUDE.md` and open the document it names. Use other notes only for what the table does not cover. 3. If the question names a decision, a card or a document, read it whole before answering. Redo any arithmetic in writing. 4. Answer with citations (`[[decisions#D12]]`, `[[2026-10-01-loyalty-workshop]]`). Give every factual statement its basis: measured now, read at the source now, or not checked, and say the third one in words inside the sentence. 5. Before answering from a canonical document, look at its `verified-on`. If it is older than the limit in `_meta/llm-wiki.json`, say so in the answer. 6. Offer to file the answer in `_curated/analyses/<short-question>.md`, and log it if filed. When the user contests an answer, reopen the source first. Start the reply with "I keep" and the evidence, or "I change" and the new evidence. Changing position without new evidence is not allowed.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · jvbeat/consulting-llm-wiki | 86 | MIT |
| h1994st/rllvm | 100 | Apache-2.0 |
| garrytan/gbrain | 100 | MIT |
| garrytan/gbrain | 100 | MIT |
| proteanhq/protean | 100 | Apache-2.0 |
| oxy-hq/airlayer | 100 | Apache-2.0 |
| erayozenn/BigHead-2ndBrain | 100 | MIT |
| lambdalisue/cclens | 100 | MIT |
| oxy-hq/airlayer | 100 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version 43d270c5b281 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90new-vault
Create a consulting LLM wiki in a folder, or add a new client project to an existing one. Use when the user says "create my vault", "set up the wiki", "start a vault here", "new client", "add a project for <client>". - 90ask-company
Ask the whole company a question through Employee001 and get one answer, citing which colleague or document each fact came from. Use when the user asks what the team decided, who owns something, why something was built a certain way, or what a policy, customer or project status… - 100kb-query
Answer a keyword or topic question from the markdown knowledge base, with every fact pointing to a file and section, and outside knowledge explicitly labeled. Use when the user asks what the knowledge base says about a term, method, paper or problem, or asks a research question the base may cover. - 100second-brain-query
Answer a question from a second-brain vault by reading its own pages, citing the pages used, and saying plainly when the vault does not contain the answer. Use this skill whenever the user asks what they know about a topic, what they have read on something, what connects two… - 86vault-recall
Use before researching a topic from scratch, or when the user asks what they know, noted or decided about something. Answers from the Obsidian knowledge vault with citations. - 100wiki-query
Answer an explicitly vault-scoped question from an Obsidian wiki without changing it. Use when the user selects the vault as the evidence source: query the wiki, query quick, query deep, explain from the wiki, summarize the vault, find in wiki, search the wiki, or based on the…