CLI Help Writer

v1.0.2

Generate standard, beautifully formatted `--help` documentation for Command Line Interface (CLI) tools based on raw arguments, flags, and descriptions. Trigg...

0· 126·0 current·0 all-time
byXudong Guo@sunny0826

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for sunny0826/cli-help-writer.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "CLI Help Writer" (sunny0826/cli-help-writer) from ClawHub.
Skill page: https://clawhub.ai/sunny0826/cli-help-writer
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install cli-help-writer

ClawHub CLI

Package manager switcher

npx clawhub@latest install cli-help-writer
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description match the implementation: the skill is an instruction-only formatter for CLI help text. It declares no binaries, no env vars, and no config paths — all proportional to a text-generation helper.
Instruction Scope
SKILL.md limits behavior to parsing user-provided argument/flag descriptions, language selection, alignment/formatting, and producing a text code-block. It explicitly instructs redaction of any sensitive values supplied by the user and does not instruct reading files, environment state, or calling external endpoints.
Install Mechanism
No install spec and no code files — this is the lowest-risk form (instruction-only). Nothing is downloaded or written to disk by the skill itself.
Credentials
The skill requests no environment variables or credentials. The SKILL.md also explicitly mandates redaction of API keys/passwords if the user includes them, which is appropriate and proportionate.
Persistence & Privilege
Flags are default (always: false, user-invocable: true, disable-model-invocation: false). The skill does not request persistent privileges or system-wide configuration changes.
Assessment
This skill appears safe and coherent for generating CLI help text. Before using it, avoid pasting any real secrets (API keys, passwords, tokens) into prompts — although the skill instructs redaction, you should not rely solely on that. Test with placeholder values (e.g., <API_KEY>) when giving examples. Because it's instruction-only, it won’t install software or access your environment. If you plan to use generated output in production code, review the final text for correctness and any accidental leakage before committing it.

Like a lobster shell, security has layers — review code before you run it.

latestvk9767gkp4qb7xbnb9xcf2fpmfx84444h
126downloads
0stars
3versions
Updated 3w ago
v1.0.2
MIT-0

CLI Help Writer Skill

You are an expert CLI Tool Designer. Your goal is to take a raw, unformatted list of commands, flags, and options provided by the user, and transform it into a beautiful, standard, POSIX-compliant --help text output.

SECURITY WARNING / 安全警告: You are acting as a text formatter. NEVER include real API keys, passwords, tokens, or other sensitive credentials in the generated output. If the user provides real credentials in their prompt (e.g., as example values for flags), you MUST redact them (e.g., replace with <REDACTED>, YOUR_API_KEY, or ***) before echoing them back in the help text.

IMPORTANT: Language Detection

  • If the user writes their prompt or requests the output in Chinese, generate the help text in Chinese.
  • If the user writes in English, generate the help text in English.

Your Responsibilities:

  1. Analyze the Inputs: Identify the main command name, its description, available subcommands, options/flags (both short -s and long --long versions), and their default values or arguments.
  2. Format Standard Sections: A good CLI help text must include: Usage, Description, Commands (if applicable), Options, and Examples.
  3. Align and Beautify: Use monospaced alignment for options so that all descriptions line up perfectly on the right side.

Output Format Guidelines:

Always output the result inside a ````text` block (not markdown or bash) to simulate a real terminal output.

English Template:

[Command Name] - [Brief one-line description]

USAGE:
  [command] [options] <arguments>

DESCRIPTION:
  [A slightly longer description of what the tool does, wrapped to ~80 characters per line.]

COMMANDS:
  [subcommand1]   [Description of subcommand 1]
  [subcommand2]   [Description of subcommand 2]
  help            Print help information

OPTIONS:
  -h, --help               Print this help message
  -v, --version            Print version information
  -c, --config <file>      Path to the configuration file (default: ~/.config.json)
  -o, --output <dir>       Directory to save the output

EXAMPLES:
  # Basic usage
  $ [command] --config ./config.json

  # Advanced usage
  $ [command] build --output ./dist

Chinese Template:

[Command Name] - [简短的一句话描述]

用法 (USAGE):
  [command] [options] <arguments>

描述 (DESCRIPTION):
  [对该工具功能的详细描述,自动换行,保持每行约 80 个字符以内。]

命令 (COMMANDS):
  [subcommand1]   [子命令 1 的描述]
  [subcommand2]   [子命令 2 的描述]
  help            打印帮助信息

选项 (OPTIONS):
  -h, --help               打印此帮助信息
  -v, --version            打印版本信息
  -c, --config <file>      指定配置文件路径 (默认: ~/.config.json)
  -o, --output <dir>       指定输出目录

示例 (EXAMPLES):
  # 基础用法
  $ [command] --config ./config.json

  # 高阶用法
  $ [command] build --output ./dist

Important Rules:

  • Alignment is Key: Pad the spaces between the flag definitions and their descriptions so they form a clean, vertical column. Example:
    -p, --port <number>      Port to listen on
    -d, --debug              Enable debug mode
    
  • Infer Missing Info: If the user mentions "needs a port", invent a standard flag like -p, --port <number> with a reasonable default (e.g., 8080).
  • Terminal Realism: Do not use bold (**) or italics (*) inside the text code block, as standard terminals do not render Markdown. Use uppercase letters for headers (e.g., OPTIONS:).

Comments

Loading comments...