How many of the spec's requirements were verified for this tool.
See /coverage for the full matrix.
Level
Total
Verified
Unverified
MUST
28
19
9
SHOULD
21
13
8
MAY
10
10
0
file-traversal Scored as a file-traversal tool: subcommand-shape applicability filters already produce the expected Skip outcomes for fd/find-style tools, so no audits are explicitly suppressed by this profile today.
This is an informational signal, not an authoritative verdict — see methodology. The per-audit evidence below is the ground truth.
Top Issues
FAILStructured-output CLI exposes its schema at runtimeStructured, Parseable OutputCLI emits structured output but exposes no `schema` subcommand or `--schema` flag at top level or nested one level deep. Agents need a runtime-discoverable schema to pin against shape changes.
WARNStructured output supportStructured, Parseable Output--output/--format flag detected but could not validate JSON via safe probes (--help/--version override output flags in most CLIs)
WARNFlags advertise env-var bindings in --helpNon-Interactive by Default63 flag(s) found in --help but no `[env: NAME]` bindings advertised
--output/--format flag detected but could not validate JSON via safe probes (--help/--version override output flags in most CLIs)
FAIL
Structured-output CLI exposes its schema at runtime
CLI emits structured output but exposes no `schema` subcommand or `--schema` flag at top level or nested one level deep. Agents need a runtime-discoverable schema to pin against shape changes.
WARN
--json / --jsonl short aliases for --output
no --json or --jsonl short alias found. Agents and pipelines benefit from short forms alongside the canonical `--output` enum.
WARN
`--raw` flag for pipe-safe unformatted output
no `--raw` flag advertised. MAY-tier — useful for pipelines that want to strip formatting before piping to other tools.
`examples` subcommand or `--examples` flag for curated usage patterns
no `examples` subcommand or `--examples` flag found. MAY-tier — a curated usage block keeps agents from hunting through long help text.
PASS
Short `-h` summary differs from `--help` long form
SKIP
Each subcommand's `--help` ships at least one invocation example
binary has no subcommands; MUST applies conditionally to CLIs that use them.
WARN
Help text pairs human and `--output json` example invocations
no paired text + `--output json` example found within 5 lines in top-level or any subcommand `--help`. Pairing keeps agents from reverse-engineering the JSON invocation from the text one.
pager referenced in --help but no --no-pager escape hatch advertised
PASS
Respects NO_COLOR
SKIP
Subcommand verbs follow community-standard names
no subcommands parsed from --help
PASS
`--color` flag for explicit color control
SKIP
Input-accepting commands read from stdin when no file is given
no input-accepting subcommand detected (process/parse/convert/transform/analyze/validate/format/lint/audit); vacuous skip for the conditional SHOULD.
SKIP
Subcommand naming follows a consistent verb/noun convention
fewer than 2 user-defined subcommands; vacuous skip for the conditional SHOULD.
WARN
Operations are subcommands, not verb-shaped flags
top-level verb-shaped flag(s) found: --exec. Operations belong under the `Commands:` block (`tool search "q"`), not on the flag namespace where they fight the `--help` filtering agents rely on.
