Creating skills¶

skilly create creates a specification-compliant skill directory with a SKILL.md file.

Usage¶

skilly create [OPTIONS] [NAME]

The NAME argument is required outside an interactive terminal. In a TTY, you can omit it and the wizard will prompt for one.

Options¶

Option	Description
`--description <TEXT>`	Describe what the skill does and when to use it.
`--instructions <MARKDOWN>`	Markdown body for the `SKILL.md`.
`--license <NAME>`	License name or bundled reference.
`--compatibility <REQS>`	Environment requirements for the skill.
`--metadata <KEY=VALUE>`	Add frontmatter metadata (repeatable).
`--allowed-tools <TOOLS>`	Space-separated pre-approved tools.
`--with-scripts`	Create an empty `scripts/` directory.
`--with-references`	Create an empty `references/` directory.
`--with-assets`	Create an empty `assets/` directory.
`--overwrite`	Replace an existing skill atomically.
`-y`, `--yes`	Create without confirmation.
(destination flags)	See destinations reference.

Examples¶

Minimal non-interactive creation¶

skilly create code-review \
  --description "Review code for correctness and maintainability." \
  --instructions "# Instructions\n\nReview the proposed change." \
  --yes

With metadata and scripts¶

skilly create deployment-checks \
  --description "Validate deployment readiness." \
  --instructions "# Instructions\n\nRun the deployment checklist." \
  --metadata owner=platform \
  --metadata severity=high \
  --with-scripts \
  --with-references \
  --yes

Overwrite an existing skill¶

skilly create code-review --overwrite --yes

Interactive behavior¶

In a TTY without sufficient flags, skilly create opens a full-screen editor:

Ctrl+S — creates the skill.
Ctrl+X — cancels without writing.

Existing skills are rejected unless --overwrite is passed.