cli-design — for Claude Code cli-design, pylon-sync, community, for Claude Code, ide skills, obsidian, obsidian-plugin, obsidian-sync, output json, version

v1.0.0
GitHub

Об этом навыке

Подходящий сценарий: Ideal for AI agents that need build command-line tools that feel solid, communicate clearly, and compose well with the unix. Локализованное описание: Sync files to GitHub and S3-compatible storage via REST API — no git binary required. It covers obsidian, obsidian-plugin, obsidian-sync workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

Возможности

Build command-line tools that feel solid, communicate clearly, and compose well with the Unix
Creating a new CLI tool or adding subcommands
Designing output format (human, JSON, LLM)
Implementing error handling and exit codes
Adding authentication, configuration, or plugin systems

# Core Topics

for Claude Code obsidian obsidian-plugin obsidian-sync output json version
magarcia magarcia
[0]
[0]
Updated: 4/9/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 10/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Quality floor passed for review
Review Score
10/11
Quality Score
60
Canonical Locale
en
Detected Body Locale
en

Подходящий сценарий: Ideal for AI agents that need build command-line tools that feel solid, communicate clearly, and compose well with the unix. Локализованное описание: Sync files to GitHub and S3-compatible storage via REST API — no git binary required. It covers obsidian, obsidian-plugin, obsidian-sync workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

Зачем использовать этот навык

Рекомендация: cli-design helps agents build command-line tools that feel solid, communicate clearly, and compose well with the unix. Sync files to GitHub and S3-compatible storage via REST API — no git binary required.

Подходит лучше всего

Подходящий сценарий: Ideal for AI agents that need build command-line tools that feel solid, communicate clearly, and compose well with the unix.

↓ Реализуемые кейсы использования for cli-design

Сценарий использования: Applying Build command-line tools that feel solid, communicate clearly, and compose well with the Unix
Сценарий использования: Applying Creating a new CLI tool or adding subcommands
Сценарий использования: Applying Designing output format (human, JSON, LLM)

! Безопасность и ограничения

  • Ограничение: Requires repository-specific context from the skill documentation
  • Ограничение: Works best when the underlying tools and dependencies are already configured

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team handoff, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is cli-design?

Подходящий сценарий: Ideal for AI agents that need build command-line tools that feel solid, communicate clearly, and compose well with the unix. Локализованное описание: Sync files to GitHub and S3-compatible storage via REST API — no git binary required. It covers obsidian, obsidian-plugin, obsidian-sync workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

How do I install cli-design?

Run the command: npx killer-skills add magarcia/pylon-sync/cli-design. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for cli-design?

Key use cases include: Сценарий использования: Applying Build command-line tools that feel solid, communicate clearly, and compose well with the Unix, Сценарий использования: Applying Creating a new CLI tool or adding subcommands, Сценарий использования: Applying Designing output format (human, JSON, LLM).

Which IDEs are compatible with cli-design?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for cli-design?

Ограничение: Requires repository-specific context from the skill documentation. Ограничение: Works best when the underlying tools and dependencies are already configured.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add magarcia/pylon-sync/cli-design. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use cli-design immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

cli-design

Install cli-design, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

CLI Design

Build command-line tools that feel solid, communicate clearly, and compose well with the Unix ecosystem.

When to use

  • Creating a new CLI tool or adding subcommands
  • Designing output format (human, JSON, LLM)
  • Implementing error handling and exit codes
  • Adding authentication, configuration, or plugin systems
  • Reviewing CLI code for usability issues

Core philosophy

  1. Human-first, machine-compatible -- design for humans, then ensure machines can consume output
  2. Conversation, not interrogation -- each invocation is a turn in a dialogue; suggest corrections, show next steps
  3. Consistency over novelty -- follow conventions (--help, -v, --output json, exit codes)
  4. Say just enough -- concise by default, verbose via flags
  5. Robustness as a feeling -- fast startup, clear feedback, no hanging, no cryptic stack traces

Rule index

Rules are organized by domain and impact. See the linked reference for full details with examples.

#DomainRuleImpactReference
1CommandUse tool <noun> <verb> [flags] for multi-resource CLIsCRITICALcommand-structure
2CommandKeep subcommand nesting to 2 levels maxHIGHcommand-structure
3CommandPrefer flags over positional args (self-documenting, order-independent)HIGHcommand-structure
4CommandEvery flag has a long form; common ones also get a short formMEDIUMcommand-structure
5CommandSupport global flags: --help, --version, --verbose, --output, --no-color, --quietCRITICALcommand-structure
6OutputDetect TTY -- adapt output to terminal vs pipeCRITICALoutput-design
7Outputstdout for data, stderr for messages/progress/errorsCRITICALoutput-design
8OutputSupport --output json with stable schemaCRITICALoutput-design
9OutputSupport --output llm for agent-friendly consumptionHIGHoutput-design
10OutputUse color for scannability, not decoration; respect NO_COLORMEDIUMoutput-design
11OutputShow spinners/progress for long operations on stderrHIGHoutput-design
12HelpShow concise summary when run with no args; full help on --helpCRITICALhelp-system
13HelpLead with examples in help textHIGHhelp-system
14HelpSuggest corrections on typos and next steps after actionsHIGHhelp-system
15HelpProvide shell completion for bash, zsh, fish, powershellMEDIUMhelp-system
16ErrorsEvery error answers: what happened, why, and what to doCRITICALerror-handling
17ErrorsUse namespaced error codes (AUTH-003, NET-001)HIGHerror-handling
18ErrorsDefine clear exit code mapping (0=success, 1=general, 2=usage, etc.)HIGHerror-handling
19ErrorsNever show raw stack traces; log to debug fileHIGHerror-handling
20InteractivePrompt for missing args only when stdin is TTY; fail with --no-inputHIGHinteractivity
21InteractiveConfirm destructive actions; support --yes to bypassCRITICALinteractivity
22ConfigFollow XDG Base Directory (~/.config/mycli/) on all platformsHIGHconfiguration
23ConfigPrecedence: flags > env vars > project config > user config > defaultsHIGHconfiguration
24AuthSupport token via flag, env var, stored creds, and interactive loginHIGHauthentication
25ExtendUse mycli-<name> executable pattern for pluginsMEDIUMextensibility
26PerfTarget <100ms cold start; defer work until neededHIGHperformance
27PerfPrint something within 100ms; responsiveness > raw speedHIGHperformance
28DistShip single static binary when possibleHIGHdistribution
29DistSupport --version with version, commit hash, build dateMEDIUMdistribution
30TestIntegration-test full CLI invocations (stdout, stderr, exit codes)HIGHtesting
31RobustHandle SIGINT (exit 130), SIGTERM (exit 143), SIGPIPE (exit silently)HIGHtesting
32RobustValidate input early, bail before state changesHIGHerror-handling
33RobustDesign for crash-only: avoid cleanup requirements on exitMEDIUMtesting
34SecurityNever accept secrets via flags (visible in ps, shell history)CRITICALconfiguration
35FutureKeep changes additive; deprecate before removingHIGHdistribution

Workflow

When building or reviewing a CLI tool:

  1. Read the relevant reference files for the domains you're working on
  2. Apply rules by impact -- CRITICAL first, then HIGH, then MEDIUM
  3. Use the checklist before shipping

Additional references

Связанные навыки

Looking for an alternative to cli-design or another community skill for your workflow? Explore these related open-source skills.

Показать все

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

★ 333.8k
⑂ 0
Искусственный интеллект

widget-generator

Logo of f
f

Создание настраиваемых плагинов виджетов для системы ленты новостей prompts.chat

★ 149.6k
⑂ 0
Искусственный интеллект

flags

Logo of vercel
vercel

Фреймворк React

★ 138.4k
⑂ 0
Браузер

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

★ 98.6k
⑂ 0
Разработчик