agentleFS
tograftograf/sidebrain/.claude/skills/query/SKILL.md

query

Skill1 starsChanged 5 months agoMITView on GitHub

Answer a question from the vault. Search the notes (qmd if installed, otherwise Grep/Glob), read the top notes in full, and synthesize an answer with wikilink citations — then offer to file the answer back into the vault so explorations compound. Use whenever the user asks a question the vault may already cover.

38 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use attach-db, install-duckdb and 6 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.
  • duckdbSkill

    attach-db

    Attach a DuckDB database file for use with /duckdb-skills:query. Explores the schema (tables, columns, row counts) and writes a SQL state file so subsequent queries can restore this session automatically via duckdb -init.

    Also in 3 projects that use this

  • carlopiSkill

    install-duckdb

    Install or update DuckDB extensions. Each argument is either a plain extension name (installs from core) or name@repo (e.g. magic@community). Pass --update to update extensions instead of installing.

    Also in 3 projects that use this

  • carlopiSkill

    read-file

    Read and explore any data file (CSV, JSON, Parquet, Avro, Excel, spatial, …) by filename only — resolves the path automatically. Uses DuckDB + the magic extension for format auto-detection. Installs magic if needed.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    lint

    Run all linting and spell checking for TypeScript and Rust code. Run this before committing to catch style issues, clippy warnings, and misspellings.

    Also in 17 projects that use this

  • seongjaeryuSkill

    save

    Complete and save your current thinking to Bindly

    Also in 4 projects that use this

  • AnthropicSkill

    start

    Set up your bio-research environment and explore available tools. Use when first getting oriented with the plugin, checking which literature, drug-discovery, or visualization MCP servers are connected, or surveying available analysis skills before starting a new project.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 31 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    No qmd (default path): search in two passes — (a) scan the ## Index sections of the topic starter notes (04-Resources/<Topic>/<Topic>.md) …

    line 22
  2. Distinctive:

    Read the top notes in full: before answering — search snippets are only leads.

    line 27
  3. Very specific:

    Offer to file the answer back: If the answer required real synthesis (a comparison, an analysis, a connection across notes), it shouldn't …

    line 35
  4. Distinctive:

    Never present un-sourced recall as if it came from the vault — if you add general knowledge on top of vault content, label it as such.

    line 44

“Common” is measured: kept by at least 6 in 10 of the 31 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
<!-- Adapted from the query skill of a private LLM-wiki repo (see BACKLOG.md), following the LLM-wiki pattern (karpathy). Reworked for this PARA vault: qmd optional, Grep fallback. -->

query — answer a question from the vault

Answer from what the vault actually contains, not from model memory. Vault conventions live in CLAUDE.md.

Folder paths in this skill are the template defaults — the authoritative paths live in the "Folder roles" table in CLAUDE.md's Vault structure section. Look folders up there by role — never trust the literal defaults on a renamed or non-English vault.

Steps

  1. Search the vault. Probe once with command -v qmd:
    • qmd installed: qmd query "<the user's question>" -n 10 (hybrid search + re-rank). For search syntax beyond that, defer to qmd skill show.
    • No qmd (default path): search in two passes — (a) scan the ## Index sections of the topic starter notes (04-Resources/<Topic>/<Topic>.md) and the project/area files, (b) Grep key terms and their synonyms across **/*.md (a question about "clients" may be filed under "customers"). Follow [[wikilinks]] from the hits one hop out.
  2. Read the top notes in full before answering — search snippets are only leads. Include the linked source note when a concept note cites one.
  3. Synthesize the answer from the retrieved text, citing notes as [[wikilinks]]. Distinguish what a cited source claims from established fact. If the vault doesn't cover the question, say so plainly rather than inventing — and point out that the gap is an ingest candidate.
  4. Offer to file the answer back. If the answer required real synthesis (a comparison, an analysis, a connection across notes), it shouldn't vanish into chat history — offer to save it as a note in the fitting 04-Resources/<Topic>/ (or the relevant project/area file). If accepted: write the note with frontmatter and wikilinks to everything it drew on, add it to the ## Index section of the topic's starter note, log one line in today's daily note, and re-embed if qmd is installed. Skip the offer for trivial lookups.

Quality bar

  • Never present un-sourced recall as if it came from the vault — if you add general knowledge on top of vault content, label it as such.
  • Cited notes must actually support the claim — re-read, don't pattern-match on titles.

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.