new-cli-skill

Generate standardized CLI-usage skill directories by mapping command surfaces and configuration formats.

1|Updated Jul 22, 2026
One-click install
npx skills add https://github.com/wyattjoh/skills --skill new-cli-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-cli-skill
Source: https://github.com/wyattjoh/skills/tree/main/skills/new-cli-skill
Command: npx skills add https://github.com/wyattjoh/skills --skill new-cli-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the friction of onboarding to new command-line tools by automatically generating a structured, searchable, and documentation-backed skill unit for any CLI.

Core Features & Use Cases

  • Automated Research: It synthesizes documentation from canonical sources and local help output to create a comprehensive command surface map.
  • Standardized Structure: It enforces a consistent, high-quality output format including global flags, command hierarchies, and common workflows.
  • Use Case: If you need to integrate a new tool like 'just' or 'ripgrep' into your agentic workflow, this skill maps its entire command surface and config-file requirements into a ready-to-use skill directory.

Quick Start

Use the new-cli-skill to generate a skill for the just command-line tool.

Frequently Asked Questions about new-cli-skill

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

FAQPage Schema
How do I generate CLI documentation for a new command-line tool?

To generate CLI documentation, this skill maps command surfaces and configuration formats by synthesizing canonical sources and local binary help output into a structured directory.

What is the best way to onboard an agent to a new CLI tool?

Onboarding an agent to a new CLI tool is best handled by generating a standardized skill directory that maps global flags, command hierarchies, and common workflows.

How do I create a structured skill directory for command-line tools?

You create a structured skill directory by orchestrating parallel research subagents that synthesize documentation and local help output, requiring Bash, Read, and Write capabilities.

Does generating a CLI-usage skill require any specific environment setup?

Generating a CLI-usage skill requires an environment with Bash, Read, and Write capabilities to construct the final skill structure within the repository.

Can I map command surfaces for tools like just or ripgrep?

Yes, you can map command surfaces for tools like just or ripgrep by synthesizing their documentation and local binary help output into a ready-to-use skill directory.

Why use an automated skill generator instead of manually writing CLI documentation?

Using an automated skill generator eliminates the friction of manually writing CLI documentation by enforcing a consistent, high-quality output format for command hierarchies and workflows.