Usage¶
Once the plugin is loaded, its skills appear as slash commands in the Claude Code prompt. This page covers the common invocation patterns and the namespace.
Invoking skills¶
Skills are invocable by name—with or without the plugin prefix:
They also appear under /skills where Tab-completion works.
Which skill for what¶
| Skill | Purpose | Typical triggers |
|---|---|---|
skill-management |
Scaffold new skills; validate existing ones against the spec | "create a new skill," "scaffold a skill for X," "validate this skill" |
spec |
Write, translate, index and drift-check multilingual specs | "write a spec for X," "is X already covered?," "regenerate the index" |
Response language¶
Skill files themselves are kept in English (token efficiency). Claude detects the user's language from their message and responds in that language—German in gets German out.
Namespace collisions¶
If a project ships its own skill of the same name, the plugin version remains reachable. Use the namespaced form /nolte-shared:<skill> to resolve ambiguity.
Next¶
- Skill Management in depth
- Spec skill in depth
- Specifications: the authoring rules