Creating Cli Tools

Organization

zenobi-us

creating-cli-tools

Design command-line interface parameters and UX: arguments, flags, subcommands, help text, output formats, error messages, exit codes, prompts, config/env precedence, and safe/dry-run behavior. Use when you’re designing a CLI spec (before implementation) or refactoring an existing CLI’s surface area for consistency, composability, and discoverability.

Overview

Publisher	zenobi-us
Repository	`dotfiles`
Skill name	`creating-cli-tools`
Stars	67
Forks	6
Bundled files	2
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
2 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by zenobi-us on GitHub. Read the source before you install it.

Installation

Install the Creating Cli Tools AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/zenobi-us/dotfiles/tree/master/files/devtools/agent/bundles/developer/skills/devtools/creating-cli-tools

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/zenobi-us/dotfiles.git /tmp/dotfiles
mkdir -p .claude/skills
cp -r /tmp/dotfiles/files/devtools/agent/bundles/developer/skills/devtools/creating-cli-tools .claude/skills/creating-cli-tools

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Creating Cli Tools in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Creating Cli Tools on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Creating Cli Tools is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Create CLI

Design CLI surface area (syntax + behavior), human-first, script-friendly.

Do This First

Read agent-scripts/skills/create-cli/references/cli-guidelines.md and apply it as the default rubric.
Upstream/full guidelines: https://clig.dev/ (propose changes: https://github.com/cli-guidelines/cli-guidelines)
Ask only the minimum clarifying questions needed to lock the interface.

Clarify (fast)

Ask, then proceed with best-guess defaults if user is unsure:

Command name + one-sentence purpose.
Primary user: humans, scripts, or both.
Input sources: args vs stdin; files vs URLs; secrets (never via flags).
Output contract: human text, --json, --plain, exit codes.
Interactivity: prompts allowed? need --no-input? confirmations for destructive ops?
Config model: flags/env/config-file; precedence; XDG vs repo-local.
Platform/runtime constraints: macOS/Linux/Windows; single binary vs runtime.

Deliverables (what to output)

When designing a CLI, produce a compact spec the user can implement:

Command tree + USAGE synopsis.
Args/flags table (types, defaults, required/optional, examples).
Subcommand semantics (what each does; idempotence; state changes).
Output rules: stdout vs stderr; TTY detection; --json/--plain; --quiet/--verbose.
Error + exit code map (top failure modes).
Safety rules: --dry-run, confirmations, --force, --no-input.
Config/env rules + precedence (flags > env > project config > user config > system).
Shell completion story (if relevant): install/discoverability; generation command or bundled scripts.
5–10 example invocations (common flows; include piped/stdin examples).

Default Conventions (unless user says otherwise)

-h/--help always shows help and ignores other args.
--version prints version to stdout.
Primary data to stdout; diagnostics/errors to stderr.
Add --json for machine output; consider --plain for stable line-based text.
Prompts only when stdin is a TTY; --no-input disables prompts.
Destructive operations: interactive confirmation + non-interactive requires --force or explicit --confirm=....
Respect NO_COLOR, TERM=dumb; provide --no-color.
Handle Ctrl-C: exit fast; bounded cleanup; be crash-only when possible.

Templates (copy into your answer)

CLI spec skeleton

Fill these sections, drop anything irrelevant:

Name: mycmd
One-liner: ...
USAGE:
- mycmd [global flags] <subcommand> [args]
Subcommands:
- mycmd init ...
- mycmd run ...
Global flags:
- -h, --help
- --version
- -q, --quiet / -v, --verbose (define exactly)
- --json / --plain (if applicable)
I/O contract:
- stdout:
- stderr:
Exit codes:
- 0 success
- 1 generic failure
- 2 invalid usage (parse/validation)
- (add command-specific codes only when actually useful)
Env/config:
- env vars:
- config file path + precedence:
Examples:
- …

Notes

Prefer recommending a parsing library (language-specific) only when asked; otherwise keep this skill language-agnostic.
If the request is “design parameters”, do not drift into implementation.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

references/cli-guidelines.md14 KB
references/styles-bash.md2 KB

Frequently asked questions

What does the Creating Cli Tools AI skill do?

Why use Creating Cli Tools on TypingMind?

Because you install it once and use it with any model. Creating Cli Tools is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Creating Cli Tools in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/zenobi-us/dotfiles/tree/master/files/devtools/agent/bundles/developer/skills/devtools/creating-cli-tools. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Creating Cli Tools?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Creating Cli Tools?

As many as you like. As long as a model supports skills, you can use Creating Cli Tools with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Creating Cli Tools AI skill free?

Yes. It is published on GitHub by zenobi-us under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Improve Codebase Architecture

mattpocock

CommunityPopular

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

Prototype

Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

Research

Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading…

Resolving Merge Conflicts

mattpocock

CommunityPopular

Use when you need to resolve an in-progress git merge/rebase conflict.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Create CLI

Do This First

Clarify (fast)

Deliverables (what to output)

Default Conventions (unless user says otherwise)

Templates (copy into your answer)

CLI spec skeleton

Notes

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now