agentleFS
jskhermanjskherman/engg-skills/skills/uv/SKILL.md

uv

Skill7 starsChanged 6 months agoApache-2.0View on GitHub

Confirm the `uv` Python package manager is installed and available on PATH and document the standard `uv run script.py --output ...` invocation used by every other skill in this repository. Use as a prerequisite check before invoking any other engineering skill. Don't use as a substitute for actually running a skill — it does no engineering work itself.

  • Pipes a download into a shell

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 0 are distinctive, and 7 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    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:

    Every other skill in this repository runs its scripts via uv run (PEP-723 inline dependency declaration).

    line 24
  2. Very specific:

    If uv is missing, install it from https://docs.astral.sh/uv/ .

    line 40
  3. Very specific:

    Every script in this repository is invoked as uv run <path>/scripts/<name>.py <subcommand> --<flag> <value> --output /tmp/<name>.json.

    line 61
  4. Very specific:

    Read this SKILL.md and any referenced files needed for the task.

    line 70
  5. Very specific:

    Use scripts from scripts/ when a deterministic calculation or check is available.

    line 71
  6. Very specific:

    Run uv --version and confirm it prints a version.

    line 84
  7. Very specific:

    Run a representative skill script with uv run ...

    line 85

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “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

uv (Python runner)

Overview

Every other skill in this repository runs its scripts via uv run (PEP-723 inline dependency declaration). This skill is a one-page check: "is uv on PATH, and if not, how do you install it?"

When to Use

  • Setting up the environment for the first time.
  • A skill invocation has failed with uv: command not found.

Don't use for

  • Any engineering calculation.
  • Authoring a new skill (use engineering-skill-creator instead).

Setup

If uv is missing, install it from https://docs.astral.sh/uv/ . The common path on Linux/macOS:

curl -LsSf https://astral.sh/uv/install.sh | sh

On Windows (PowerShell):

powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"

Then verify:

uv --version

Conventions

  • Every script in this repository is invoked as uv run <path>/scripts/<name>.py <subcommand> --<flag> <value> --output /tmp/<name>.json.
  • The script header declares dependencies inline (PEP-723); uv run will install them the first time and cache for subsequent runs.
  • Stdout is reserved for a single success message; results live in the JSON file at --output.

Procedure

  1. Read this SKILL.md and any referenced files needed for the task.
  2. Use scripts from scripts/ when a deterministic calculation or check is available.
  3. Preserve stated assumptions, warnings, and scope limits in the final answer.

Pitfalls

  • Trying to python a script directly rather than uv run; the script header won't be respected.
  • Running scripts from a different working directory than the skill folder — works, but path-based imports resolve engg_skills_common from the sibling skills/engg-skills-common folder, which is robust.

Verification

  • Run uv --version and confirm it prints a version.
  • Run a representative skill script with uv run ... --output <file> and confirm the JSON output file is created.

References

Anti-Patterns

  • Installing uv globally with sudo; let the install script handle it.
  • Pinning uv versions in skill scripts; the PEP-723 dependencies pin the Python deps, and uv itself should be free to update.

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.