agentleFS
Sign inStart free
ozgurkarahanozgurkarahan/ai-agent-memory/.claude/skills/query/SKILL.md

query

Skill8 starsChanged 4 months agoMITView on GitHub

Answer a question by searching the wiki: read index.md, find relevant pages, synthesize an answer with [[wikilink]] citations, file the answer in wiki/_queries/, update log.md. Trigger: 'query [question]' or a direct knowledge-base question.

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 7 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

  • 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

  • MicrosoftSkill

    doctor

    Diagnose an Amplifier CLI environment through the CLI doctor agent. USE WHEN a user requests CLI runtime, settings or missing-capability inspection. DO NOT USE for project bugs or other hosts.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 2 are distinctive, and 3 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.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When the user asks a question about the knowledge base or says "query":

    line 8
  2. Very specific:

    If memory/schema.md exists in the current workspace, use memory/.

    line 12
  3. Very specific:

    If no folder containing both schema.md and index.md resolves, report the missing path and stop.

    line 15
  4. Distinctive:

    All paths below are relative to that memory root.

    line 17
  5. Very specific:

    Update wiki/_queries/_index.md: if a new page was filed

    line 27

“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

Query Wiki

When the user asks a question about the knowledge base or says "query":

Resolve the memory root

  1. If memory/schema.md exists in the current workspace, use memory/.
  2. Else if schema.md exists, use the current directory.
  3. Else follow the memory-wiki path declared in AGENT.md.
  4. If no folder containing both schema.md and index.md resolves, report the missing path and stop.

All paths below are relative to that memory root.

  1. Read index.md first — scan the content catalog for relevant pages
  2. Read relevant pages in full — don't skip or summarize prematurely
  3. Synthesize an answer with [[wikilink]] citations to source pages
  4. If the answer is valuable, file it as a new page in wiki/_queries/:
    • YAML frontmatter: title, category: queries, tags, question, date_created
    • The synthesized answer as the body
    • ## Sources listing the pages referenced
  5. Update log.md: - **{timestamp}** | QUERY | "{question}" | filed_as: {path}
  6. Update wiki/_queries/_index.md if a new page was filed

Present the answer with citations.

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