How do I install the Invoke Python Engineer skill?

Run npx skillmds@latest add drmoisan/invoke-python-engineer in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Invoke Python Engineer safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Invoke Python Engineer?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Invoke Python Engineer free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Invoke Python Engineer?

drmoisan (@drmoisan) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Invoke Python Engineer by drmoisan — Agent Skill

Name: Invoke Python Engineer
Author: drmoisan

Invoke Python Engineer

Invoke the python-typed-engineer worker to design, implement, and verify Python changes within typed repository boundaries. Applies Black -> Ruff -> Pyright -> Pytest toolchain, the 3-production + 3-test per-batch budget, and zero-regression quality gates.

drmoisan da7b894 2.8 KB Updated Sep 17, 2026

File contents

Implement Python Skill

This direct-use wrapper delegates Python implementation work to the python-typed-engineer worker. Use this entry point when a prompt needs a scoped Python change that must stay inside the typed engineer's guardrails.

When to Use This Skill

Use this skill when:

The user requests a Python code change, bug fix, refactor, or test addition.
Estimated scope fits the small path (1-3 production files plus corresponding tests).
The toolchain (Black, Ruff, Pyright, Pytest) can be run in the current environment, or the user has explicitly authorized an unverified plan-only response.

If the estimated scope exceeds the small-path budget, this skill defers to the orchestrated flow via python-change-budget-router instead of proceeding directly.

Inputs

Objective statement (what the change must accomplish).
Files or entrypoints in scope.
Constraints, including public APIs that must be preserved.
Optional approved plan. If none is supplied, the worker delegates plan authoring to atomic_planner before any edits.
Optional budget override in the form budget: prod=<N>, test=<M> subject to repo policy compliance.

Output Paths

Python source and test files within the approved scope.
Baseline evidence under <FEATURE>/evidence/baseline/<timestamp>/ and post-change evidence under <FEATURE>/evidence/qa-gates/<timestamp>/ per evidence-and-timestamp-conventions.
This location is canonical per evidence-and-timestamp-conventions and is not overridable. See .agents/skills/evidence-and-timestamp-conventions/SKILL.md for the canonical evidence path authority.
Plan artifacts under the active feature folder when the task is feature-scoped.

Required Reporting Block

The worker must return the python-qa-gate reporting block:

Scope (exact file list).
Baseline (Ruff, Pyright, Pytest, coverage status).
Plan (design and test strategy).
Diffs (patch-style or full-file replacements).
QA Gate Results (Ruff, Pyright, Pytest, and coverage deltas, or clearly marked unverified).

Worker Routing

Worker: python-typed-engineer

Preloaded Contracts

The worker operates under the following preloaded skills and rules:

policy-compliance-order
python-change-budget-router
atomic-plan-contract
python-qa-gate
acceptance-criteria-tracking
feature-promotion-lifecycle
remediation-handoff-atomic-planner
evidence-and-timestamp-conventions
.agents/skills/python/SKILL.md (path-scoped for **/*.py)
AGENTS.md
AGENTS.md
AGENTS.md

---name: invoke-python-engineerdescription: Invoke the python-typed-engineer worker to design, implement, and verify Python changes within typed repository boundaries. Applies Black -> Ruff -> Pyright -> Pytest toolchain, the 3-production + 3-test per-batch budget, and zero-regression quality gates.---# Implement Python SkillThis direct-use wrapper delegates Python implementation work to the `python-typed-engineer` worker. Use this entry point when a prompt needs a scoped Python change that must stay inside the typed engineer's guardrails.## When to Use This SkillUse this skill when:- The user requests a Python code change, bug fix, refactor, or test addition.- Estimated scope fits the small path (1-3 production files plus corresponding tests).- The toolchain (Black, Ruff, Pyright, Pytest) can be run in the current environment, or the user has explicitly authorized an unverified plan-only response.If the estimated scope exceeds the small-path budget, this skill defers to the orchestrated flow via `python-change-budget-router` instead of proceeding directly.## Inputs- Objective statement (what the change must accomplish).- Files or entrypoints in scope.- Constraints, including public APIs that must be preserved.- Optional approved plan. If none is supplied, the worker delegates plan authoring to `atomic_planner` before any edits.- Optional budget override in the form `budget: prod=<N>, test=<M>` subject to repo policy compliance.## Output Paths- Python source and test files within the approved scope.- Baseline evidence under `<FEATURE>/evidence/baseline/<timestamp>/` and post-change evidence under `<FEATURE>/evidence/qa-gates/<timestamp>/` per `evidence-and-timestamp-conventions`.- This location is canonical per evidence-and-timestamp-conventions and is not overridable. See `.agents/skills/evidence-and-timestamp-conventions/SKILL.md` for the canonical evidence path authority.- Plan artifacts under the active feature folder when the task is feature-scoped.## Required Reporting BlockThe worker must return the `python-qa-gate` reporting block:1. Scope (exact file list).2. Baseline (Ruff, Pyright, Pytest, coverage status).3. Plan (design and test strategy).4. Diffs (patch-style or full-file replacements).5. QA Gate Results (Ruff, Pyright, Pytest, and coverage deltas, or clearly marked **unverified**).## Worker Routing- Worker: `python-typed-engineer`## Preloaded ContractsThe worker operates under the following preloaded skills and rules:- `policy-compliance-order`- `python-change-budget-router`- `atomic-plan-contract`- `python-qa-gate`- `acceptance-criteria-tracking`- `feature-promotion-lifecycle`- `remediation-handoff-atomic-planner`- `evidence-and-timestamp-conventions`- `.agents/skills/python/SKILL.md` (path-scoped for `**/*.py`)- `AGENTS.md`- `AGENTS.md`- `AGENTS.md`

Frequently asked questions