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 that clearly communicates the tool (uv) and provides explicit trigger terms, making it easy for Claude to know when to select it. Its main weaknesses are the lack of specific concrete actions (what exactly can it do beyond 'environment management'?) and some overlap risk with broader Python development skills due to generic trigger terms like 'pip' and 'dependencies'.
Suggestions
Add specific concrete actions like 'create virtual environments, install packages, manage lockfiles, resolve dependencies, initialize Python projects' to improve specificity.
Consider narrowing generic triggers like 'pip' and 'dependencies' by adding qualifiers, or note that this skill should be preferred over general pip workflows to reduce conflict risk.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Python environment management) and the tool (uv), and mentions a performance claim (10-100x faster than pip), 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' (explicitly lists trigger terms with 'Triggers on:' clause), providing clear guidance for when Claude should select this skill. | 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 of how users would phrase requests related to Python environment management. | 3 / 3 |
Distinctiveness Conflict Risk | While 'uv' and 'pyproject' are distinctive, terms like 'pip', 'install package', and 'dependencies' are quite broad and could overlap with general Python development skills or package management skills not specific to uv. | 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 Python environment management with uv. Its greatest strengths are conciseness and progressive disclosure, with clear tables and executable commands throughout. The main weakness is the project setup workflow, which could benefit from explicit validation steps and a more concrete pyproject.toml creation step.
Suggestions
Add a validation step to the Project Setup Checklist (e.g., 'Verify: `uv run python --version`' after venv creation, or check that `uv pip list` shows expected packages).
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 verification that the venv was created correctly, no check that installations 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 and quick-reference tables up front, followed by well-signaled one-level-deep references to detailed patterns (pyproject-patterns.md, dependency-management.md, publishing.md). The 'See Also' section provides clear navigation to related skills. | 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
9f4534c
- 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.