Token导航 LogoToken导航

Agent Skill · 前端设计

system-create-cli（系统 create CLI）

system-create-cli 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息，适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态，以及是否会触发联网、命令执行或文件读写。

system-create-cli 是前端设计类 Agent Skill，可用宿主为 Codex、Claude、Cursor、Gemini CLI，通过GitHub 仓库获取，权限为执行命令；许可证信息还不明确，第三方扫描已通过，按安装量在前端设计类的 10,216 个 Skill 里排第 6,853。

总安装 447周安装 19GitHub Stars 2下载 157核验 2026-05-01
前端设计执行命令GitHub 仓库未标认证来源可访问许可证需确认审计通过CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明，不托管安装包，也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手，先确认命令和权限，再让它执行。

请帮我安装这个 Agent Skill：system-create-cli（系统 create CLI）
来源仓库：https://github.com/multicam/qara
仓库路径：skills/system-create-cli
安装命令：
npx skills add https://github.com/multicam/qara --skill system-create-cli
安装前请先检查当前环境是否支持对应 CLI，并向我确认将要执行的命令、安装目录、联网范围和文件读写权限；确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill；本站只展示命令，不托管安装包，也不自动执行。

skills.shnpx skills
npx skills add https://github.com/multicam/qara --skill system-create-cli

这个 Skill 是做什么的

前端设计类 Skill 关注页面结构、视觉规范和组件写法，输出通常是可运行的界面代码。

system-create-cli 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息，适合在 Codex、Claude、Cursor、Gemini CLI 中围绕仓库状态、代码变更或协作事项进行整理时使用。适用于 CLI 工具开发与协作流程管理，可结合原始 README 验证功能细节。

通过 npx skills add 命令从指定 GitHub 仓库安装，需确认权限范围和维护状态。安装前建议确认是否会触发联网、命令执行或文件读写等操作。适用宿主包括 Codex、Claude、Cursor、Gemini CLI，接入前应确认版本、权限和运行环境要求。

来源仓库内路径：skills/system-create-cli

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI；先确认自己用的是其中之一，再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/multicam/qara --skill system-create-cli；命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开，让新装的 Skill 被重新扫描到，否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要执行命令，先在测试目录或测试账号里跑，确认没问题再放到正式项目。

常见问题

6 条

system-create-cli 怎么安装？

在终端执行 npx skills add https://github.com/multicam/qara --skill system-create-cli。装完完全退出宿主工具再打开，让它重新扫描本地 Skill。

system-create-cli 支持哪些 AI 工具？

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录，一般也能手动放进去，但要自己确认触发方式是否一致。

system-create-cli 需要什么权限？

权限级别是执行命令。安装流程涉及命令执行，可能通过 npx skills add https://github.com/multicam/qara --skill system-create-cli 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

system-create-cli 是免费的吗？

公开资料没有标注明确许可证，收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

system-create-cli 用的人多吗？

公开数据是累计安装 447 次，近一周安装 19 次，下载 157 次，GitHub 2 星。这些数字来自第三方目录统计，只能当作热度参考，不代表质量或安全性。

system-create-cli 安全吗？

第三方扫描结果为通过，但这只覆盖已知的静态检查项，不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具，换客户端不用重新找替代品。
  • 第三方扫描已通过，常见的高风险行为没有命中。

先想清楚的地方

  • 需要执行命令，装到常用环境前要先评估影响面。
  • 许可证没有明确标注，能不能商用、能不能再分发都不确定。
  • 第三方目录整理，版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex，想直接扩展它能力的人。
  • 需要处理前端设计类任务、又不想每次都手写提示词的人。

不太适合

  • 不能接受 Skill 在你机器上执行命令的人。
  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

前端设计类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
frontend-design

前端设计 · Codex、Claude

8,823,360126,072只读MIT通过
vercel-composition-patterns

Vercel 组合模式 · Codex、Claude

3,858,81625,893需要联网MIT通过
vercel-react-native-skills

Vercel React native skills 前端 · Codex、Claude

2,468,66425,878只读MIT通过
adapt

adapt 搜索 · Codex、Claude

2,027,04023,125操作浏览器未明确通过
bolder

bolder 分析 · Codex、Claude

2,004,28823,130只读未明确通过
system-create-cli

系统 create CLI · 本页

4472执行命令未明确通过

按安装量取同分类前几名；数字来自第三方目录统计，只作热度参考，不代表质量结论。

SKILL.md 原文

system-create-cli

Automated CLI Generation System

Generate production-ready TypeScript CLIs with comprehensive documentation, type safety, error handling, and PAI's CLI-First Architecture principles.

WORKFLOW ROUTING (SYSTEM PROMPT)

When user requests CLI creation, follow this routing:

Primary Workflow: Create New CLI

Triggers: "create CLI", "build command-line tool", "make CLI for X", "generate CLI" Route to: workflows/create-cli.md Action: Generate complete CLI from requirements

Extension Workflow: Add Command

Triggers: "add command to CLI", "extend CLI with", "add feature to existing CLI" Route to: workflows/add-command.md Action: Add new command to existing CLI

Migration Workflow: Upgrade Complexity Tier

Triggers: "upgrade CLI", "migrate to Commander", "CLI needs more complexity" Route to: workflows/upgrade-tier.md Action: Migrate Tier 1 → Tier 2 (manual → Commander.js)

Testing Workflow: Add Test Suite

Triggers: "add tests to CLI", "test scaffolding", "need CLI tests" Route to: workflows/add-testing.md Action: Generate comprehensive test suite

Distribution Workflow: Setup Publishing

Triggers: "publish CLI", "distribute CLI", "make standalone binary" Route to: workflows/setup-distribution.md Action: Configure npm publishing or binary distribution

WHEN TO ACTIVATE THIS SKILL

Activate when you see these patterns:

Direct Requests

  • "Create a CLI for [API/service/tool]"
  • "Build a command-line interface for X"
  • "Make a CLI that does Y"
  • "Generate a TypeScript CLI"
  • "I need a CLI tool for Z"

Context Clues

  • User describes repetitive API calls → Suggest CLI
  • User mentions "I keep typing this command" → Suggest CLI wrapper
  • User has bash script doing complex work → Suggest TypeScript CLI replacement
  • User working with API that lacks official CLI → Suggest creating one

Examples

  • ✅ "Create a CLI for the GitHub API"
  • ✅ "Build a command-line tool to process CSV files"
  • ✅ "Make a CLI for my database migrations"
  • ✅ "Generate a CLI that wraps this API"
  • ✅ "I need a tool like llcli but for Notion API"

CORE CAPABILITIES

Three-Tier Template System

Tier 1: llcli-Style (DEFAULT - 80% of use cases)

  • Manual argument parsing (process.argv)
  • Zero framework dependencies
  • Bun + TypeScript
  • Type-safe interfaces
  • ~300-400 lines total
  • Perfect for: API clients, data transformers, simple automation

When to use Tier 1:

  • ✅ 2-10 commands
  • ✅ Simple arguments (flags, values)
  • ✅ JSON output
  • ✅ No subcommands
  • ✅ Fast development

Tier 2: Commander.js (ESCALATION - 15% of use cases)

  • Framework-based parsing
  • Subcommands + nested options
  • Auto-generated help
  • Plugin-ready
  • Perfect for: Complex multi-command tools

When to use Tier 2:

  • ❌ 10+ commands needing grouping
  • ❌ Complex nested options
  • ❌ Plugin architecture
  • ❌ Multiple output formats

Tier 3: oclif (REFERENCE ONLY - 5% of use cases)

  • Documentation only (no templates)
  • Enterprise-grade plugin systems
  • Perfect for: Heroku CLI, Salesforce CLI scale (rare)

READ: references/tier-comparison.md for detailed framework comparison, performance metrics, and migration paths

What Every Generated CLI Includes

1. Complete Implementation

  • TypeScript source with full type safety
  • All commands functional and tested
  • Error handling with proper exit codes
  • Configuration management

2. Comprehensive Documentation

  • README.md with philosophy, usage, examples
  • QUICKSTART.md for common patterns
  • Inline help text (--help)
  • API response documentation

3. Development Setup

  • package.json (Bun configuration)
  • tsconfig.json (strict mode)
  • .env.example (configuration template)
  • File permissions configured

4. Quality Standards

  • Type-safe throughout
  • Deterministic output (JSON)
  • Composable (pipes to jq, grep)
  • Error messages with context
  • Exit code compliance

INTEGRATION WITH QARA

Technology Stack Alignment

Generated CLIs follow PAI's standards:

  • ✅ Runtime: Bun (NOT Node.js)
  • ✅ Language: TypeScript (NOT JavaScript or Python)
  • ✅ Package Manager: Bun (NOT npm/yarn/pnpm)
  • ✅ Testing: bun test (when tests added)
  • ✅ Output: Deterministic JSON (composable)
  • ✅ Documentation: README + QUICKSTART (llcli pattern)

Repository Placement

Generated CLIs go to:

  • ${PAI_DIR}/bin/[cli-name]/ - Personal CLIs (like llcli)
  • ~/Projects/[project-name]/ - Project-specific CLIs
  • ~/Projects/PAI/examples/clis/ - Example CLIs (PUBLIC repo)

SAFETY: Always verify repository location before git operations

CLI-First Architecture Principles

Every generated CLI follows:

  1. Deterministic - Same input → Same output
  2. Clean - Single responsibility
  3. Composable - JSON output pipes to other tools
  4. Documented - Comprehensive help and examples
  5. Testable - Predictable behavior

EXTENDED CONTEXT

For detailed information, read these files:

Workflow Documentation

  • workflows/create-cli.md - Main CLI generation workflow (decision tree, 10-step process)
  • workflows/add-command.md - Add commands to existing CLIs
  • workflows/upgrade-tier.md - Migrate simple → complex
  • workflows/add-testing.md - Test suite generation
  • workflows/setup-distribution.md - Publishing configuration

Reference Documentation

READ: references/tier-comparison.md for comprehensive framework comparison including:

  • Detailed feature comparison (Tier 1 vs 2 vs 3)
  • Performance metrics (startup time, memory usage)
  • Migration paths between tiers
  • Decision algorithm for tier selection
  • Real-world examples and recommendations

READ: references/cli-examples-basic.md and references/cli-examples-advanced.md for 6 complete examples covering:

  • API clients (GitHub, Notion)
  • File processors (markdown, CSV)
  • Data pipelines (complex workflows)
  • Database operations (PostgreSQL)
  • Common patterns and testing approaches
  • Documentation templates

PHILOSOPHY

Why This Skill Exists

User repeatedly creates CLIs for APIs and tools. Each time:

  1. Starts with bash script
  2. Realizes it needs error handling
  3. Realizes it needs help text
  4. Realizes it needs type safety
  5. Rewrites in TypeScript
  6. Adds documentation
  7. Now has production CLI

This skill automates steps 1-7.

The llcli Pattern

The llcli CLI (Limitless.ai API) proves this pattern works:

  • 327 lines of TypeScript
  • Zero dependencies (no framework)
  • Complete error handling
  • Comprehensive documentation
  • Production-ready immediately

This skill replicates that success.

Design Principles

  1. Start Simple - Default to Tier 1 (llcli-style)
  2. Escalate When Needed - Tier 2 only when justified
  3. Complete, Not Scaffold - Every CLI is production-ready
  4. Documentation First - README explains "why" not just "how"
  5. Type Safety - TypeScript strict mode always

QUALITY STANDARDS

Every generated CLI must pass these gates:

1. Compilation

  • ✅ TypeScript compiles with zero errors
  • ✅ Strict mode enabled
  • ✅ No any types except justified

2. Functionality

  • ✅ All commands work as specified
  • ✅ Error handling comprehensive
  • ✅ Exit codes correct (0 success, 1 error)

3. Documentation

  • ✅ README explains philosophy and usage
  • ✅ QUICKSTART has common examples
  • ✅ --help text comprehensive
  • ✅ All flags/options documented

4. Code Quality

  • ✅ Type-safe throughout
  • ✅ Clean function separation
  • ✅ Error messages actionable
  • ✅ Configuration externalized

5. Integration

  • ✅ Follows PAI tech stack (Bun, TypeScript)
  • ✅ CLI-First Architecture principles
  • ✅ Deterministic output (JSON)
  • ✅ Composable with other tools

This skill turns "I need a CLI for X" into production-ready tools in minutes, following proven patterns from llcli and PAI's CLI-First Architecture.

平台分布

Codex

33.31%
按下载量换算52

Claude

30.62%
按下载量换算48

Cursor

18.24%
按下载量换算29

Gemini CLI

10.1%
按下载量换算16

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

执行命令

安装流程涉及命令执行，可能通过 npx skills add https://github.com/multicam/qara --skill system-create-cli 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

安装前确认

本站仅展示第三方公开信息，不托管安装包，不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源，建议同时核对源仓库。

继续浏览同类 Skills

更多前端设计 Skills（10,216）返回 Skills 目录

上一个 Skill

system-architecture（系统架构）

hieutrtr/ai1-skills

system-architecture 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息，适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态，以及是否会触发联网、命令执行或文件读写。

下一个 Skill

system-deconstruction（系统解构）

dragoon0x/taste-skills

system-deconstruction 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息，适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态，以及是否会触发联网、命令执行或文件读写。