Skip to content
Skills Library
Personal productivity · Research

sb-query

/sb-query

Answer a question from the Trilium Symbiont with citations, using staged retrieval (hub index, hub page, detail notes). Use when the user asks what the Symbiont knows about something.

Licence
MIT
Last repository change
13.11.2026

Assessment and security

86/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content21 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Answer a question from the Trilium Symbiont with citations, using staged retrieval (hub index, hub page, detail notes). Use when the user asks what the Symbiont knows about something.

Original author description

Answer a question from the Trilium Symbiont with citations, using staged retrieval (hub index, hub page, detail notes). Use when the user asks what the Symbiont knows about something.

How it works

SKILL.md has no level-two headings · 40 lines, 393 words

SKILL.md preview
---
name: sb-query
description: Answer a question from the Trilium Symbiont with citations, using staged retrieval (hub index, hub page, detail notes). Use when the user asks what the Symbiont knows about something.
---

# Query — answer from the system, with citations

You are operating on the user's **Trilium Symbiont** via the Trilium MCP server.

**First** (umbrella `_Schema` §1): load the umbrella `_Schema` (`#sbType=schema` directly under `root`)
and read it fully; check that `#sbVersion` has major version `1` (e.g. `1.0.0`); read the **Principles** hub page;
read the **Hubs** `_Schema` for knowledge questions and the **Daily** `_Schema` for questions about time.
Respect the scope law: search only with `ancestorNoteId = <space root>`.

**Task:** answer the user's question with the least context necessary (umbrella §8).

1. **Pick the route:**
   - **Knowledge** ("what do I know about X") → stage 0: `Hubs/_Index`; stage 1: the relevant hub page
     and its Synthesis; stage 2: only the detail notes, concepts or sources you need (follow the synthesis's
     in-text links and the hub page's links).
   - **State** ("what is open in X", "which areas") → attribute queries within Hubs: `#status` (columns
     from the Board), `#sbType=area|project`, `#!archived`, due dates (`#startTime`).
   - **Time** ("what happened last week / in October") → week notes first (`#weekNote` within Daily),
     then the day notes they point to.
   - **Unclear** → start at stage 0 and say which route you took.
2. **Never open** anything outside the system. If the answer would need one, say so.
3. **Answer** with **citations** — clickable links to the notes you used. Mark what comes from an
   agent-written synthesis or concept versus a source or your own note. Thoughts are reported as
   thoughts (linked, with date), never as facts or interpretations.
4. **Gaps:** if the system holds little, say so; offer `/sb-research` (deep) or a web search for this
   answer only.
5. **Keep it?** If the answer is worth keeping, **offer** to file it as a concept under the fitting hub
   (`#sbType=concept`, `#sbControl=auto`, `#readOnly`, in-text links to the notes used) — only on a yes,
   then log it in `Hubs/_Log`. The query itself is a read and is not logged.

Depth: *quick* (stage 0–1), *standard* (up to stage 2), *deep* (plus web search, clearly separated from
what the system holds).

**End your output with exactly one status marker** on its own final line (see steering "End-of-run status
marker"): `✅ Done` / `❓ Needs your answer` / `⏸️ Awaiting confirmation` / `⚠️ Done with caveats` /
`🚫 Refused (out of scope)`.

Input: the user's request (for a slash command, the text after it).

Versions

The database has no other skills named sb-query.

Database snapshot: 13.11.2026 · package version 572868e7e704 (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

  • 90sb-hub
    Create a hub in the Trilium Symbiont on request, refresh a hub page or its synthesis, or propose a split when a hub grows too big. Use when the user asks for a new hub or to update one.
  • 90sb-init
    Bootstrap the four-space Trilium Symbiont into an empty Trilium instance from the rulebooks bundled with this skill. Use only when the user explicitly asks to set it up.
  • 100trilium-capture
    Write findings, clipped material and long documents into a self-hosted Trilium Notes instance over its native MCP, filed under a project, labelled from a controlled vocabulary, and revised in place rather than duplicated. Use when the user says to store, capture, save or file…
  • 90trilium-workflows
    Task recipes and safety rules for working with a Trilium Notes instance through the trilium MCP server beyond plain create/search - journal and day notes, the inbox, organizing the tree (move, clone, reorder), labels and relations, attachments, revisions and recovering lost…
  • 90query-wiki
    Answer a question using this OKF wiki and (optionally) file the answer back as a reusable page. Use when the user asks a question about the wiki's subject matter, asks "what does the wiki say about X", or wants an answer synthesized from the wiki's concepts/synthesis with citations.
  • 90wiki-query
    Answers a question against an Obsidian-based LLM knowledge wiki. Performs index-first search, reads relevant pages, synthesizes an answer with citations, and optionally files the synthesis back as a new wiki page. Triggers when the user runs /wiki:query or asks a question that…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.