Proven skills / Compare

Two testing skills · both proven

skill-creator vs test-driven-development

Both skills were run through Claude twice: once on a fixed brief without the skill, once with it. The briefs differ because each is written for the job the skill claims to do, so compare each skill against its own baseline, then decide which difference matters for your work.

skill-creator

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

Category
Testing
Source
anthropics/skills · 182,147 stars
License
Not stated
Proof model
claude-opus-5-5
Brief
“Write a complete SKILL.md for a skill called release-notes that turns a list of merged pull request titles into customer-facing release notes grouped by feature, fix and breaking change, in the tone of a small developer-tools company. Present the finished SKILL.md as a single HTML page, with the frontmatter and body shown in a code block and a short note under it on how you decided what to include.”
Skill commit
dbd4588

test-driven-development

Use when implementing any feature or bugfix, before writing implementation code

Category
Testing
Source
obra/superpowers · 301,947 stars
License
MIT
Proof model
claude-opus-5-5
Brief
“Implement a function that parses a cron expression (the standard five fields) and returns the next run time after a given date, in TypeScript. Present the work as a single HTML page with two columns: the test file on the left and the implementation on the right, each in a code block, with a short note at the top on the order you did things in and anything you decided not to support.”
Skill commit
bb92a77

We don’t pick a winner for you: the pages are the evidence. Both proofs can be repeated with the brief, model and commit shown above. See alternatives to skill-creator or alternatives to test-driven-development.