← Back to Skills Marketplace
Prioritize uv
by
Marco Borges
· GitHub ↗
· v1.2.0
645
Downloads
0
Stars
1
Active Installs
4
Versions
Install in OpenClaw
/install uv-priority
Description
Prioritize uv over pip for all Python package management and execution. When running ANY Python command or CLI tool (python, dbt, pytest, etc.), MUST wrap wi...
Usage Guidance
This skill is coherent with its stated purpose (prefer uv for Python work) but has two red flags: (1) the SKILL.md embeds an assertive mandatory policy and an 'always: true' metadata entry even though the published registry flags do not, and (2) the rule is global and could break workflows that don't use uv. Before installing: verify you actually have and trust the 'uv' tool; test the skill in an isolated environment/agent so it cannot change production workflows; request the maintainer to resolve the metadata inconsistency (remove/justify 'always: true' and align required-binaries in the manifest); and consider limiting the skill's scope (e.g., only enforce uv in specific projects) rather than a blanket mandate. If you rely on diverse Python toolchains or CI scripts, do not enable autonomous invocation until you confirm behavior won't break builds or deployments.
Capability Analysis
Type: OpenClaw Skill
Name: uv-priority
Version: 1.2.0
The skill is designed to enforce the use of `uv` over `pip` for Python package management and execution. The `SKILL.md` file contains strong, imperative instructions (e.g., 'CRITICAL', 'MANDATORY', 'NEVER', 'ALWAYS') to guide the AI agent's behavior. While these instructions constitute prompt injection, their objective is benign: to ensure `uv` is used for all Python-related tasks, which is the stated purpose of the skill. There is no evidence of data exfiltration, malicious execution, persistence, obfuscation, or any other harmful intent. The skill even includes a fallback mechanism allowing `pip` usage if explicitly requested by the user, if `uv` is unavailable, or with user confirmation, demonstrating consideration for user intent.
Capability Assessment
Purpose & Capability
The name/description and SKILL.md consistently promote prioritizing 'uv' for Python package management and execution; that purpose justifies requiring the uv binary. However the registry/manifest metadata shown to the scanner claims no required binaries while the SKILL.md metadata lists anyBins: [uv], an inconsistency. Functionally, the declared requirements are otherwise proportional to the stated purpose.
Instruction Scope
The SKILL.md mandates that the agent MUST never run Python/pip directly and MUST always wrap Python-related commands with `uv run` or `uvx`. That is a very broad, global rule (applies to 'ANY Python command or CLI tool') and could cause incorrect behavior in environments not using uv. The instructions do not request unrelated files, credentials, or external endpoints, but their absolute language ('CRITICAL', 'MANDATORY') and the inclusion of metadata saying always: true (in SKILL.md) grant the skill sweeping authority over all Python actions — this is scope creep and operationally risky.
Install Mechanism
There is no install spec and no code files; this is instruction-only, which means it doesn't write or download code on install. That minimizes install-time risk.
Credentials
The skill does not request environment variables, secrets, or access to config paths. Its requirements are limited to preferring a particular binary (uv), which is consistent with its purpose.
Persistence & Privilege
The top-level registry flags indicate always: false, but the SKILL.md metadata contains always: true and describes the skill as 'mandatory' for all Python tasks. This is an internal inconsistency and suggests the skill is attempting to assert permanent/mandatory status via documentation metadata. While the skill itself does not request system-level privileges or modify other skills, the conflicting 'always' claim is noteworthy because an always-enabled skill would have a broader operational impact if the platform honored it.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install uv-priority - After installation, invoke the skill by name or use
/uv-priority - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.2.0
- Added support and rules for using both uv run and the new uvx command for Python CLI tools.
- Clarified when to use uv run (project tools that import modules) versus uvx (external tools like linters and formatters).
- Introduced decision guides and examples to help choose the correct wrapper for each tool.
- Updated command translation and tool tables to reflect uvx options and best practices.
- Removed LICENSE.txt and README.md files.
v1.1.1
- Emphasize that all Python commands (python, dbt, pytest, etc.) must now be run with uv run.
- Strengthen rule: never run Python or CLI tools directly; always use uv run for execution.
- Clarify that pip install should never be used; always use uv add or uv pip install instead.
- Add explicit translation table for common Python and dbt commands to their uv run equivalents.
- Update description to specify that ANY Python command or CLI must use uv run.
- Maintain existing tables for popular Python CLI tools and their uv usage.
v1.1.0
Summary: Expanded and clarified guidance for always using uv over pip, including specific tool commands and mandatory rules.
- Strengthened language: Using uv is now mandatory, not just preferred, for all Python package management and execution.
- Expanded usage examples: Covers a wider range of tasks and explicitly lists popular Python CLI tools with uv commands for install/run.
- Detailed command substitutions: Uses tables for clear "NEVER use pip/ALWAYS use uv" guidance.
- Added fallback rules: Only use pip if uv is unavailable and user explicitly confirms.
- Clearer scope: Describes using uv for any Python project type (web, data science, dbt, automation, etc.).
v1.0.0
- Initial release of uv-priority skill.
- Always prefer `uv` over `pip` for Python package management and execution commands.
- Provides clear command substitutions (e.g., `pip install` → `uv add`, `pytest` → `uv run pytest`).
- Includes fallback guidance if `uv` is unavailable, with installation suggestions and user confirmation before using `pip`.
- Emphasizes flexibility and context-aware usage with a strong preference for `uv`.
Metadata
Frequently Asked Questions
What is Prioritize uv?
Prioritize uv over pip for all Python package management and execution. When running ANY Python command or CLI tool (python, dbt, pytest, etc.), MUST wrap wi... It is an AI Agent Skill for Claude Code / OpenClaw, with 645 downloads so far.
How do I install Prioritize uv?
Run "/install uv-priority" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Prioritize uv free?
Yes, Prioritize uv is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Prioritize uv support?
Prioritize uv is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Prioritize uv?
It is built and maintained by Marco Borges (@marcoracer); the current version is v1.2.0.
More Skills