From 1eb28da2073a27239fde295eca10208fd2cc66ea Mon Sep 17 00:00:00 2001 From: Defame1297 Date: Sat, 4 Jul 2026 11:24:05 +0000 Subject: [PATCH] fix(kyberforge): remove internal mechanics sentence from skill-author description MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit ## Why The description sentence "Handles both the full create flow (scaffold → fill → validate) and the improve flow (signals → root cause → edit → audit)." describes internal mechanics rather than user intent. The surrounding trigger phrases already cover both create and improve intents, so this sentence adds no triggering value and violates the description principle of focusing on what the user is trying to achieve. Co-Authored-By: Claude Sonnet 4.6 Claude-Session: https://claude.ai/code/session_0147vXtL5sP6vorDdqXGJJU9 --- plugins/kyberforge/skills/skill-author/SKILL.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/plugins/kyberforge/skills/skill-author/SKILL.md b/plugins/kyberforge/skills/skill-author/SKILL.md index b212a82..939922e 100644 --- a/plugins/kyberforge/skills/skill-author/SKILL.md +++ b/plugins/kyberforge/skills/skill-author/SKILL.md @@ -4,9 +4,7 @@ description: > Use when the user wants to create a new skill from scratch ("write a skill for X", "build a skill that does Y", "create a SKILL.md for Z") or improve an existing one ("improve this skill", "fix based on feedback", "apply these - audit findings", "update based on grill output"). Handles both the full - create flow (scaffold → fill → validate) and the improve flow (signals → - root cause → edit → audit). Also use when the user provides inline feedback + audit findings", "update based on grill output"). Also use when the user provides inline feedback about a skill's behavior and wants it applied, or when a grill session, eval run, or audit has produced findings the user wants acted on — even if they don't say "improve" explicitly. Do not use for read-only review — use