CreateCLI

Generate TypeScript CLI scaffolds with llcli-style templates and documentation.

186|24|Updated Jan 1, 2026
One-click install
npx skills add https://github.com/Steffen025/pai-opencode --skill createcli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: CreateCLI
Source: https://github.com/Steffen025/pai-opencode/tree/main/.opencode/skills/CreateCLI
Command: npx skills add https://github.com/Steffen025/pai-opencode --skill createcli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of production-ready TypeScript CLIs, eliminating boilerplate and enabling teams to wrap APIs, automate tasks, and deliver reliable command-line tools with consistent structure and documentation.

Core Features & Use Cases

  • LLCLI-based generation: Produces type-safe CLI skeletons in Bun + TypeScript with deterministic JSON output.
  • Comprehensive docs: Includes README, QUICKSTART, and example usage to accelerate adoption.
  • Tier guidance: Default to Tier 1 (llcli pattern); escalation paths to Tier 2 (Commander.js) or Tier 3 (documentation) when complexity grows.
  • Use Cases: Wraps an API (e.g., GitHub API), automate data tasks, or create internal CLIs for tooling.

Quick Start

Use the CreateCLI skill to generate a complete CLI scaffold from your requirements. After activation, CLIs are created under the OpenCode workspace (e.g., ~/.opencode/Bin/[cli-name]/) with source, documentation, and setup scripts ready to run.

Frequently Asked Questions about CreateCLI

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

FAQPage Schema
How do I generate a production-ready TypeScript CLI?

You can generate a production-ready TypeScript CLI by applying llcli-style templates that output type-safe skeletons with deterministic JSON output, structured error handling, and comprehensive documentation like README and QUICKSTART files.

What is llcli-style architecture for command-line tools?

LLCLI-style architecture is a CLI-First pattern that produces type-safe Bun and TypeScript skeletons with deterministic JSON output, defaulting to a Tier 1 structure before escalating to Commander.js or advanced documentation as complexity grows.

How do I structure error handling in a TypeScript CLI generator?

Error handling is structured automatically by enforcing type safety and deterministic JSON output across CLI scenarios, with escalation rules that elevate patterns to Tier 2 Commander.js or Tier 3 documentation as complexity grows.

When should I escalate my CLI pattern to Commander.js?

You should escalate to Tier 2 Commander.js patterns when your CLI complexity grows beyond the default Tier 1 llcli structure, ensuring your command-line tool maintains type safety and robust architecture at scale.

Can I automate internal tooling tasks using a TypeScript CLI?

Yes, you can automate data tasks and create internal tooling CLIs by generating scaffolds that include source code, setup scripts, and example usage, accelerating adoption for automation workflows.