query

Query the Dojo registry to resolve needs, search nodes, and fetch skill bundles.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/theslashdojo/dojo --skill query-theslashdojo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: query
Source: https://github.com/theslashdojo/dojo/tree/main/nodes/dojo/api/query
Command: npx skills add https://github.com/theslashdojo/dojo --skill query-theslashdojo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The skill provides a single, consistent client to query the Dojo registry so agents and tooling can resolve a need, search nodes, inspect graph context, and fetch portable skill bundles without hard-coding route logic.

Core Features & Use Cases

  • Unified Operation Surface: Supports discover, resolve, search, skill, learn, tree, graph, backlinks, alias, bundle, agent_ask, and agent_learn operations.
  • Agent & CLI Friendly: Works as both a JavaScript import and a CLI helper with structured JSON input, argument parsing, and clear error messages.
  • Use Case: An agent uses discover to decide learn-versus-do, then calls bundle to retrieve the SKILL.md, scripts, and tests needed to run or port a skill.

Quick Start

Call the query helper with an operation (for example discover, resolve, or bundle) and provide the relevant parameters such as q, uri, or current_context to retrieve registry results.

Frequently Asked Questions about query

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I discover and fetch skill bundles from a registry using natural language?

To discover and fetch skill bundles from a registry, you can query the Dojo registry using natural-language needs. The query operation resolves your request, searches nodes, and retrieves bundled packages containing scripts and tests without hard-coding route logic.

What is the best way to search a skill registry and inspect graph context for agents?

The best way to search a skill registry and inspect graph context is to use a unified client that supports discover, resolve, and tree operations. This allows agents to inspect backlinks and aliases while returning structured JSON responses.

Can I use a CLI helper to resolve registry nodes and export skill packages?

Yes, you can use a CLI helper to resolve registry nodes and export skill packages. The query client works as both a JavaScript import and a CLI tool, accepting structured JSON inputs and providing clear error messages for argument parsing.

Does the registry query client support HTTP read and agent POST shapes?

Yes, the registry query client supports both HTTP read and agent POST shapes. It processes structured inputs like operation, uri, q, tags, mode, and current_context, returning the status, method, url, and parsed JSON responses.

How do agents decide whether to learn a skill or execute it directly from a registry?

Agents decide whether to learn or execute by using the discover operation against the registry. This queries the Dojo registry to resolve natural-language needs, allowing the agent to evaluate the context before calling bundle to retrieve the necessary SKILL.md and scripts.