Find a skill
- Open Tools → Skills.
- Search by name, keyword, or path to find an installed skill.
- Read its description and source. A Claude-owned skill and a Rudr-owned skill are not automatically available through every harness.
- Return to Code with the intended harness selected.
- Type
/in the composer, choose an offered skill or command, and add the task-specific request.
The selected entry appears as a token in the composer. Review its description before sending; removing the token removes that selection from the draft. Skill instructions can guide model behavior, but they do not independently grant new account access or install missing tools.
Understand command kinds
Rudr session commands such as /compact, /rewind, and /fork are handled as session operations where supported. Native provider slash commands depend on that provider’s implementation. A skill can instead attach an instruction body for the task to follow.
These mechanisms can look similar in a slash picker while having different effects. Do not infer native history support simply because a similarly named skill exists. Qualified history operations are described in context and history.
If an entry is missing
Check the active harness and the skill’s owning source under Tools or Code Harnesses. A skill found in another CLI’s configuration is not guaranteed to transfer when switching providers. If the entry remains absent, record its source and the harness version without uploading private instruction files unnecessarily.
Use available tools to inspect dependencies and permissions to understand the task’s actual action authority.