Skip to content

Commit bd022a0

Browse files
n0mahdclaude
andcommitted
docs: describe the skill switches by what they do, not by what is on screen
The Skills guide described the sparkle and the icons beside a switch, clicking a row, a bar at the bottom, badges and the buttons on a row. Keep what the switches do and where they apply, and drop the rest. Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
1 parent f8437ea commit bd022a0

1 file changed

Lines changed: 16 additions & 21 deletions

File tree

‎docs/user/skills.md‎

Lines changed: 16 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,8 @@
33
Open **Settings → Skills** on web and desktop to see which skills your agents can use. The page
44
reads the environment and project chosen at the top of Settings, so with a remote environment you
55
see that machine's skills. You can turn each skill on or off for every agent, or for one agent at a
6-
time, and choose which projects use it. To change what a skill says, open it with **Edit skill**,
7-
edit it in your editor or ask an agent.
6+
time, and choose which projects use it. To change what a skill says, edit its `SKILL.md` in your
7+
editor or ask an agent.
88

99
The agents are your enabled provider instances. Two Claude instances show as two agents, each
1010
with its own config folder.
@@ -26,10 +26,8 @@ instead of showing it as empty.
2626

2727
## Turning skills on or off
2828

29-
Every skill has a switch. It turns the skill on for every agent, or off for every agent. The icons
30-
beside it show who has the skill on: a sparkle when every agent does, otherwise the agents that
31-
do. Click a row to open it, switch single agents and use **Use in…** or **Edit skill**. The switch
32-
on **This project**, **Global** or a group turns all of its skills on or off at once, and asks
29+
A skill's switch turns it on or off for every agent. Open the skill to switch a single agent. The
30+
switch on **This project**, **Global** or a group changes all of its skills at once, and asks
3331
before turning many off.
3432

3533
Turning a skill on for an agent that reads a different folder makes a link in that agent's own
@@ -51,23 +49,21 @@ removes that link and nothing else.
5149
the skill. On Windows, global links are junctions, and project links need Developer Mode or
5250
administrator rights.
5351

54-
Skills the installer recorded as coming from the same place, such as a GitHub repo, sit together
55-
under **From owner/repo** when there are two or more. A search lists skills without groups.
52+
Skills the installer recorded as coming from the same place, such as a GitHub repo, are grouped
53+
together when there are two or more.
5654

5755
## Acting on several skills
5856

59-
**Select** turns on checkboxes. A group's box ticks all of its skills. A bar at the bottom turns the
60-
ticked skills on or off for every agent, deletes them, or puts them in a project with **Use in…**.
61-
**Done** goes back to the switches.
57+
Choose **Select** to act on several skills at once: turn them on or off for every agent, delete
58+
them, or put them in projects with **Use in…**. Ticking a group ticks all of its skills.
6259

6360
## Using a skill in projects
6461

6562
**Use in…** chooses where a skill is used: **This project only**, **Globally**, or **Only these
6663
projects**, which lists the projects of this environment. A skill used in only some projects is
67-
still Global, with one copy, so an edit shows up in all of them. It has a badge such as **2
68-
projects**. Each change asks first, and never merges into or replaces a skill with the same name;
69-
T3 Code leaves both and says so. When git tracks a project skill that leaves its project, the
70-
confirmation says you can undo it with git.
64+
still Global, with one copy, so an edit shows up in all of them. Each change asks first, and never
65+
merges into or replaces a skill with the same name; T3 Code leaves both and says so. When git
66+
tracks a project skill that leaves its project, the confirmation says you can undo it with git.
7167

7268
Such a skill is linked into each project that uses it, outside git, and into the worktrees T3 Code
7369
makes for those projects. The agents that read `.agents/skills` have it in all of them. Turning on
@@ -86,13 +82,12 @@ move or delete them.
8682

8783
**Needs attention** filters the list to skills that need a look. A skill is on it when:
8884

89-
- an installed and enabled agent doesn't use it. Hover the icons to see which agent, or use the
90-
button on the row to turn the skill on for it. An agent
91-
loads one skill per name, the first it finds in its folders (Codex and OpenCode list every
92-
copy), so a copy that another folder shadows is not used by that agent. Claude doesn't use a
93-
skill that its own `skillOverrides` setting switches off either.
85+
- an installed and enabled agent doesn't use it. An agent loads one skill per name, the first it
86+
finds in its folders (Codex and OpenCode list every copy), so a copy that another folder shadows
87+
is not used by that agent. Claude doesn't use a skill that its own `skillOverrides` setting
88+
switches off either.
9489
- the same name exists more than once with different text, in **This project**, in **Global**, or
95-
across them. These rows have a **Conflict** badge.
90+
across them.
9691
- Claude can't read the skill's header, the YAML between the `---` lines at the top of
9792
`SKILL.md`, so it skips the skill. Quote a value that contains a colon or brackets, for example
9893
a description.

0 commit comments

Comments
 (0)