python-env
Fast Python environment management with uv (10-100x faster than pip). Triggers on: uv, venv, pip, pyproject, python environment, install package, dependencies.
85
84%
Does it follow best practices?
Impact
79%
1.29xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid description with excellent trigger term coverage and clear completeness, explicitly stating both what the skill does and when to use it. Its main weaknesses are the lack of specific concrete actions (it says 'environment management' but doesn't enumerate capabilities like creating venvs, installing packages, managing lockfiles) and some overlap risk with general Python/pip skills due to broad trigger terms.
Suggestions
Add specific concrete actions like 'create virtual environments, install packages, resolve dependencies, manage lockfiles, initialize projects with pyproject.toml'
Consider narrowing trigger terms to reduce conflict with general Python skills—e.g., clarify that this skill should be preferred over pip-based approaches when speed or uv-specific features are relevant
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Python environment management) and the tool (uv), and mentions a performance claim, but doesn't list specific concrete actions like 'create virtual environments, install packages, manage dependencies, sync lockfiles'. | 2 / 3 |
Completeness | Answers both 'what' (fast Python environment management with uv) and 'when' (explicit 'Triggers on:' clause with specific keywords). The trigger guidance is explicit and actionable. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger terms users would say: 'uv', 'venv', 'pip', 'pyproject', 'python environment', 'install package', 'dependencies'. These cover common variations well and match how users naturally phrase requests. | 3 / 3 |
Distinctiveness Conflict Risk | While 'uv' is distinctive, terms like 'pip', 'install package', and 'dependencies' could overlap with general Python development skills or package management skills. The description is somewhat specific to uv but the broad trigger terms increase conflict risk. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill that efficiently covers uv-based Python environment management. Its main strengths are concise table-based quick references, executable code examples, and good progressive disclosure to reference files. The only notable weakness is the project setup workflow, which could benefit from explicit validation steps and a more concrete pyproject.toml creation step.
Suggestions
Add explicit validation checkpoints to the Project Setup Checklist (e.g., verify venv activation with `which python`, verify install success with `uv pip list`)
Replace the vague '# Create pyproject.toml' comment in the checklist with a concrete command or reference to the template above
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It uses tables for quick reference, provides only essential commands without explaining what uv or virtual environments are, and respects Claude's existing knowledge. The 'When to Use' section is slightly unnecessary but brief enough not to significantly impact token efficiency. | 3 / 3 |
Actionability | Every section contains concrete, copy-paste ready commands and code. The pyproject.toml template is complete and usable, bash commands are executable, and the troubleshooting table maps specific errors to specific solutions. | 3 / 3 |
Workflow Clarity | The 'Project Setup Checklist' provides a reasonable sequence but lacks validation checkpoints — there's no step to verify the venv was created correctly, no check that the install succeeded, and the comment '# Create pyproject.toml' is vague rather than actionable. For a non-destructive workflow this is acceptable but not exemplary. | 2 / 3 |
Progressive Disclosure | Excellent structure with a concise overview in the main file and clear one-level-deep references to detailed patterns (pyproject-patterns.md, dependency-management.md, publishing.md). The 'See Also' section with related skills provides good navigation for discovery. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- NeverSight/skills_feed
- Commit
f772de4
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.