A single SKILL.md that teaches an LLM how to use the nitro Python ecosystem:
- nitro-cli - static site generator (
nitroCLI) - nitro-ui - HTML as Python classes
- nitro-dispatch - plugin and hook system
- nitro-validator - data validation
- nitro-image - chainable image pipeline
Drop it into your assistant's skill directory and the model will know imports, public API, common patterns, and how the pieces compose.
mkdir -p ~/.claude/skills/nitro && \
curl -fsSL https://raw.githubusercontent.com/nitrosh/nitro-skill/main/SKILL.md \
-o ~/.claude/skills/nitro/SKILL.mdFor project-scoped install (only loads in the current repo):
mkdir -p .claude/skills/nitro && \
curl -fsSL https://raw.githubusercontent.com/nitrosh/nitro-skill/main/SKILL.md \
-o .claude/skills/nitro/SKILL.mdmkdir -p ~/.agents/skills/nitro && \
curl -fsSL https://raw.githubusercontent.com/nitrosh/nitro-skill/main/SKILL.md \
-o ~/.agents/skills/nitro/SKILL.mdIf your tool reads a single rules file rather than a skills directory, append the contents:
curl -fsSL https://raw.githubusercontent.com/nitrosh/nitro-skill/main/SKILL.md \
>> .cursorrules(Replace .cursorrules with .windsurfrules, AGENTS.md, GEMINI.md, etc. as appropriate.)
Download SKILL.md and put it wherever your assistant looks for skills.
Re-run the install command. It overwrites the existing file.
The skill is one file, around 700 lines. Each package gets its own section with:
- Install and import (PyPI name vs import name - the two that bite are
nitro-ui->nitro_uiandnitro-image->nitro_img) - Public API surface
- Common patterns
- Gotchas worth knowing before you write code
There's also a "How they compose" section showing a real page that uses four of the packages together, and a house-style note (no em-dashes, no emojis, no inline comments unless necessary).
For deep API reference, each package ships its own SKILL.md inside its repo - this file points you there when the surface here isn't enough.
BSD 3-Clause. See LICENSE.