Skip to content

feat(skills): add eval coverage requirements to the creator-skill #54

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
olegshulyakov merged 2 commits into from
May 21, 2026
Merged

feat(skills): add eval coverage requirements to the creator-skill #54

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b739dae
feat(skills): add eval coverage requirements to the creator-skill
olegshulyakov May 21, 2026
21ebd08
Merge branch 'main' into feature/skills-creator-skill-eval-coverage
olegshulyakov May 21, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .agents/skills/creator-skill/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ If the request spans multiple phases, read the references in workflow order: aut

1. **Clarify scope**: identify what the skill should do, which user phrases or contexts should trigger it, what output it should produce, and whether objective evals are useful.
2. **Write the skill**: revise `SKILL.md` with concise metadata, focused instructions, bold scan anchors, and references for details that would bloat the main file.
3. **Test behavior**: run this skill's `scripts/quick_validate.py` against the target skill; for objectively testable skills, create realistic eval prompts and run skill-enabled outputs against a meaningful baseline.
3. **Test behavior**: run this skill's `scripts/quick_validate.py` against the target skill; for router skills, confirm every `references/*.md` file has 8-10 evals mapped by `reference`; for objectively testable skills, run skill-enabled outputs against a meaningful baseline.
4. **Show evidence**: share outputs and benchmark results with the user before making another revision.
5. **Iterate deliberately**: continue until feedback is resolved or further changes stop improving results.
6. **Package last**: package the final skill only after the user is satisfied with behavior and trigger accuracy.
Expand Down
Loading
Loading