Every Skill has a scope setting that controls how broadly it’s applied.
Scope options
| Scope | Behaviour |
|---|
| session (default) | The skill must be manually selected in the Skill Picker when starting a new chat. It applies only to sessions where you explicitly activate it. |
| global | The skill is automatically applied to every new session without manual selection. Only one global skill can be active at a time. |
Setting scope
When creating or editing a skill, the Scope toggle appears at the bottom of the editor:
- Session — user selects per session (default for all new skills)
- Global — auto-applied to every new session
Only one skill can have global scope and be enabled at the same time. If you enable a second
global skill, the first one’s scope reverts to session automatically.
Use cases for global scope
Global scope is useful when you have a standard operating mode you always want — for example:
- An internal house-style skill that enforces your team’s output format
- A client-specific persona you’re using for an extended engagement
- A “strict mode” skill with low temperature for all sessions during a focused analysis sprint
Disabling a global skill
To stop a global skill from auto-applying:
- Go to Skills (⌘2)
- Click the global skill to open it
- Toggle Scope back to Session, or disable the skill entirely with the Enabled toggle
Alternatively, you can toggle the Enabled switch on the skill card in the Skills list — disabled skills are excluded from auto-application and from the Skill Picker.
Per-session override
Even with a global skill active, you can override it in any session:
- Detach the global skill from the session header during that session
- Apply a different skill — this replaces the global skill for that session only
- The global skill remains active for all other new sessions
