Generate a SKILL.md file that makes the CLI discoverable and usable by AI agents through the skill-creator methodology. This file serves as a self-contained skill definition that can be loaded by Claude Code or other AI assistants.
SKILL.md files follow a standard format that enables AI agents to:
- Discover the CLI's capabilities
- Understand command structure and usage
- Generate correct command invocations
- Handle output programmatically
---
name: "cli-anything-<software>"
description: "Brief description of what the CLI does"
---- Installation prerequisites
- Basic command syntax
- Command groups and their functions
- Usage examples
- Agent-specific guidance (JSON output, error handling)
from skill_generator import generate_skill_file
skill_path = generate_skill_file(
harness_path="/path/to/agent-harness"
)
# Default output: skills/cli-anything-<software>/SKILL.md- Software name and version from setup.py
- Command groups from the CLI file (Click decorators)
- Documentation from README.md
- System package requirements
- Default template:
templates/SKILL.md.template - Uses Jinja2 placeholders for dynamic content
- Can be extended for software-specific sections
SKILL.md is generated canonically at the repo root, with a packaged compatibility copy for installed harnesses:
skills/
└── cli-anything-<software>/
└── SKILL.md
<software>/
└── agent-harness/
└── cli_anything/
└── <software>/
└── skills/
└── SKILL.md
cd cli-anything-plugin
python skill_generator.py /path/to/software/agent-harnessThe SKILL.md generation should be run after Phase 6 (Test Documentation) completes successfully, ensuring the CLI is fully documented and tested before creating the skill definition.
- SKILL.md must be self-contained (no external dependencies for understanding)
- Include agent-specific guidance for programmatic usage
- Document
--jsonflag usage for machine-readable output - List all command groups with brief descriptions
- Provide realistic examples that demonstrate common workflows
If the harness supports previews, the generated or edited SKILL.md should
include a dedicated preview section that covers:
- the producer command surface:
cli-anything-<software> preview ... - the consumer command surface:
cli-hub previews ... - whether
preview diff,preview live ..., or poll mode exist - how agents should use
--jsonresults and artifact paths - at least one publish example and one inspect/watch example
For the full preview methodology, see
preview-methodology.md.
ReplSkin prefers the repo-root canonical skill file and falls back to the packaged copy, displaying whichever absolute path is available in the startup banner. AI agents can read the file at the displayed path:
# In the REPL initialization (e.g., shotcut_cli.py)
from cli_anything.<software>.utils.repl_skin import ReplSkin
skin = ReplSkin("<software>", version="1.0.0")
skin.print_banner() # Displays repo-root skills/cli-anything-<software>/SKILL.md when availableEnsure setup.py includes the skill file as package data so it is installed with pip:
package_data={
"cli_anything.<software>": ["skills/*.md"],
},