axi-check

Validates command-line tools against mechanically checkable AXI conformance rules.

Updated Jul 28, 2026
One-click install
npx skills add https://github.com/vinzenz/workflows --skill axi-check-vinzenz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: axi-check
Source: https://github.com/vinzenz/workflows/tree/main/.agents/skills/axi-check
Command: npx skills add https://github.com/vinzenz/workflows --skill axi-check-vinzenz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agent-facing CLI tools often fail in predictable ways — missing identity headers, wrong exit codes, ANSI color codes, or interactive prompts that hang agents. This Skill automates the mechanical half of the AXI conformance checklist so these failures are caught before a tool is shipped or merged. ## Core Features & Use Cases - Automated conformance checks: Runs 15 checks against a real binary covering --help, --version, home view identity headers (bin:/description:), structured errors on stdout, exit code 2 for unknown commands and flags, and no ANSI output. - Per-command flag validation: With --command, verifies that subcommands handle --help and unknown flags correctly, listing valid flags in errors. - CI integration: Exits 0 on pass, 1 on failure, and 2 on usage errors, with grep-friendly output (search for ",fail,") for pipelines. - Use Case: After building a new agent-facing CLI, run the checker against the compiled binary before marking the task complete, and add it to CI to prevent regressions. ## Quick Start Ask the agent to run axi-check against your built CLI binary, passing --command for each subcommand, and report any failing checks.

Frequently Asked Questions about axi-check

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

FAQPage Schema
How do I check if my CLI tool is agent-friendly?▼

Run axi-check against the built binary, passing the path or a name on PATH. It runs 15 automated checks covering help output, version, home view headers, exit codes, and ANSI-free output, then prints a pass/fail summary.

How to test CLI exit codes for unknown commands and flags?▼

axi-check verifies that unknown commands, leading flags, and unknown flags all exit with code 2 and emit structured error:/code: lines on stdout. Pass --command for each subcommand to enable the per-command flag checks.

What does axi-check not validate?▼

It cannot judge output quality — schema minimality, suggestion usefulness, or truncation limits are section 9.2 items requiring human review. It only enforces the mechanically checkable rules from AXI section 9.1.

Why does axi-check fail home view checks in CI or sandboxes?▼

Tools whose home view needs network access or authentication will fail the home-* checks in restricted environments. Run the checker where the tool can actually operate, or treat those specific results as unknown rather than failures.

Can axi-check hang on interactive CLI tools?▼

No. Every invocation runs with stdin closed and a per-invocation timeout (default 10 seconds, configurable via --timeout), so a tool that prompts for input fails the check instead of hanging.