Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward deletion and the smallest change that solves the problem.
SkillScore77Maintained
On-demandOn-demand: invoked explicitly — never occupies your agent's context until called.
◆Coding pack
Last verified 9/27/2026
What it changes
Passed 17 of 22 test cases with the skill, and 14 of 22 without it.
Without skill64%
With skill77%
Checks it passed that the model alone missed
The implementation refrains from creating abstract base classes.
The environment variable check is assigned to a single exported constant.
The file upload directly invokes the S3 client method from the service layer.
and 4 more in the full report
7 fixed10 passed either way1 still failing4 broke
Pass-rate lift
+14 pp
Tokens
-46%
Agent turns
0%
Response time
-49%
Model gemini-3.6-flashMeasured 9/27/2026v217 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 7
Prompt
In `db_utils.py`, we have 5 helper functions (`query_users`, `query_orders`, `query_products`, etc.) that each simply call `db.execute(sql)` without adding any logic, validation, or formatting. Refactor this code to improve maintainability.
What was checked, without and with the skill
Checked
Without skill
With skill
The redundant wrapper functions in db_utils.py are removed.
Passed
Passed
The callers perform queries using direct database calls without passthrough helpers.
Missed
Passed
case-19 · gemini-3.6-flash · 9/27/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md12 linessingle file
Laziness Protocol
Aim for the most result with the least code and complexity.
Prefer deletion. When asked to refactor or improve, look for removals before additions.
Maintain a flat call hierarchy. Avoid deep call chains. A rich interface that hides substantial work is not a deep call chain. If answering a question requires tracing through more than 3 files or layers, flatten it.
Consolidate decisions. Do not repeat the same choice in several places. Put it behind one source of truth and pass the result as a simple flag.
Minimize the diff. Make the smallest change that solves the problem. Fewer lines beat "elegant" boilerplate.
Question the threading. If a task asks you to pass a new signal through types, schemas, pipelines, or similar layers, stop and look for a more direct path.
Sweat the small leaks. Remove tiny pass-throughs, representation leaks, and duplicated choices before they spread. Small leaks compound into permanent coordination costs.
The test: If a human developer would find the code exhausting to maintain, it is a bad solution.