Skip to content
TrustedSkillsbeta
Back to all skills

Cli Building

Checked
siviter-xyz·vlatest·backend·MIT

Automates command-line interface creation from specifications, streamlining development workflows and reducing repetitive coding tasks.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add siviter-xyz/dot-agent --skill cli-building -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

siviter-xyz

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned siviter-xyz/dot-agent at 33762551d4.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
33762551d4
Manifest
skills/cli-building/SKILL.md
Scanned
6 files, 518 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill, Cli Building, provides guidelines and recommendations for creating command-line interfaces (CLIs) using modern patterns and best practices. It focuses on streamlining development workflows by automating aspects of CLI creation and reducing repetitive coding tasks. The skill offers guidance on framework selection, command architecture, and output formatting to ensure robust and maintainable CLIs. It supports both TypeScript/JavaScript and Python environments.

When to use it

  • Creating new CLI tools or commands from scratch.
  • Adding new commands to existing projects that require a modern CLI approach.
  • Developing interactive terminal applications with complex workflows.
  • Building CLIs where asynchronous operations are central to functionality.
  • When selecting a suitable CLI framework (e.g., stricli, oclif, cyclopts, typer).

Key capabilities

  • Framework recommendations: Provides guidance on choosing appropriate frameworks for TypeScript/JavaScript (stricli, oclif) and Python (cyclopts, typer).
  • Async-first design: Emphasizes asynchronous programming practices to avoid blocking operations.
  • Composable commands: Encourages modularity and reusability through command composition patterns.
  • Strategy pattern implementation: Suggests using the strategy pattern for branching workflows and task-based commands.
  • Output formatting guidelines: Provides rules for clean output, including unicode symbols, color support (respecting NO_COLOR), and avoiding emojis.

Example prompts

  • "Suggest a CLI framework suitable for an async-first Python project."
  • "How can I structure my CLI commands to be more reusable?"
  • "What are the best practices for formatting output in a command-line tool?"
  • “Explain how to use the strategy pattern within a CLI application.”

Tips & gotchas

  • The skill emphasizes an "async-first" approach, so familiarity with asynchronous programming concepts is beneficial.
  • When using TypeScript/JavaScript, stricli is recommended for modern async-first CLIs, while oclif is suitable for more complex projects.
  • Always respect the NO_COLOR environment variable when implementing color support in your CLI output.