# CLI Craftsman

> Paste your --help output and get a concrete rewrite with reasons. Use when the user suspects their help text confuses people or wants a fast second opinion on it.

- Skill: `garphengate/cli-craftsman` (Agent Skill)
- Install (CLI): `npx skillmds@latest add garphengate/cli-craftsman`
- Raw SKILL.md: https://api.skillmd.com/api/skills/garphengate/cli-craftsman/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: GarphenGate (https://skillmd.com/u/garphengate)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/garphengate/cli-craftsman

---


# Help Text Reviewer

*Free gateway skill from the CLI Craftsman bundle by GarphenGate.*

One paste, one review, one rewrite. The full Help Text Writer builds from scratch; this takes what exists and returns the improved version with every change justified.

## Procedure

1. **Take the paste** of the current --help output, plus (optional but valuable) one sentence on what the tool does and who uses it.
2. **Score it against the five checks:** summary line answers 'is this the tool I need'; a copy-pasteable example appears in the first ten lines; options show defaults; error-prone flags are explained, not just named; total length fits one screen.
3. **Write the rewrite,** preserving the tool's actual flags and behavior exactly as described; where the paste is ambiguous about behavior, keep the original wording and mark the ambiguity rather than inventing semantics.
4. **Deliver both parts** in the format below: the rewrite ready to use, then the change log with a one-line reason per change so the user learns the pattern, not just the fix.

```
HELP TEXT REVIEW
Score: <n>/5 - <failed checks named>
--- REWRITE ---
<the improved help text, complete>
--- CHANGES ---
1. <what changed> - <why, one line>
Ambiguities kept as-is: <list, with the question to resolve each - or 'none'>
```

## Rules

- Never invent flags, defaults, or behaviors not present in the paste; ambiguity is marked, not filled.
- Never return criticism without the rewrite; the rewrite is the review.
- Keep the rewrite within one screen (about 25 lines); if the original cannot fit, the review says what moves to subcommand help.

## Degradation

If the paste is a fragment or the tool's purpose is unstated, review what is present, mark the summary line as provisional, and list the two questions whose answers would complete the rewrite.


---

*Like this? This is the free gateway skill for **CLI Craftsman** by Moltline Studio. The paid listing: https://www.agensi.io/skills/cli-craftsman-bundle*