CtrlK
BlogDocsLog inGet started
Tessl Logo

vibe-python-style

Python coding conventions for Mistral Vibe. Use when writing, reviewing, or refactoring Python code in the Vibe codebase. Covers style, type hints, imports, Pydantic patterns, logging, error handling, and file I/O.

67

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

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

A tight, actionable conventions reference with concrete commands and a well-sequenced import-deferral validation workflow. It is self-contained and well-structured, with only minor trimming and splitting opportunities.

DimensionReasoningScore

Conciseness

Dense, lean bullet lists that assume Claude's competence; a few parenthetical rationales (e.g. logging %s explanation) could be trimmed but mostly earn their place.

4 / 5

Actionability

Concrete module paths, exact API names, and runnable commands ('uv run python scripts/check_import_contracts.py', 'from vibe.observability.logging import logger'); lacks full copy-paste code blocks but guidance is specific and executable.

4 / 5

Workflow Clarity

The TYPE_CHECKING deferral section gives a clear pre-merge sequence with explicit gated (TC004, check_import_contracts) vs informational (suggest_lazy_imports) checkpoints; the rest is convention reference rather than multi-step workflow.

4 / 5

Progressive Disclosure

Well-organized into clear sections (Style, Typing & imports, Pydantic, Logging & errors, File I/O) with no external references needed; the detailed TYPE_CHECKING subsection could arguably live in its own file but is coherent inline.

4 / 5

Total

16

/

20

Passed

Description

88%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that clearly states capabilities and explicit use-conditions with concrete trigger phrases. Minor improvements possible by adding file-extension synonyms (.py) to widen natural trigger coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('writing, reviewing, or refactoring Python code') and comprehensively enumerates coverage areas (style, type hints, imports, Pydantic patterns, logging, error handling, file I/O).

5 / 5

Completeness

Explicitly answers both what ('Python coding conventions for Mistral Vibe... Covers...') and when ('Use when writing, reviewing, or refactoring Python code in the Vibe codebase') with concrete triggers.

5 / 5

Trigger Term Quality

Natural phrases like 'writing, reviewing, refactoring Python code' are present, but common synonyms and extensions such as '.py files' or 'Python scripts' are missing.

4 / 5

Distinctiveness Conflict Risk

Scoping to 'Mistral Vibe' codebase gives a clear niche, but the trigger phrasing around generic Python coding could overlap with broader Python style skills.

4 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

14

/

16

Passed

Repository
mistralai/mistral-vibe
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.