system-createcli

Generate Bun-compatible TypeScript CLIs with templates and validation gates.

9|1|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/CarbeneAI/Forge --skill system-createcli-carbeneai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: system-createcli
Source: https://github.com/CarbeneAI/Forge/tree/main/.claude/skills/CreateCLI
Command: npx skills add https://github.com/CarbeneAI/Forge --skill system-createcli-carbeneai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of production-ready TypeScript command-line interfaces so developers stop writing brittle shell scripts and ad-hoc CLIs and instead get deterministic, documented, and testable tools.

Core Features & Use Cases

  • Three-Tier Templates: Default llcli manual parsing for minimal CLIs, Commander.js escalation for organized subcommands, and oclif referenced for enterprise plugin systems.
  • Production-Grade Output: Generates Bun-compatible TypeScript, strict tsconfig, package.json, .env.example, comprehensive README and QUICKSTART, and test scaffolding.
  • Quality & Safety Gates: Built-in checks for TypeScript compilation, help text, error handling patterns, signal handling, and distribution workflows.
  • Use Cases: Ideal for API client CLIs, file processors, data transformers, automation wrappers, and for incrementally adding commands or upgrading complexity.

Quick Start

Use the system-createcli skill to generate a TypeScript CLI named ghcli that lists GitHub repositories and prints JSON output.

Frequently Asked Questions about system-createcli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a production-ready TypeScript CLI without writing brittle shell scripts?

Generate a production-ready TypeScript CLI by using a scaffolding system that outputs Bun-compatible TypeScript with strict tsconfig, package.json, .env configuration, comprehensive README, and test scaffolding. This replaces ad-hoc shell scripts with deterministic, documented, and testable command-line tools.

What is the best way to structure a TypeScript CLI when it needs to scale from manual parsing to subcommands?

The best way to scale a TypeScript CLI is using a tiered template approach. Start with manual parsing for minimal CLIs, escalate to Commander.js for organized subcommands, and reference oclif for enterprise plugin systems, ensuring you only add complexity as needed.

Does this CLI generator support Bun and strict TypeScript configurations?

Yes, this CLI generator supports Bun and strict TypeScript configurations. It produces Bun-compatible TypeScript code along with a strict tsconfig, ensuring type safety and deterministic execution for API clients, file processors, and data transformers.

What quality gates are included when creating a TypeScript command-line interface?

Quality gates included when creating a TypeScript command-line interface are built-in checks for TypeScript compilation, help text generation, error handling patterns, signal handling, and distribution workflows, ensuring the resulting CLI is production-grade and safe to distribute.

Can I use this to create a CLI for an API client that outputs JSON?

Yes, you can create a CLI for an API client that outputs JSON. The generator is ideal for building API client CLIs, file processors, data transformers, and automation wrappers, providing type-safe structures for handling and formatting API responses.

When should I not use manual parsing for a TypeScript command-line interface?

You should not use manual parsing for a TypeScript command-line interface when your tool requires organized subcommands or enterprise plugin systems. Instead, escalate to the Commander.js template for subcommands or reference the oclif template for complex plugin architectures.