jbvc/python-standard-workflow
Standardize Python project setup and validation with uv, ruff, typos, and mypy. Use when creating a new Python project, normalizing an existing repository, adding Python quality tooling, or driving Python code to a clean lint, spelling, formatting, and type-check state through a repeatable uv-based workflow.
94
94%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
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 an excellent skill description that clearly communicates both what the skill does and when to use it. It names specific tools and concrete actions, includes a comprehensive 'Use when...' clause with multiple trigger scenarios, and occupies a distinct niche that minimizes conflict risk with other skills. The description is concise yet thorough, using appropriate third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Standardize Python project setup and validation', mentions specific tools (uv, ruff, typos, mypy), and describes concrete outcomes like 'clean lint, spelling, formatting, and type-check state through a repeatable uv-based workflow'. | 3 / 3 |
Completeness | Clearly answers both 'what' (standardize Python project setup and validation with specific tools) and 'when' with an explicit 'Use when...' clause covering four distinct trigger scenarios: creating new projects, normalizing existing repos, adding quality tooling, or driving code to a clean state. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Python project', 'uv', 'ruff', 'typos', 'mypy', 'lint', 'spelling', 'formatting', 'type-check', 'quality tooling', 'repository'. These cover a wide range of terms a user might naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Python-specific project setup using a specific toolchain (uv, ruff, typos, mypy). The combination of these specific tools and the focus on standardization/validation makes it very unlikely to conflict with generic Python or code quality skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%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, actionable skill that provides a clear multi-step workflow with concrete commands, validation checkpoints, and appropriate progressive disclosure. Its main weakness is mild verbosity in the applicability sections and some guidance that restates principles Claude already knows. Overall it is a strong skill that would effectively guide Claude through Python project standardization.
Suggestions
Trim or remove the 'Use This Skill When' and 'Do Not Use This Skill When' sections—these are routing concerns better handled by the YAML frontmatter description, saving ~15 lines of tokens.
Condense advisory bullets like 'Prefer real type checking over silencing errors' and 'Avoid adding broad ignores unless the failure is understood' into a single concise principle statement.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some sections that could be tightened—'Use This Skill When' and 'Do Not Use This Skill When' sections add moderate value but consume tokens on guidance Claude could infer. Some bullet points restate obvious principles (e.g., 'Prefer real type checking over silencing errors'). | 2 / 3 |
Actionability | Provides concrete, executable bash commands throughout (uv add, ruff format, ruff check, typos, mypy), a fixed gate order, and specific ruff rule sets (E, F, I, B, UP). The commands are copy-paste ready and the guidance is specific enough to act on immediately. | 3 / 3 |
Workflow Clarity | The six-step workflow is clearly sequenced with an explicit fixed order for the quality gate, a dedicated 'Fix Failures, Then Re-Run' step that serves as a feedback loop, and clear completion criteria that prevent premature success reporting. The inspect-before-changing step adds appropriate caution. | 3 / 3 |
Progressive Disclosure | The skill provides a clear overview with well-organized sections, and appropriately references external files (references/pyproject-template.md, scripts/run_quality_gate.sh) for detailed content. References are one level deep and clearly signaled in a dedicated 'Reference Files' section. | 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.
Reviewed
Table of Contents