This skill should be used when writing, reviewing, or refactoring Python code. Covers code integration, idiomatic patterns, docstring formatting, anti-abstraction rules, and software engineering basics.
SkillScore100Maintained
Automatic
◆Coding pack
Last verified 8/14/2026
What it changes
Passed 23 of 23 test cases with the skill, and 13 of 23 without it.
Without skill57%
With skill100%
Checks it passed that the model alone missed
Does not use `typing.Union`.
Uses a single-line docstring for the test function.
Uses imperative mood in the summary line of the docstring.
and 14 more in the full report
10 fixed13 passed either way0 still failing0 broke
Pass-rate lift
+43 pp
Tokens
+25%
Agent turns
0%
Response time
-46%
Model gemini-3.6-flashMeasured 8/14/2026v123 of 23 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 10
Prompt
Write a Google-style docstring Returns section for a function `analyze_text(text)` that returns two values: `word_count` (int) and `sentiment` (float).
What was checked, without and with the skill
Checked
Without skill
With skill
Documents each returned value as a separate named entry in the Returns section.
Missed
Passed
Does not format the return type as a single `tuple` type in the docstring header.
Missed
Passed
case-22 · gemini-3.6-flash · 8/14/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md104 lines5 files
Python Guidelines
Integrate into existing code. Don't append to it.
Simple is better than complex. Flat is better than nested.
Errors should never pass silently. Unless explicitly silenced.
If the implementation is hard to explain, it's a bad idea.
-- The Zen of Python (PEP 20)
Code Philosophy
Match existing naming, importing, and signature patterns. Use existing utilities and data structures.
Functions have a single purpose. Don't hardcode behavior that makes them less general.
No trivial wrappers for 2 lines or less. Inline it.
Inline single-use variables at the usage site.
No try/except unless critical. Let errors surface.
No duplicate code.
Functions handle their own input validation. No if-else checks in main.
Use pathlib, not os.path.
Consider API and time costs for MongoDB/Gemini/OpenAI/Claude/Voyage.
Don't do this:
# Generate comment report only if requested
if include_comments:
comment_report = generate_comments_report(start_date, end_date, team, verbose)
else:
comment_report = ""
print(" Skipping comment analysis (disabled)")
Do this:
comment_report = generate_comments_report(start_date, end_date, team, verbose) if include_comments else ""
Ask yourself: "Am I adding code, or integrating into what exists?"