managing-packages
Manages Python package dependencies. Use when adding, upgrading, removing, or syncing Python/pypi packages in projects or libs.
95
93%
Does it follow best practices?
Impact
99%
1.52xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
100%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 strong, well-crafted description that concisely covers what the skill does and when to use it. It uses third person voice, lists specific actions, includes natural trigger terms, and occupies a clear niche. The description is concise without being vague.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'adding, upgrading, removing, or syncing' Python package dependencies. These are clear, actionable operations. | 3 / 3 |
Completeness | Clearly answers both 'what' (manages Python package dependencies) and 'when' (explicit 'Use when adding, upgrading, removing, or syncing Python/pypi packages in projects or libs'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'Python', 'package', 'dependencies', 'adding', 'upgrading', 'removing', 'syncing', 'pypi', 'projects', 'libs'. Good coverage of terms a user would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Python package dependency management specifically, with distinct triggers like 'pypi', 'dependencies', 'syncing packages'. Unlikely to conflict with general Python coding skills or other language package managers. | 3 / 3 |
Total | 12 / 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-crafted, lean skill that provides exactly the information Claude needs to manage Python packages with uv. It excels at conciseness and actionability with concrete, executable commands and project-specific paths. The only minor weakness is that the commit step in Notes could be better integrated as a post-operation verification checkpoint.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line earns its place. No unnecessary explanations of what uv is or how package managers work. The project paths list is project-specific knowledge Claude wouldn't have, and the notes are minimal and essential. | 3 / 3 |
Actionability | All commands are concrete, copy-paste ready bash commands with clear placeholders. Each operation (add, upgrade, remove, sync, dev dependency) has an explicit executable command. | 3 / 3 |
Workflow Clarity | This is a collection of independent commands rather than a multi-step workflow, which is appropriate for the task. However, the notes mention committing both pyproject.toml and uv.lock but don't integrate this as a verification step after add/remove/upgrade operations, which is a minor gap for a workflow involving dependency changes. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines with no need for external references, the content is well-organized with clear sections (Commands, Project paths, Notes). The structure is appropriate for the scope. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- SpecterOps/Nemesis
- Commit
432d081
- 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.