← home · use cases
What a skill generator is actually for.
The point of turning docs into SKILL.md is what it unlocks: Tab-aware CLIs, shareable knowledge, and completions that work offline. Here are the jobs people reach for skillterm to do.
Tab completion for a CLI that never shipped one
Generate a SKILL.md for a tool with no completion script, and get contextual Tab completions from its own docs.
read the workflow →
web docsA skill from a SaaS product's docs
Point skillterm at a documentation URL and turn a SaaS API into a reusable, Tab-aware skill.
read the workflow →
offlineBuilding skills offline from man pages
With web access turned off, generate skills purely from system man pages and --help output.
read the workflow →
registrySharing a curated skill set across a team
Publish skills to a registry and let your whole team install a consistent, versioned set.
read the workflow →
per-repoPer-project skill overrides
Pin repo-specific skills that win over your personal and system skills inside that project.
read the workflow →
runtimeRunning the generator on Codex instead of Claude Code
Switch the headless agent runtime from Claude Code to Codex with a single config value.
read the workflow →
Don't see yours?
If you spend time in a terminal and read docs, skillterm probably fits. Tell us your setup.