You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/edge/en/concepts/skills.mdx
+24-10Lines changed: 24 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,10 @@ mode: "wide"
9
9
10
10
Skills are self-contained directories that provide agents with **domain-specific instructions, guidelines, and reference material**. Each skill is defined by a `SKILL.md` file with YAML frontmatter and a markdown body.
11
11
12
-
When activated, a skill's instructions are injected directly into the agent's task prompt — giving the agent expertise without requiring any code changes.
12
+
Agents first receive each configured skill's name and description. When a
13
+
description applies to the current request, the agent loads that skill's full
14
+
instructions for that execution. This keeps unrelated instructions out of the
15
+
context while giving the agent the relevant expertise without code changes.
13
16
14
17
<Notetype="info"title="Skills vs Tools — The Key Distinction">
15
18
**Skills are NOT tools.** This is the most common point of confusion.
@@ -79,12 +82,13 @@ reviewer = Agent(
79
82
role="Senior Code Reviewer",
80
83
goal="Review pull requests for quality and security issues",
81
84
backstory="Staff engineer with expertise in secure coding practices.",
| Activation | Full SKILL.md body text |`activate_skill()`|
358
-
359
-
During normal agent execution (passing directory paths via `skills=["./skills"]`), skills are automatically discovered and activated. The progressive loading only matters when using the programmatic API.
0 commit comments