Documentation Index
Fetch the complete documentation index at: https://mintlify.com/modiqo/skillspec/llms.txt
Use this file to discover all available pages before exploring further.
skillspec sensemake reads a skill.spec.yml file and returns a structured map of the spec’s collections and handles without dumping the entire YAML into the context. It is the recommended first step before running decide, query, or refs because it reveals what routes, rules, commands, phases, and tests the spec contains at whatever detail level the agent or user needs.
The default --view index output is compact and safe for repeated use inside a run. It intentionally hides exhaustive handle lists — move to --view summary or --view full only when you need exact identifiers.
Synopsis
skillspec sensemake <path> [--view index|summary|full] [--json]
Options
| Flag | Type | Default | Description |
|---|
<path> | path | (required) | Path to a skill.spec.yml file. |
--view | index | summary | full | index | Detail level. index is compact and hides exhaustive handle lists. summary shows collection members. full shows exact item content. |
--json | flag | off | Emit machine-readable JSON instead of a concise human report. |
Examples
Print a compact spec map before routing a task:
skillspec sensemake ./skill.spec.yml --view index
Inspect collection members when you need specific handles:
skillspec sensemake ./skill.spec.yml --view summary
Emit JSON so the agent can parse collection names and counts programmatically:
skillspec sensemake ./skill.spec.yml --view index --json
skillspec query retrieves one collection, item, or field path from the spec using a handle string. Use handles produced by sensemake to drill progressively into the spec rather than re-reading the full YAML.
Synopsis
skillspec query <path> <handle> [--view index|summary|full] [--json]
Options
| Flag | Type | Default | Description |
|---|
<path> | path | (required) | Path to a skill.spec.yml file. |
<handle> | string | (required) | A collection name (e.g. routes) or an item path (e.g. command:validate_spec.requires, test:browse_selects_browser.expect). |
--view | index | summary | full | summary | Detail level to use for the query result. |
--json | flag | off | Emit JSON instead of a concise human report. |
Examples
List the routes collection at summary depth:
skillspec query ./skill.spec.yml routes --view summary
Inspect the requirements declared for a specific command:
skillspec query ./skill.spec.yml command:validate_spec.requires --view summary
Read the full content of a test’s expected outcome:
skillspec query ./skill.spec.yml test:browse_selects_browser.expect --view full --json
skillspec refs shows outgoing references for an item handle — for example, a rule’s preferred route, a route’s checks, a command’s dependencies, or a test’s expected route and rules. Use it to understand the dependency graph of a spec item before running decide or act.
Synopsis
skillspec refs <path> <handle> [--view index|summary|full] [--json]
Options
| Flag | Type | Default | Description |
|---|
<path> | path | (required) | Path to a skill.spec.yml file. |
<handle> | string | (required) | Item handle, such as rule:<id>, command:<id>, state:<id>, recipe:<id>, or test:<name>. |
--view | index | summary | full | summary | Detail level for the reference output. |
--json | flag | off | Emit JSON instead of a concise human report. |
Examples
See what a routing rule refers to:
skillspec refs ./skill.spec.yml rule:browser_tasks_use_browser
Inspect a test’s expected route, rules, and elicitations:
skillspec refs ./skill.spec.yml test:browse_selects_browser --view summary
Emit JSON for a command’s full reference graph:
skillspec refs ./skill.spec.yml command:validate_spec --view full --json