All skills
python-professional-usage
FoundationJIT onlyanalysis-agent/task-agent/review-agent: use when Python changes cross import, async, resource, typing, mutability, or serialization boundaries; skip tool-only work.
- Group
- Language usage
- Supported roles
- MainAnalysisTaskReview
- Source
- SKILL.md
Use when
Trigger signals that make this skill the right owner
- Python import initialization reload fork spawn side effects async blocking task cancellation context propagation resource lifetime
- Python dynamic typing runtime validation missing None mutability aliasing serialization exception boundary
Do not use when
Anti-triggers — as binding as the triggers above
- language runtime selection dependency policy build mechanics test strategy or measured performance is the open decision
- no Python-specific runtime resource import mutability or serialization boundary changes
Required inputs
What must be supplied before this skill can decide anything
- changed Python entrypoints process model async call graph and owned resources
- runtime value shapes mutability aliases serialization format and caller failure contract
Output contract
What this skill owes the next role
- Python boundary decision with inspected import and initialization, async and cancellation, resource lifetime, typing and mutability, serialization and exception behavior, validation evidence, proof limits, residual risk, and specialist handoffs
Escalation signals
When this skill must hand the decision back
- Python imports blocking work leaked resources shared mutation and unsafe serialization can fail across workers requests cancellation or version skew
Loaded by
This skill never owns a task. These professionals may pull it in as Layer 3.
Targeted references
Each reference carries its own load condition. None of them enter context by default.
| Reference | Load when | Do not load when | Required by |
|---|---|---|---|
| benchmarks-and-patterns.mdbenchmark-pattern | Python change crosses import async resource mutability typing serialization or exception boundary whose failure semantics remain unclear | Current Python entrypoints value contracts and focused checks settle the changed boundary | TaskAnalysisReview |