python-code-quality
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".
Install with Tessl CLI
npx tessl i github:jjjermiah/dotagents --skill python-code-quality100
Does it follow best practices?
Validation for skill structure
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 clearly identifies the specific tools (Ruff, ty), lists concrete actions, provides explicit 'Use when...' guidance with multiple trigger scenarios, and includes natural example phrases users would actually say. The description is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'configuring Ruff rules', 'setting up ty type checking', '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 with explicit 'Use when...' clause listing specific 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 file that provides comprehensive, actionable guidance for Python code quality tooling. It efficiently covers configuration for multiple scenarios (single package, workspace, strict mode) with complete, executable examples. The clear YOU MUST/NEVER sections and cross-references to related skills demonstrate thoughtful design.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing configuration examples without explaining what linting or type checking are. Every section delivers actionable config or commands without padding. | 3 / 3 |
Actionability | Provides complete, copy-paste ready TOML configurations for both Ruff and ty, executable bash commands, and concrete pixi task definitions. Examples are fully executable, not pseudocode. | 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 auto-fix vs unsafe-fixes. The YOU MUST/NEVER sections provide clear guardrails. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from overview to specific configs. References to detailed docs (ruff-rules.md, ty-config.md) are clearly signaled with load-on-demand guidance. Context7 integration for up-to-date info is well-placed. | 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.
- 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.