agentleFS
Sign inStart free
JakkuSakuraJakkuSakura/skills/python-uv/SKILL.md

python-uv

Skill1 starsChanged 9 months agoMITView on GitHub

Use when creating or updating Python projects that should be managed by uv with the uv_build backend, including pyproject.toml layout, scripts entrypoints, and uv run/tool usage.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 1 is distinctive, and 7 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 7

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill to standardize Python project setup with uv, including pyproject.toml fields, uv_build backend, and CLI entry points.

    line 9
  2. Very specific:

    Create or update pyproject.toml

    line 13
  3. Very specific:

    Ensure package layout (src/) and entry points

    line 14
  4. Distinctive:

    Use uv for dependency sync and executable installation

    line 15
  5. Very specific:

    Use the template in references/pyproject.toml as the baseline.

    line 18
  6. Very specific:

    Ensure __init__.py exists in package dirs

    line 25
  7. Very specific:

    Keep CLI entry points under src/<package_name>/cli/

    line 26
  8. Very specific:

    Run without venv: uv run <script>

    line 30

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Python Uv

Overview

Use this skill to standardize Python project setup with uv, including pyproject.toml fields, uv_build backend, and CLI entry points. Prefer a src/ layout for installable packages.

Workflow

  1. Create or update pyproject.toml
  2. Ensure package layout (src/) and entry points
  3. Use uv for dependency sync and executable installation

Project Template

Use the template in references/pyproject.toml as the baseline. Update:

  • [project].name, version, and description
  • dependencies
  • [project.scripts] entry points

Layout Guidance

  • Prefer src/<package_name>/... layout
  • Ensure __init__.py exists in package dirs
  • Keep CLI entry points under src/<package_name>/cli/

uv Usage

  • Install deps: uv sync
  • Run without venv: uv run <script>
  • Install CLI: uv tool install --editable .

References

  • references/pyproject.toml for the uv/uv_build template

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free