Install any skill in seconds. Free to start, no credit card required.
Get Started Free →joonghyun-lee-frieren/research
Use this skill when external documentation, standards, or library comparisons are needed.
Passed 10 of 22 test cases with the skill, and 5 of 22 without it.
and 10 more in the full report
7 fixed3 passed either way10 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.8-flash on 10/21/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
We're deciding whether to migrate our state management setup from Redux Toolkit to Zustand in our React 18 codebase. Could you check the latest official documentation and specs for both, compare their trade-offs with clear criteria, and structure your answer into key findings, a comparison section, a clear recommendation for our repository, along with any risks or unknown areas we should watch out for?
| Checked | Without skill | With skill |
|---|---|---|
| The response contains a top-level level 2 markdown heading named Key Findings | Missed | Passed |
| The response contains a top-level level 2 markdown heading named Source-Based Comparison | Missed | Passed |
| The response contains a top-level level 2 markdown heading named Recommendation | Missed | Passed |
The instructions your model reads when the skill loads.
Read the workflow when this skill applies. For code work, follow the guard contract first. Design and implementation require separate user turns. Only the owning main conversation writes code. Missing evidence is unknown; honest failure is a valid outcome.
test cases passed, vs 5 / 22 without
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.