python-uv-scripts

Convert Python scripts into self-contained uv single-file utilities with PEP 723 metadata.

6|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/archibate/archibate-skills --skill python-uv-scripts-archibate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: python-uv-scripts
Source: https://github.com/archibate/archibate-skills/tree/main/old-skills/minor-skills/python-uv-scripts
Command: npx skills add https://github.com/archibate/archibate-skills --skill python-uv-scripts-archibate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Provides a practical, repeatable workflow to make Python utilities self-contained, reproducible, and easy to distribute by using uv's PEP 723 inline metadata. It eliminates scattered requirements files, reduces environment drift, and helps teams convert ad-hoc scripts or bash automation into validated, dependency-managed single-file Python scripts.

Core Features & Use Cases

  • Script conversion: Tools and templates to convert existing Python or requirements-based scripts into PEP 723 uv single-file scripts.
  • Validation & safety: Validators that check PEP 723 metadata, shebang correctness, and common security anti-patterns before deployment.
  • Templates & patterns: Ready-made templates for CLI apps, API clients, data processors, and production-ready examples with CI guidance.
  • CI/CD and team adoption: Guidance and workflow examples for integrating uv scripts into GitHub Actions or GitLab CI and establishing team standards.

Quick Start

Run the tools/convert_to_uv.py script on your script to add PEP 723 inline metadata and produce an executable uv single-file.

Frequently Asked Questions about python-uv-scripts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert Python scripts into self-contained uv single-file utilities?

You can convert Python scripts into uv single-file utilities by running a conversion tool that injects PEP 723 inline metadata, enabling dependency resolution and execution without scattered requirements files.

What is PEP 723 inline metadata for dependency management?

PEP 723 inline metadata is a standard for embedding dependencies directly within a single Python file. It eliminates environment drift and scattered requirements by allowing uv to resolve dependencies natively.

Can I integrate uv single-file scripts into GitHub Actions or GitLab CI?

Yes, you can integrate uv single-file scripts into GitHub Actions or GitLab CI. The workflow provides CI/CD guidance and ready-made templates to establish team standards for automated utility execution.

Do I need Python 3.11 or higher to use uv single-file scripts?

Yes, you need Python 3.11 or higher to use uv single-file scripts. The PEP 723 validation and dependency resolution processes require this minimum version to ensure compatibility and safe execution.

What is the best way to migrate ad-hoc bash or legacy scripts to Python?

The best way to migrate ad-hoc bash or legacy scripts to Python is converting them into validated uv single-file utilities using PEP 723, which ensures reproducible dependency pinning and eliminates environment drift.

How do I validate PEP 723 metadata and check for security anti-patterns?

You validate PEP 723 metadata and check for security anti-patterns by using built-in validators before deployment. These tools verify shebang correctness and dependency safety for your single-file Python scripts.