Prioritize uv

Security checks across malware telemetry and agentic risk

Overview

This skill openly tells the agent to prefer uv for Python work and does not contain hidden code, data access, or persistence, though it may change how Python commands are run.

Install this only if you want uv to be the default for Python package management and command execution. Review dependency-changing commands before approving them, and explicitly override the skill for projects that require pip, Poetry, Conda, system Python, or direct interpreter execution.

SkillSpector

By NVIDIA

Vulnerability Patterns

Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (2)

Vague Triggers

Medium

Confidence: 95% confidence
Finding: The skill declares itself mandatory for essentially any Python-related task and instructs the agent to always rewrite commands around `uv run` or `uvx`. This broad trigger can override task-specific safety, correctness, or user-intent requirements and cause the agent to execute unintended tooling paths across many contexts.

Vague Triggers

Medium

Confidence: 94% confidence
Finding: The `Use when` section applies the skill to an extremely wide set of Python activities, including virtually any package, environment, script, test, or dbt workflow. In an agent setting, such ambiguity increases the chance that this skill activates outside its intended environment and alters commands in ways that break workflows, bypass user preference, or introduce unsafe execution assumptions.

VirusTotal

64/64 vendors flagged this skill as clean.

View on VirusTotal