python

Python development with ruff, mypy, pytest - TDD and type safety

Quality

57%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/python/SKILL.md

Quality

Content

65%

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

The body is highly actionable with executable code and config throughout, but it is a long monolithic reference document lacking progressive disclosure and any explicit multi-step workflow with validation checkpoints.

Suggestions

Move the full GitHub Actions and pre-commit YAML into reference files (e.g., references/ci.yml) linked from the body to improve progressive disclosure and conciseness.

Add an explicit multi-step workflow with validation checkpoints (e.g., 'lint -> type-check -> test -> fix and re-run on failure') for the development loop.

Trim or summarize the CI/pre-commit configs inline, keeping only the essential directives, to reduce token volume.

Dimension	Reasoning	Score
Conciseness	The body is code-forward with no patronizing concept explanations, but the full GitHub Actions and pre-commit YAML configs are verbose reference material that could be tightened or externalized.	2 / 3
Actionability	It provides fully executable, copy-paste-ready guidance: pyproject.toml config, pytest tests, CI workflow, pre-commit hooks, and concrete Pydantic/DI/Result examples.	3 / 3
Workflow Clarity	Content is organized into sections, but there is no sequenced multi-step workflow with explicit validation checkpoints or feedback loops; the CI pipeline has only implicit validation.	2 / 3
Progressive Disclosure	Sections are well-organized, but the file is monolithic (~210 lines, all inline) with no bundle files or external references, and content like the CI/pre-commit configs that could be separate remains inline.	2 / 3
	Total	9 / 12 Passed

Description

50%

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 identifies a clear Python tooling niche with named tools and methodology, but it reads as a tag list rather than a complete trigger-rich description and lacks an explicit 'Use when...' clause.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when writing, linting, type-checking, or testing Python code') to raise completeness and trigger quality.

Reframe the description around concrete actions (e.g., 'Lint, type-check, and test Python code with ruff, mypy, and pytest using TDD') instead of the vague term 'development'.

Include natural trigger variations users would say (e.g., 'Python files', 'pyproject.toml', 'pytest', 'type hints') to improve trigger-term coverage and distinctiveness.

Dimension	Reasoning	Score
Specificity	Names the domain ('Python development') and concrete tools (ruff, mypy, pytest) plus methodology (TDD, type safety), but 'development' is not a concrete action and the actions are not comprehensive.	2 / 3
Completeness	It states what the skill does but includes no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 2 per the rubric guidelines.	2 / 3
Trigger Term Quality	Relevant natural terms (Python, pytest, mypy, TDD) appear, but they are framed as a tag list rather than natural trigger phrasing and miss common variations.	2 / 3
Distinctiveness Conflict Risk	It targets a specific Python+toolchain niche, but the broad phrase 'Python development' could still overlap with a general coding skill.	2 / 3
	Total	8 / 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: alinaqi/claude-bootstrap
Path: skills/python/SKILL.md
Commit: bb6195f

Reviewed: 6 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.