Skills
A skill is a set of instructions the agent follows when you call it. Type / in the message box and pick one, or type its name, such as /kosuke:open-pr. In a Codex session, skills start with $, as in $kosuke:open-pr. Sensei ships ten skills, named after its kosuke plugin, and you can add your own to the repository, the workspace or your account.
Run a skill
- In a chat session, type
/in the message box, or$in a Codex session. A menu lists every skill the session carries. - Keep typing to filter the list, then pick a skill. Each row shows a badge that says where the skill comes from.
- Add arguments after the name. The message box shows the arguments the skill takes.
- Send the message. The agent follows the skill for that turn.
The Open PR and Sync buttons run /kosuke:open-pr and /kosuke:sync-branch for you. Skills from installed plugins appear in the same menu, named after their plugin, such as /code-review:code-review.
The menu also lists /clear and /compact, badged Runtime. A Codex session offers them as $clear and $compact. They act on the agent's memory of the conversation, and Messages, Up next and steering explains them.
Where skills come from
| Origin | Where it lives | Who manages it | Menu badge |
|---|---|---|---|
| Project Skill | In the repository, at .claude/skills/<name>/SKILL.md for Claude or .agents/skills/<name>/SKILL.md for Codex. Muse Code reads .agents/skills, then .codex/skills, then .claude/skills | Whoever can commit to the repository | Project |
| Workspace Skill | Settings > your workspace > Skills | Workspace owners and admins | Workspace |
| Personal Skill | Settings > You > Skills | You | Personal, or your name for other members |
| Factory Skill | Sensei's kosuke plugin | Sensei | Sensei |
The menu can list one name twice when a Project Skill shares it with a Workspace or Personal Skill. The badge tells you which is which.
Your Personal Skills also reach your Sensei. A workspace's skills do not. The skills Sensei ships do not, because each one needs a session's branch.
Skills Sensei ships
Sensei ships these as Factory Skills, in its own plugin named kosuke. Every chat session carries all of them. They cannot be turned off and do not appear in settings, and Sensei keeps them up to date. Type each one with the plugin's prefix, such as /kosuke:open-pr, or $kosuke:open-pr in a Codex session. Muse Code and Google sessions use / too.
| Skill | What it does | What runs it |
|---|---|---|
/kosuke:automated-qa | Tests the Testing Checklist in a browser and publishes a QA Report. | The Review & QA button, /kosuke:ship, or you |
/kosuke:batch-merge | Picks the pull requests with a go-ahead, merges them into one, reviews its own conflict resolutions, runs a short QA and opens one pull request for you to merge. | Sensei, when the project has Batch merging on |
/kosuke:open-pr | Commits and pushes the work, then opens or updates the pull request. | The Open PR button, /kosuke:ship, or you |
/kosuke:plan | Plans a change with you: rounds of questions until the intent is clear, a spec another model attacks, then a detailed phased plan. | /kosuke:ship for a migration or backfill, or you |
/kosuke:prototype | Draws a screen before it is built, from the project's real components. You click through its normal flows, and choose conditions such as errors, theme and width. | /kosuke:ship, or you |
/kosuke:review | Has one model from another family try to break the change, then fixes its MAJOR and CRITICAL findings. | The Review & QA button, /kosuke:ship, /kosuke:batch-merge, or you |
/kosuke:ship | Carries the session's ticket from raw text to a pull request marked ready, and stops only when it needs you. | Ship on a Backlog ticket in Sensei, or you |
/kosuke:sync-branch | Brings the branch up to date with its Target Branch. | The Sync button, Sensei when you approve a card that asks to sync, or you |
/kosuke:web-pentest | Looks for security holes and proves each one against the Preview. | You |
Turn a Workspace Skill on or off
Workspace owners and admins choose which Workspace Skills every session in the workspace carries.
- Open Settings > your workspace > Skills.
- Use the switch on the skill's row.
A running session picks up the change at its next turn. Members see each skill as Enabled or Disabled and can read a Custom Skill's files. To add a Custom Skill or change one, see Manage Workspace Skills.
Personal Skills
Personal Skills are your own. Add them in Settings > You > Skills with Add skill, or drop a skill folder on the list. They use the same editor and limits as Workspace Skills.
- They follow you into every workspace you belong to. One switch turns a skill on or off everywhere.
- Only you can see or edit them in settings. Workspace admins cannot.
- A Personal Skill replaces a Custom Skill of the same name in your tasks. The row in your settings names the workspaces where this happens.
- A Personal Skill never replaces a Factory Skill. One named
open-prsits beside/kosuke:open-pr, and the Open PR button still runs Sensei's.
Whose Personal Skills a session uses
A session carries the Personal Skills of its Assignee, whoever sends the message. When you send into a session assigned to someone else, the menu shows their Personal Skills with their name as the badge. AI providers explains credential ownership, which follows the work's place and selected source.
When a session is reassigned to you, your Personal Skills apply from its next turn. When you leave a workspace, your Personal Skills stop reaching its sessions.