Store Python project task runners in pyproject.toml with taskipy
Define short Python project commands in pyproject.toml so agents and maintainers can run the same test, lint, docs, and release tasks without hunting through shell notes.
npx skills add agentskillexchange/skills --skill store-python-project-task-runners-in-pyproject-toml-with-taskipy
Use taskipy when an agent needs to make a Python repository’s routine commands explicit, versioned, and easy to invoke from the project root. The operator workflow is narrow: inspect the repo’s existing test, lint, build, docs, and release commands; encode them as named taskipy tasks in pyproject.toml; add pre/post hooks only where they reduce repeated command chaining; then verify the named tasks run consistently in local or CI automation. Invoke this instead of using the project normally when repeated commands are scattered across README text, shell history, CI YAML, or maintainer memory and the agent needs a stable command surface it can call later. The scope boundary is project-local task orchestration for Python repos, not a generic Python framework, package manager, or CI platform listing.
What this skill actually does
Inputs and prerequisites: Python, pip or Poetry, pyproject.toml.
Setup notes: Install with pip install taskipy or add it through the project’s Python package manager, define tasks under [tool.taskipy.tasks] in pyproject.toml, then run them with task or poetry run task .
Source and verification boundary: use https://github.com/taskipy/taskipy as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.
Framework fit: publish this as a Multi-Framework workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.