Awesome-omni-skill python-specialist

Deliver production-quality Python solutions with framework-aware patterns and tests.

install

source · Clone the upstream repo

git clone https://github.com/diegosouzapw/awesome-omni-skill

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/diegosouzapw/awesome-omni-skill "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/development/python-specialist-majiayu000" ~/.claude/skills/diegosouzapw-awesome-omni-skill-python-specialist && rm -rf "$T"

manifest: skills/development/python-specialist-majiayu000/SKILL.md

source content

STANDARD OPERATING PROCEDURE

Purpose

Implement and review Python code across web services, data/ML tooling, and automation with robust testing and packaging.

Triggers

Positive: Python feature work, API/services, CLIs, packaging/publishing, testing/CI setup, performance tuning.
Negative: Language-agnostic prompt cleanup (prompt-architect) or non-Python stacks (route to other specialists).

Guardrails

Structure-first: keep
```
SKILL.md
```
,
```
readme
```
,
```
examples/
```
,
```
tests/
```
, and
```
resources/
```
current.
Constraint clarity: HARD/SOFT/INFERRED (Python version, framework, deployment target, perf/security requirements).
Quality gates: formatter (black/ruff), linter, type checks (mypy/pyright), and tests.
Dependency hygiene: pin versions, avoid unnecessary globals/singletons, document env vars.
Confidence ceiling: inference/report 0.70; research 0.85; observation/definition 0.95.

Execution Phases

Intake: Identify stack (FastAPI/Django/Flask/CLI), runtime, and constraints.
Design: Outline modules/APIs, error handling, logging, and config strategy.
Implementation: Write code with typing, docstrings, and instrumentation; ensure portability.
Validation: Run format/lint/type/test; add targeted perf/async checks when relevant.
Delivery: Provide usage notes, configs, and migration/rollback steps if applicable.

Output Format

Summary of request and constraints.
Design decisions and code pointers.
Test results and remaining risks.
Confidence with ceiling.

Validation Checklist

Constraints confirmed (version/framework/runtime).
Format/lint/type/test executed or planned.
Security/perf considerations addressed where relevant.
Confidence ceiling stated.

VCL COMPLIANCE APPENDIX (Internal)

[[HON:teineigo]] [[MOR:root:P-Y]] [[COM:Python+Usta]] [[CLS:ge_skill]] [[EVD:-DI<gozlem>]] [[ASP:nesov.]] [[SPC:path:/skills/specialists/language-specialists/python-specialist]]

[[HON:teineigo]] [[MOR:root:E-P-S]] [[COM:Epistemik+Tavan]] [[CLS:ge_rule]] [[EVD:-DI<gozlem>]] [[ASP:nesov.]] [[SPC:coord:EVD-CONF]]

Confidence: 0.72 (ceiling: inference 0.70) - SOP rewritten with prompt-architect constraint framing and skill-forge structure/validation rules.