Python code quality with Ruff linting/formatting and ty type checking. Use when configuring Ruff rules, setting up ty type checking, writing pyproject.toml quality config, creating pixi quality tasks, enforcing type annotations, or fixing lint errors—e.g., "set up ruff and ty", "configure Python linting", "add type checking to project", "fix ruff violations".
100
100%
Does it follow best practices?
Impact
100%
1.31xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
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 hits all the marks. It uses third person voice, provides specific concrete actions, includes a comprehensive 'Use when...' clause with natural trigger terms and example phrases, and is clearly distinguishable from other skills through its focus on specific tools (Ruff, ty, pixi).
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Ruff linting/formatting', 'ty type checking', 'configuring Ruff rules', 'writing pyproject.toml quality config', 'creating pixi quality tasks', 'enforcing type annotations', 'fixing lint errors'. | 3 / 3 |
Completeness | Clearly answers both what (Python code quality with Ruff linting/formatting and ty type checking) and when (explicit 'Use when...' clause with multiple trigger scenarios and example user phrases). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'ruff', 'ty', 'Python linting', 'type checking', 'pyproject.toml', 'lint errors', 'ruff violations', plus concrete example phrases like 'set up ruff and ty', 'configure Python linting'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific tool names (Ruff, ty, pixi) and clear niche (Python code quality tooling). Unlikely to conflict with generic coding or documentation skills due to explicit tool-specific triggers. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill that efficiently covers Python code quality tooling with Ruff and ty. It provides complete, actionable configurations with clear workflow guidance, appropriate use of tables for quick reference, and well-organized progressive disclosure through referenced files. The YOU MUST/NEVER sections effectively communicate critical constraints.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, using tables for quick reference, providing executable config blocks without explaining what linting or type checking are, and assuming Claude understands Python tooling concepts. | 3 / 3 |
Actionability | Provides complete, copy-paste ready TOML configurations for both Ruff and ty, executable pixi task definitions, and specific commands for fixing violations. All examples are directly usable. | 3 / 3 |
Workflow Clarity | Clear sequencing with explicit ordering (format BEFORE check), validation through the `qc` task chain, and specific guidance on when to use each tool. The YOU MUST/NEVER sections provide clear guardrails. | 3 / 3 |
Progressive Disclosure | Well-structured with quick overview tables, standard configs first then extended configs, and clear one-level-deep references to detailed rule documentation in the references folder. | 3 / 3 |
Total | 12 / 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.
b74de5e
Table of Contents
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.