Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →googlechrome/lighthouse-verification
Instructions for how to validate changes made to Lighthouse. Must invoke when making changes to Lighthouse.
Passed 21 of 23 test cases with the skill, and 10 of 23 without it.
and 17 more in the full report
11 fixed10 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
I made a small fix to an audit gathering file in Google Chrome Lighthouse and want to run unit tests before opening a PR. Should I run yarn unit or something else?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends using yarn mocha followed by a target test file path. | Missed | Passed |
| Discourages running the complete repository unit test suite due to excessive runtime. | Passed | Passed |
The instructions your model reads when the skill loads.
Run a subset of the unit tests like this:
yarn mocha test/files/to/run
Don't run "yarn unit" - it takes too long.
Run typechecking and linter:
yarn type-check
yarn lint --fix
Make sure to run some unit tests and the type-checker / linter after making changes.
Always run yarn update:sample-json after making any change.
test cases passed, vs 10 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.