Skip to content
Back to skills

Python Tooling

ASecurity

Configure Python tooling, dependency surfaces, static analysis, and verification gates. Use when editing `pyproject.toml`, `requirements.txt`, `pytest.ini`, `ruff`, `pyright`, CI, or Python release checks.

  • 549 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 5, 2026
developmentpythonsecurity

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned September 5, 2026

npx -y skills add HoangNguyen0403/agent-skills-standard --skill python-tooling --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Python Tooling?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Python Tooling
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/hoangnguyen0403-python-tooling-3fcd56c9/badge)](https://www.skillsdirectory.com/skills/hoangnguyen0403-python-tooling-3fcd56c9)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: python-tooling
description: Configure Python tooling, dependency surfaces, static analysis, and verification gates. Use when editing `pyproject.toml`, `requirements.txt`, `pytest.ini`, `ruff`, `pyright`, CI, or Python release checks.
metadata:
  triggers:
    files:
      - "pyproject.toml"
      - "requirements.txt"
      - "pytest.ini"
      - "ruff.toml"
      - ".ruff.toml"
      - "mypy.ini"
      - "uv.lock"
      - "poetry.lock"
    keywords:
      - ruff
      - pyright
      - basedpyright
      - pip-audit
      - compileall
      - pytest.ini
---

# Python Tooling

## **Priority: P1 (HIGH)**

## Rules

- Keep one authoritative dependency surface per environment and audit every tracked requirements file.
- Prefer `ruff` for lint plus import hygiene; use `pyright` or `basedpyright` for type feedback.
- Run `pytest` plus `python -m compileall` for runtime Python changes.
- Add smoke or security gates when the change touches workflow/runtime behavior.

## Verification Workflow

1. **Lint** with `ruff check`.
2. **Type-check** with `pyright` or `basedpyright` where configured.
3. **Run focused pytest scope** for changed behavior.
4. **Run `python -m compileall -q ...`** for changed runtime trees.
5. **Run security or smoke gates** when auth, workflow runtime, or dependency surfaces change.

## Anti-Patterns

- **No untracked requirements files** outside the audit list.
- **No format-only green claim** for runtime changes.
- **No stale SBOM or audit artifacts** in release gates.
- **No local-only fix without CI parity** when changing gates.

## References

- [Framework Map](../references/framework-map.md)
- [Tooling Gates](references/tooling-gates.md)

Files in this skill

  • SKILL.md1.7 KB
  • evals/evals.json1.2 KB
  • references/tooling-gates.md418 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…