Skip to content
Agentmart
Submit a tool

cli-design

Design or refine stable Typer commands, flags, help text, and Rich output for the media-report CLI.

Skill by smaje99

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/smaje99-cli-design

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Design or refine stable Typer commands, flags, help text, and Rich output for the media-report CLI. Use when adding commands, changing options or defaults, or improving user-facing errors and CLI behavior.

Use cases: documents, design

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/cli-design

What's inside

Skill name
cli-design
Description
Design or refine stable Typer commands, flags, help text, and Rich output for the media-report CLI. Use when adding commands, changing options or defaults, or improving user-facing errors and CLI behavior.
License
MIT
Instructions
32 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# CLI Design

## Goal

Design stable, explicit Typer commands and Rich-driven output for `media-report`.

## When To Use

- Adding a command
- Changing flags or defaults
- Improving help text or error messages

## Steps

1. Start from the user task and resulting artifacts.
2. Keep command names and options explicit.
3. Decide which output is for humans and which is persisted as artifacts.
4. Validate failure messages for actionable guidance.
5. Add integration coverage for public behavior.

## Checklist

- Help output is readable
- Defaults are documented
- Errors map to non-zero exits
- New flags are additive unless documented otherwise

## Exit Criteria

The command is discoverable, stable, and covered by integration tests.

From smaje99/orgdoc, MIT.

More from smaje99/orgdoc

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Jun 12, 2026 (4 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from smaje99

Cite this page

cli-design skill. Agent Mart. https://agentmart.dev/skills/smaje99-cli-design (last updated 2026-10-24)