fix(kyberforge): apply audit improvements to skill-improve
Remove redundant gotcha (duplicated description + Step 1), replace 2-item checklist with prose, and add README.md to file table. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -23,3 +23,4 @@ Provide the skill directory path and any signal files in the conversation. The s
|
||||
| File | Purpose |
|
||||
|------|---------|
|
||||
| `SKILL.md` | Skill instructions for agents |
|
||||
| `README.md` | Human-facing description of the skill and its files |
|
||||
|
||||
@@ -19,13 +19,10 @@ metadata:
|
||||
|
||||
- Patching per symptom is the default failure mode. Three eval failures may all trace to one missing instruction — always identify the root cause before editing.
|
||||
- Do not create new scripts unless a signal explicitly calls for it. Writing scripts from scratch requires transcript analysis that is out of scope here; flag the opportunity as a suggestion instead.
|
||||
- If no improvement signals are present, do not proceed — redirect to `/skill-audit` for a blind review.
|
||||
|
||||
## Step 1 — Verify inputs
|
||||
|
||||
Confirm:
|
||||
- [ ] Skill directory path is provided and the directory exists
|
||||
- [ ] At least one improvement signal is present in the conversation or a referenced file
|
||||
Confirm the skill directory path exists and that at least one improvement signal is present in the conversation or a referenced file.
|
||||
|
||||
If the skill dir is missing, ask for it. If no signals are present, stop: "This skill applies existing signals to a skill. For a blind review without signals, use `/skill-audit` instead."
|
||||
|
||||
|
||||
Reference in New Issue
Block a user