iainmcl/python-coding
claude/skills/python-coding/SKILL.md
Python coding conventions and style guide. Use when writing or modifying Python code.
development
Updated May 1, 2026
$ install --global
skillsauthnpx skillsauth add iainmcl/dotfiles python-codingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 1, 2026, 9:57 AM143.3s1 file scanned
SKILL.md
- name:
- python-coding
- description:
- Python coding conventions and style guide. Use when writing or modifying Python code.
Python Coding
Documentation
-
New functions should include docstrings that describe their purpose. This should not include things like
:paramor:return:sections, just a brief description of what the function does. -
Use type hints for function parameters and return types to improve code readability and maintainability.
Code Style
- Use modern practices. For example use f-strings for string formatting instead of
%orstr.format(). - When typing use
list,dict,set, andtupleinstead ofList,Dict,Set, andTuplefrom thetypingmodule, unless you need to specify type parameters. For optional parameters use| Noneinstead ofOptional.
Logging
When logging messages add the additional context in the extra parameter of the
logging methods. For example:
logger.info("Processing item", extra={"item_id": item.id})
When logging exceptions use logger.exception instead of logger.error to
automatically include the stack trace. For example:
try:
process_item(item)
except Exception:
logger.exception("Failed to process item", extra={"item_id": item.id})
DO NOT include exception information in the log message itself. For example, avoid doing this:
try:
process_item(item)
except Exception as e:
logger.error(f"Failed to process item: {e}", extra={"item_id": item.id})
Module imports
Avoid using function level imports wherever possible. All imports should be at the top of the file. The only exceptions to this are if there are issues with top level imports like circular imports.
Related Skills
iainmcl/weekly-review
development
VerifiedTrustedCommunity
Run a weekly achievement review - pulls from Jira, GitHub, and Slack to capture what you shipped in the last week, maps achievements to your 2026 goals, and appends impact-focused entries to your brag doc. Use when asked to "do a weekly review", "capture this week's wins", "update my brag doc", "what did I ship this week", "record my achievements", "what have I done this week", "add to my performance doc", or anything about tracking weekly progress, brag doc entries, or performance evidence. Trigger even if the user just says "weekly review" or "document what I did".
SKILL.mdUpdated May 19, 2026
iainmcl/skill-creator
testing
VerifiedTrustedCommunity
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
SKILL.mdUpdated May 19, 2026
iainmcl/setup-project-update
tools
VerifiedTrustedCommunity
Set up a project update config for the current repo, so that running project-update requires no setup questions. Use when asked to "set up project updates", "configure project update", "initialise project update", or "create a project update config". Run this once per project repo.
SKILL.mdUpdated May 19, 2026
iainmcl/sentry-fix
testing
VerifiedTrustedCommunity
Find the highest-frequency unresolved Sentry error for the VAT & Invoicing or Billing team, understand its root cause, create a Jira ticket in the APP project, implement a fix, and open a draft PR. Use when asked to "fix sentry issues", "triage sentry errors", "look at sentry", "what's broken in sentry", "create a fix for a sentry issue", or "sentry triage". Runs the full flow autonomously in the background.
SKILL.mdUpdated May 19, 2026