python-env

Fast Python environment management with uv (10-100x faster than pip). Triggers on: uv, venv, pip, pyproject, python environment, install package, dependencies.

1.29x

Quality

—

Does it follow best practices?

Impact

79%

1.29x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill body is concise and highly actionable, built almost entirely from executable commands and tables. Its weaknesses are the missing validation step in the project-setup workflow and the broken reference files that undermine the progressive-disclosure structure.

Suggestions

Add an explicit verification step to the Project Setup Checklist (e.g., run 'uv pip list' or 'uv run python -c "import httpx"' and confirm expected output before proceeding).

Create the referenced ./references/ files or remove the broken links, since pointing to nonexistent files breaks the disclosure path.

Add a brief feedback loop in Troubleshooting for the dependency-conflict case (run 'uv pip compile --resolver=backtracking', re-check the lockfile, retry) to convert error guidance into a validate-fix-retry workflow.

Dimension	Reasoning	Score
Conciseness	The body is lean and command/table-driven with almost no prose, assumes Claude already knows what venvs and pyproject files are, and every section earns its tokens.	3 / 3
Actionability	It provides fully executable, copy-paste-ready commands throughout (e.g., 'uv venv --python 3.11', 'uv pip install "django>=4.0,<5.0"') with concrete examples for each task.	3 / 3
Workflow Clarity	The 'Project Setup Checklist' gives a clear sequence but lacks any explicit validation or verification checkpoint, so it sits at the sequence-present-but-checkpoints-implicit level rather than 3.	2 / 3
Progressive Disclosure	References are clearly signaled one level deep under 'Additional Resources', but the referenced files (./references/pyproject-patterns.md, dependency-management.md, publishing.md) do not exist, so the disclosure targets are broken.	2 / 3
	Total	10 / 12 Passed

Description

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.

The description cleanly states purpose and provides explicit, natural trigger terms, giving it strong completeness and trigger quality. It is held back by a lack of enumerated concrete actions and by generic triggers that invite overlap with adjacent skills.

Suggestions

List two or three concrete actions in the description (e.g., 'Create virtual environments, install and lock dependencies, run scripts with uv') to raise specificity.

Qualify the generic triggers so they bind to Python (e.g., 'python package install', 'pip-to-uv migration') to reduce conflict with non-Python packaging skills.

Replace the marketing claim '10-100x faster than pip' with the concrete capability it implies, since buzzword-style over-claims are penalized.

Dimension	Reasoning	Score
Specificity	Names a concrete domain and tool ('Python environment management with uv') but does not enumerate multiple specific actions (e.g., create venvs, install/lock dependencies), so it falls short of the score-3 anchor listing several concrete actions.	2 / 3
Completeness	It states what the skill does ('Fast Python environment management with uv') and provides explicit 'when' trigger guidance via the 'Triggers on:' clause, satisfying both halves required for a 3.	3 / 3
Trigger Term Quality	The explicit 'Triggers on: uv, venv, pip, pyproject, python environment, install package, dependencies' covers natural terms a user would actually say when needing this skill.	3 / 3
Distinctiveness Conflict Risk	The uv niche is fairly distinct, but generic triggers like 'pip', 'install package', and 'dependencies' could overlap with other packaging or language-ecosystem skills, so it does not reach the clear-distinct-niche anchor of 3.	2 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: NeverSight/skills_feed
Commit: 26d37ce

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.