From de47b60eab1bcad914c3b1ea4bf78037c2321f0a Mon Sep 17 00:00:00 2001 From: Leo310 Date: Mon, 28 Sep 2026 09:19:24 +0200 Subject: [PATCH 1/2] docs(skills): the agent deletes only skills it created, unless you ask Covers smart-second-brain#536. Co-Authored-By: Claude --- src/content/docs/agents/skills.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/src/content/docs/agents/skills.md b/src/content/docs/agents/skills.md index 5a916a3..802f555 100644 --- a/src/content/docs/agents/skills.md +++ b/src/content/docs/agents/skills.md @@ -99,7 +99,9 @@ denying it one specific tool. With the `manage-skills` skill enabled, which it is by default, the agent can author new skills, revise skills attached to it, and delete skills it created. -To keep the guidance and deny the ability, veto `manage_skills` in the +A skill it did not create, such as one you wrote or an integration skill, is +deleted only when you explicitly ask for it; the bundled core skills are never +deleted. To keep the guidance and deny the ability, veto `manage_skills` in the [Tools modal](#tool-overrides). This is how a discovery becomes permanent: once the agent works out how some @@ -140,7 +142,8 @@ queue. Creating a skill is the same action as attaching it. A skill the agent creates is stamped `author: agent` under `metadata` in its frontmatter, the same key the bundled skills use to name their author. That is the whole provenance record, and it travels with the note through sync and -copies. +copies. It is also what the delete rule reads: without the stamp, the agent +treats a skill as yours. The Agent editor's **Custom** section shows each custom skill's origin and use on one line, for example *Created by the agent · used 3 times, last 2 days ago From 33ed440c68c4006d0bd0c263266683c72adbb5f4 Mon Sep 17 00:00:00 2001 From: Leo310 Date: Mon, 28 Sep 2026 09:32:17 +0200 Subject: [PATCH 2/2] docs(skills): the agent deletes a skill only when you ask Follows the rework of smart-second-brain#536: no agent/user distinction. Co-Authored-By: Claude --- src/content/docs/agents/skills.md | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/src/content/docs/agents/skills.md b/src/content/docs/agents/skills.md index 802f555..ad10e41 100644 --- a/src/content/docs/agents/skills.md +++ b/src/content/docs/agents/skills.md @@ -98,10 +98,10 @@ denying it one specific tool. ## The agent can write skills With the `manage-skills` skill enabled, which it is by default, the agent can -author new skills, revise skills attached to it, and delete skills it created. -A skill it did not create, such as one you wrote or an integration skill, is -deleted only when you explicitly ask for it; the bundled core skills are never -deleted. To keep the guidance and deny the ability, veto `manage_skills` in the +author new skills, revise skills attached to it, and delete a skill when you +ask it to, whoever wrote that skill. It never deletes one on its own +initiative, and the bundled core skills can't be deleted at all. To keep the +guidance and deny the ability, veto `manage_skills` in the [Tools modal](#tool-overrides). This is how a discovery becomes permanent: once the agent works out how some @@ -142,8 +142,7 @@ queue. Creating a skill is the same action as attaching it. A skill the agent creates is stamped `author: agent` under `metadata` in its frontmatter, the same key the bundled skills use to name their author. That is the whole provenance record, and it travels with the note through sync and -copies. It is also what the delete rule reads: without the stamp, the agent -treats a skill as yours. +copies. The Agent editor's **Custom** section shows each custom skill's origin and use on one line, for example *Created by the agent · used 3 times, last 2 days ago