// Answer substantive questions from the supplements wiki and optionally file reusable answers into wiki/queries. Use for practical supplement questions, comparisons, stack decisions, evidence questions, mechanism questions, safety checks, and "what does the wiki say about..." prompts. Does not commit to git.
Quick preliminary research on a supplement or question. Searches for promising evidence that might warrant full deep research. Outputs a structured scouting brief to wiki/scouting/ — kept separate from the main wiki until promoted through deep research and ingest. Use when: "is X worth researching deeper?", "what's the preliminary evidence for X?", "$scout taurine cognitive", "should I research quercetin?". Do NOT use for comprehensive research (use foundry-research deep-research instead) or for wiki ingestion (use wiki-ingest).
Ingest a source into the supplements wiki, or re-audit a past ingest. Use for foundry-research reports such as "ingest the sulforaphane research" or "$wiki-ingest sulforaphane"; arbitrary sources in raw/ such as "ingest the source at raw/foo.pdf" or "$wiki-ingest raw/foo.md"; and audit-only mode such as "$wiki-ingest --audit-only sulforaphane" or "what did we miss in the sulforaphane ingest?" Orchestrates staging, pre-check, repo-local extractor and auditor role instructions, and gap-report append. Does not commit to git; the human reviews first.
Health-check the supplements wiki structurally and conceptually. Use when the user says "lint the wiki", asks whether the vault is clean, asks for maintenance findings, or wants low-risk structural fixes. Runs deterministic lint first, then performs targeted judgment-dependent review. Does not commit to git.
Make a scoped corrective edit to existing supplement wiki pages when the problem is already known. Use for audit findings, attribution mismatches, broken source links, stale status fields, scope qualifiers, metadata drift, or other narrow page issues that do not require a full re-ingest. Does not commit to git.
Run a periodic supplements wiki review. Use when the user says "run a wiki review", "monthly review", "quarterly review", "review the supplements vault", or asks what needs attention beyond a single ingest/query.
Ingest a source into the supplements wiki, or re-audit a past ingest. Use for two source types: (1) foundry-research reports — "ingest the sulforaphane research", "/wiki-ingest sulforaphane"; (2) arbitrary sources in raw/ — "ingest the source at raw/foo.pdf", "/wiki-ingest raw/foo.md". Also handles audit-only mode — "/wiki-ingest --audit-only sulforaphane", "what did we miss in the sulforaphane ingest?". Orchestrates the pipeline — stage source, present the pre-check, run wiki-extractor, run wiki-auditor, append the gap report. Does not commit to git; the human reviews first.
| name | wiki-query |
| description | Answer substantive questions from the supplements wiki and optionally file reusable answers into wiki/queries. Use for practical supplement questions, comparisons, stack decisions, evidence questions, mechanism questions, safety checks, and "what does the wiki say about..." prompts. Does not commit to git. |
Use this skill when the user asks a substantive question that should be answered from the accumulated wiki, not from a fresh web search.
wiki-repair.wiki/handoff.md.purpose.md.wiki/synthesis.md.wiki/queries/README.md.wiki/catalog.md if present; otherwise read wiki/index.md.Identify the likely page set:
wiki/interactions.md, wiki/Quick Reference Dosing.md, or
wiki/comparisons/ for practical decisions.Read only the relevant pages first, then follow wikilinks as needed.
In the answer:
File a durable query page when the answer is:
Do not file one-off lookups or answers that only restate one page.
When in doubt, ask once: "File this as a query page?"
Create a page under wiki/queries/ with type: query unless the answer is
better represented as a comparison, hypothesis, stack, decision, or dosing
page under the corresponding directory.
For a type: query page:
sources:, and > [!tldr].sources:.wiki/queries/README.md, DataView, and wiki/catalog.md, but they should
not be dead ends.After filing:
wiki/catalog.md:python3 wiki/scripts/lint.py --rebuild-catalog
wiki/log.md:
### [YYYY-MM-DD] query | <one-line question framing>wiki/handoff.md if the query creates follow-up work.wiki/synthesis.md only if the answer changes the top-level
practical story.Do not edit wiki/index.md; it is DataView-driven.
Return:
Do not commit to git.