Maintain Python Template
Extend or repair the Python Template repository while keeping its catalog, Copier questions, templates, generated references, and tests synchronized. Use for adding a framework, provider, database, interface, ML tool, deployment target, preset, compatibility rule, or generated-project capability.
Install
$ agentstack add skill-leynier-python-template-maintain-python-template ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-leynier-python-template-maintain-python-template) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Maintain Python Template
Make catalog-driven changes without creating a choice that renders but cannot run.
Change Workflow
- Inspect
catalog/components.yml,catalog/presets.yml,copier.yml, the relevant files undertemplate/, and existing tests before editing. - Define the component metadata and compatibility constraints in the catalog first. Keep each choice in exactly one architectural role unless it genuinely serves several roles.
- Wire Copier defaults and choices to the catalog. Preserve the three simple presets and reject incompatible combinations with an actionable validator message.
- Add functional source, dependency, configuration, test, README, and environment-variable templates for the component. Avoid placeholder-only integrations.
- Run
uv run python scripts/compile_catalog.py --check. If generated files are stale, run the command without--check, review all generated changes, then check again. - Add focused repository tests and generate at least one representative project. Validate its imports or endpoints, not only file presence.
- Run the gates in
validate-python-stackbefore proposing delivery.
Invariants
catalog/generated/catalog.json,catalog/generated/choices.yml, anddocs/reference/*.mdare compiler outputs; edit their sources instead.- Generated projects use a
srclayout,uv, Ruff, pytest, typing, and reproducible dependency bounds. - Optional layers must disappear cleanly when disabled.
- Conditional template path components must remain short enough to render on Windows.
- A deploy target keeps Docker portability; cloud IaC is limited to supported target/provider pairs.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: leynier
- Source: leynier/python-template
- License: MIT
- Homepage: https://python-template.leynier.dev
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.