skill-creator

Create a directory `.agents/skills/<skill-name>/` containing a SKILL.md file with YAML frontmatter defining a name and description, followed by Markdown instructions. Use kebab-case naming and placeholders like {basePackage} so the skill works in any project.

A SKILL.md needs YAML frontmatter with a kebab-case name and an English description starting with a verb that specifies the trigger. The body should include the problem context, complete implementation code with placeholders, and verification steps.

Never reference concrete package names or project-specific classes. Use placeholders like {basePackage} and {entityName}, create self-contained DTOs instead of referencing generated classes, and use generic paths such as src/main/java/{basePackage}/.

Run evals with and without the skill, then use the aggregate_benchmark.py script on the benchmark directory to compute pass rates, timing, and token deltas. The grader, comparator, and analyzer agent definitions support structured evaluation of outputs.

The skill only defines structure and authoring rules; it does not validate that generated skills actually trigger correctly at runtime. Trigger quality depends on writing a precise description, which may require iterative testing with the included eval tooling.