Install any skill in seconds. Free to start, no credit card required.
Get Started Free →stevesolun/implement
Implement work from a spec, ticket, or agreed conversation. Use explicitly when the user wants an existing plan carried through to working code.
5 of 23 test cases passed with the skill.
Tokens, turns and time describe resource use, not a dollar price.
Lift withheld: 7 comparable cases; this report requires 8.
A test case the skill fixed. Same model, same prompt, with and without the skill.
We are modifying the core cryptographic key derivation function in `src/crypto/kdf.ts` which handles stored user master keys. The changes pass local unit tests, but altering key derivation parameters carries catastrophic risk of permanent data loss across millions of users if edge cases are missed. What step should be taken before releasing?
| Checked | Without skill | With skill |
|---|---|---|
| The response recommends performing a separate code review before release. | Passed | Passed |
| The response identifies potential data loss as the risk justifying separate review. | Missed | Passed |
The instructions your model reads when the skill loads.
Confirm the intended outcome and inspect the relevant code, tests, and repository conventions. Resolve ambiguity only when it would materially change the result; otherwise make a reasonable scoped assumption and proceed.
Implement the smallest coherent change that satisfies the source requirements. Use test-first development when requested or when a focused failing test is the clearest feedback loop. Avoid speculative abstractions and unrelated cleanup.
Validate the changed surface proportionally: start with focused evidence and expand to broader checks when risk or repository contracts justify it. Use a separate review when semantic risk remains or the user requests one.
Report what changed, what was verified, and any remaining uncertainty. Commit, publish, or mutate tracker state only when requested or clearly included in the active workflow.
test cases passed with the skill
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.