From python-toolkit
Use when you see ruff violations, '[*] fixable with --fix', ty/pyright diagnostics, or Python import errors in terminal output. Also use when the user asks about lint rules, type errors, code stats, or project configuration.
How this skill is triggered — by the user, by Claude, or both
Slash command
/python-toolkit:python-toolkitThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Dispatch skill for Python development. Routes observable situations to the appropriate retained skill or bare CLI invocation.
Dispatch skill for Python development. Routes observable situations to the appropriate retained skill or bare CLI invocation.
Before routing, detect the project environment:
pixi.toml in the current or parent directory → pixi modepyproject.toml, requirements.txt, .venv/ → pip/venv moderuff --version, ty --version, pixi --version| Observable situation | Action | Notes |
|---|---|---|
ruff output with [*] fixable with --fix | ruff check --fix <path> | Run first, review remaining; use --unsafe-fixes with caution |
| ty/pyright errors or type warnings in output | Invoke typecheck skill | Full report with context and error grouping |
| Both lint and type errors present | ruff check --fix then typecheck skill | Fix lint first, types second |
| Ambiguous or multi-source diagnostic output | Invoke diagnostic-review skill | Triages ruff + ty output together; auto-activates on mixed noise |
Unknown ruff rule code (e.g. I001, PLR6201) | Invoke rule skill | Explains the rule with fix guidance |
| Many lint violations, need overview | Invoke stats skill | Ranked summary of violations by rule category |
| Code style inconsistencies after editing | ruff format <path> | Direct ruff invocation; no wrapper needed |
| Import blocks unsorted or messy | ruff check --fix <path> | I001 is auto-fixable |
Project management commands were culled in 4.0.0.0. Use bare CLI directly for these operations.
| Situation | Action |
|---|---|
| User asks to add a package | pixi add <package> / pip install <package> |
| User asks to remove a package | pixi remove <package> / pip uninstall <package> |
| Dependencies out of sync | pixi install / pip install -r requirements.txt |
| No pyproject.toml or pixi.toml in directory | pixi init / uv init to bootstrap the project |
| User asks to run a task or script | pixi run <task> / python <script.py> |
| User asks about project or tool status | Invoke info skill |
| User asks to configure linting, types, or task runner | Invoke configure skill |
| User asks to build the Python package | pixi run build / python -m build |
| User asks to run tests, or test suite is failing | pixi run test / pytest <path> |
| User asks to list, add, or remove pixi tasks | pixi task add <name> / pixi task list |
| User asks to list, create, or remove environments | pixi environment list / pixi project environment add |
| pixi.lock is outdated or user asks to refresh it | pixi update |
| User needs a shell with the environment active | pixi shell |
When you encounter an unfamiliar ruff rule, ty error, or tool flag:
ruff is not installed: advise pip install ruff or pixi global install ruffty is not installed: advise pip install ty or pixi global install typixi is not installed and user wants pixi features: advise installation from https://pixi.shpixi init or uv init to create onenpx claudepluginhub zaynram/code-marketplace --plugin python-toolkitGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.