CLI Cheatsheet Builder

What this skill does

Calls a CLI tool's help output recursively (top level and each subcommand), parses the result, and produces a one-page markdown cheatsheet listing the 80% common invocations grouped by intent.

Inputs

• tool_name: the CLI to introspect, available on $PATH.
• Optional subcommand_depth: how many subcommand levels to descend (default 2).
• Optional out_path: defaults to cheatsheets/<tool>.md.

Steps

1. Run <tool_name> --help (fall back to -h if --help errors) and capture the output.
2. Parse the help block: identify Usage:, the global flags list, and a Commands: / Subcommands: table.
3. For each subcommand listed, recurse: <tool_name> <subcmd> --help. Limit recursion to subcommand_depth.
4. For each flag entry, capture: short form, long form, value placeholder, default, one-line description.
5. Bucket flags by intent based on description keywords: auth, output-format, filter, dry-run-or-confirm, verbosity, concurrency, paths. Keep an other bucket.
6. For each subcommand, pick the three most likely "common case" invocations: a bare invocation, an invocation with the most-used filter flag, and one with --output json or equivalent.
7. Render a markdown page with: a header citing the tool version (<tool_name> --version), an H2 per subcommand, three example invocations, and a flag-table grouped by bucket.
8. Append a "Tips" section with 3 bullets (e.g., shell completion install, common env vars).
9. Write to out_path.

Output

cheatsheets/<tool>.md containing the captured tool version, command examples in fenced bash blocks, and grouped flag tables. Print the path and total subcommand count to stdout.

Verification

Re-run the example invocations in --help mode (e.g., append --help to each) and confirm none produce a "no such command" error. Diff the listed flags against <tool_name> <subcmd> --help raw output and confirm the cheatsheet contains each flag at least once. If the tool's --version errors, omit the version header rather than fabricate.

Edge cases

• Tool with no --help flag: try man <tool_name> as fallback; document the source in the header.
• Tool that emits help on stderr instead of stdout: capture both with 2>&1.
• Interactive subcommand requiring TTY: skip and note in "Not Documented" appendix.
• Tool localized to a non-English help: process anyway but tag the file with the detected language code.