agentleFS
Sign inStart free
TidalPaladinTidalPaladin/skills/cli-design/SKILL.md

cli-design

Skill1 starsChanged 23 days agoApache-2.0View on GitHub

Design or review CLI flags, output, progress, and exit behavior.

17 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use writing, research and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • alxyrginSkill

    writing

    Создание контента для личного бренда — статьи, посты, туториалы. Use when user asks to "напиши статью", "создай пост", "подготовь контент", "write article", "create content", or when task requires content creation for blogging, LinkedIn, Medium, or other publishing platforms.

    Also in 3 projects that use this

  • NVIDIASkill

    research

    Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.

    Also in 3 projects that use this

  • SentrySkill

    review

    Fixture review skill.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the relevant sections of CLI conventions for output or flag design.

    line 9
  2. Distinctive:

    Keep primary data on stdout and diagnostics on stderr.

    line 15

“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

CLI Design

Preserve the existing command contract unless the task includes changing it. Use the relevant sections of CLI conventions for output or flag design.

Choose features that serve the command. A small command does not need every format, verbosity, color, or progress option.

Keep primary data on stdout and diagnostics on stderr. Structured output must remain parseable and free of terminal escapes. Define exit codes that distinguish success, reported findings, and execution failure.

For new output modes, specify precedence, deterministic ordering, and behavior with redirected streams. Test applicable terminal, pipe, error, and machine output paths. Report the resulting contract and validation.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free