Defame1297/holocron
0
0
Fork 0
Code Issues 14 Pull Requests Actions Packages Projects Releases 3 Wiki Activity

fix(kyberforge): remove internal mechanics sentence from skill-author description

Browse Source 
## 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 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0147vXtL5sP6vorDdqXGJJU9
This commit is contained in:
Defame1297
2026-07-04 11:24:05 +00:00
parent fb4bfc1ae7
commit 1eb28da207
1 changed files with 1 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
plugins/kyberforge/skills/skill-author/SKILL.md
View File

@@ -4,9 +4,7 @@ description: >
Use when the user wants to create a new skill from scratch ("write a skill 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 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 an existing one ("improve this skill", "fix based on feedback", "apply these
audit findings", "update based on grill output"). Handles both the full audit findings", "update based on grill output"). Also use when the user provides inline feedback
create flow (scaffold → fill → validate) and the improve flow (signals →
root cause → edit → audit). Also use when the user provides inline feedback
about a skill's behavior and wants it applied, or when a grill session, eval 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 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 don't say "improve" explicitly. Do not use for read-only review — use