Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →archive228/reduce-nesting
Flatten deeply nested conditionals into readable, early-return code.
Passed 21 of 23 test cases with the skill, and 20 of 23 without it.
3 fixed18 passed either way0 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
Refactor this Kotlin function that looks up nested configuration values: ```kotlin fun findConfigValue(config: Map<String, Any>): String? { var result: String? = null if (config.containsKey("settings")) { val settings = config["settings"] as? Map<String, Any> if (settings != null && settings.containsKey("db")) { val db = settings["db"] as? Map<String, Any> if (db != null && db.containsKey("url")) { result = db["url"] as? String } } } return result } ```
| Checked | Without skill | With skill |
|---|---|---|
| Returns early upon failing dictionary key lookups. | Missed | Passed |
| Eliminates the mutable result variable. | Passed | Passed |
The instructions your model reads when the skill loads.
Deep nesting hides bugs in the branches you didn't read.
if (!valid) return; instead of wrapping the whole body in if (valid) {...}.test cases passed, vs 20 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.