ahgraber/python
skills/python/SKILL.md
Python skill router. Use when planning, implementing, or reviewing Python changes and you need to select focused skills for workflow, design, typing/contracts, reliability, testing, data/state, concurrency, integrations, runtime operations, or notebook async behavior.
development
Updated Mar 29, 2026
$ install --global
skillsauthnpx skillsauth add ahgraber/skills pythonInstall 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: Mar 31, 2026, 8:39 PM57.5s1 file scanned
SKILL.md
- name:
- python
- description:
- |-
Python Skill Router
Scope Note
- Treat these recommendations as preferred defaults for common cases, not universal rules.
- If a default conflicts with project constraints or worsens the outcome, suggest a better-fit alternative and explain why it is better for this case.
- When deviating, call out tradeoffs and compensating controls (tests, observability, migration, rollback).
Invocation Notice
- Inform the user when this skill is being invoked by name:
python.
Overview
Use this skill to route Python work to focused skills instead of loading one large guide. Select the smallest set of skills that matches the task.
Route by Task
Choose one or more based on scope:
- Delivery workflow, branch/PR checks:
python-workflow-delivery - Design, readability, module boundaries, refactor shape:
python-design-modularity - Typing, public interfaces, contract evolution, pydantic boundaries:
python-types-contracts - Error strategy, retries/timeouts, retryability policy:
python-errors-reliability - Testing strategy, pytest practices, async/reliability testing:
python-testing - Data lifecycle, consistency boundaries, configuration:
python-data-state - Concurrency models, cancellation/deadlines, leak diagnostics:
python-concurrency-performance - External clients, outbound reliability, resilience contract tests:
python-integrations-resilience - Services/jobs/CLI runtime behavior and observability:
python-runtime-operations - Notebook async loop ownership and
#%%/.ipynbpatterns:python-notebooks-async
Shared Defaults
- Use project-defined Python version first.
- Use
uvfor env/dependency workflow and run checks withuv run .... - Prefer
#%%.pynotebooks over.ipynbunless.ipynbis explicitly required. - If repo conventions conflict with a selected skill, follow the repo and state tradeoffs.
Clarification Rule
Ask concise questions before coding when behavior/contracts/reliability policy are ambiguous or when defaults appear counterproductive for the repository context.
Related Skills
ahgraber/editorial-review
development
VerifiedTrustedCommunity
Use when the user wants rigorous, non-sycophantic editorial feedback on a draft, essay, blog post, or argument through back-and-forth dialogue — pressure-testing thesis, structure, argument, clarity, tone, and evidence. Triggers: "be my sparring partner", "pressure-test this draft", "poke holes in my argument", "is this ready to publish", "sharpen this post", "where is this weak". Not for one-shot copyediting, proofreading, or ghostwriting.
2SKILL.mdUpdated May 26, 2026
ahgraber/synthesize
testing
VerifiedTrustedCommunity
Use when distilling the through-line gist of one or more sources — the spine, argument, tension, or recurring frame running through a set of documents, notes, research, or transcripts, OR across the ideas within a single rich piece — into a few concise paragraphs. Triggers: "synthesize", "what's the through-line/gist", "extract the insight", "pull these together". Not for faithful summary or condensation that covers what a source says, nor for comparisons or catalogs where enumeration is the deliverable.
2SKILL.mdUpdated May 22, 2026
ahgraber/writing-tests
development
VerifiedTrustedCommunity
Use when writing or reviewing tests in any language, or diagnosing a suite that is slow, brittle, or hard to read. Triggers: "write tests", "how should I test this", "what kind of test", "test is flaky/fragile", "should I mock this", "test is hard to read". For Python-specific guidance see `python-testing`.
2SKILL.mdUpdated May 16, 2026
ahgraber/strudel
development
VerifiedTrustedCommunity
Use when writing, debugging, or explaining Strudel live-coding music patterns — mini-notation syntax, pattern functions (fast/slow/every/off/stack), synth/sample selection, audio effects, scale/chord/voicing API, or EDM production recipes. Triggers: "write a Strudel pattern", "how do I make a bassline in Strudel", "what does .every() do", "strudel drum beat", "strudel chord voicing", any Strudel code question.
2SKILL.mdUpdated May 16, 2026