CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ruff-linter-formatter

Ruff como linter e formatter padrão para Python (substitui Flake8, Black, isort)

Quality

72%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/workflow/ruff/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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.

The body is highly actionable with executable commands, complete configuration examples, and clear integration steps for both new and existing projects. Weaknesses are mild verbosity (marketing claims and a rules legend Claude already knows) and the absence of an explicit fix→re-check feedback loop, plus reference tables that could be split out of SKILL.md.

Suggestions

Trim the '10–100x mais rápido' performance claim and the rules-prefix legend (E, F, I, N, W, UP, B) — Claude already knows these codes; keep only project-specific selections.

Add an explicit validation feedback loop after 'ruff check . --fix' (e.g. 'run ruff check . again and resolve remaining issues before committing') since batch fixes can leave unfixable violations.

Move the configuration options table and rules legend into a reference file (e.g. references/config.md) linked from SKILL.md to keep the overview lean.

DimensionReasoningScore

Conciseness

Mostly efficient, but includes padding Claude does not need: the '10–100x mais rápido' Rust marketing line, the rules-prefix legend explaining E/F/I/N/W/UP/B, and overlapping guidance repeated across 'Quando Usar' and 'Regras para os agentes'. Matches anchor 3; below 4 because several sections could be trimmed without losing information.

3 / 5

Actionability

Concrete, copy-paste-ready commands ('ruff check . --fix && ruff format .'), a complete pyproject.toml config block, and Makefile targets cover the common cases. Below anchor 5 due to minor gaps, e.g. the CI step says 'incluir ruff check e ruff format --check no pipeline' without a concrete pipeline example.

4 / 5

Workflow Clarity

Clear sequences exist (pre-commit flow, 4-step new-project setup) with a validation checkpoint ('garantir que ruff check . e ruff format . passem' before commit, plus --check in CI). Below anchor 5 because there is no explicit feedback loop for re-checking after --fix when unfixable issues remain.

4 / 5

Progressive Disclosure

Well-sectioned single-file skill with clearly signaled external doc links, but at ~125 lines it exceeds the under-50-line simple-skill case, and reference material (the options table and rules legend) is inlined where it could live in a separate file. Good structure with minor organization gaps — anchor 4.

4 / 5

Total

15

/

20

Passed

Description

65%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.

The description clearly establishes a niche with distinct trigger terms, but it states only the 'what' — the 'when to use' clause is entirely absent and no concrete actions are listed. Adding a 'Use quando...' clause and one or two concrete actions would lift the weakest dimensions.

Suggestions

Add an explicit trigger clause, e.g. 'Use quando trabalhar em projetos Python, ou quando o usuário mencionar lint, formatação, ou migração de Flake8/Black/isort para Ruff'.

Include one or two concrete actions in the description, such as 'executa ruff check --fix e ruff format' or 'configura [tool.ruff] em pyproject.toml'.

Add natural trigger variations users would say (lint, code style, qualidade de código) to improve trigger term coverage toward anchor 5.

DimensionReasoningScore

Specificity

Names the domain ('linter e formatter padrão para Python') and the tools it replaces ('substitui Flake8, Black, isort'), but lists no concrete actions such as checking, fixing, or configuring. Matches anchor 3 (domain plus role-level actions, not comprehensive); below 4 because no specific operations are stated, above 2 because it is not generic.

3 / 5

Completeness

The 'what' is clear (Ruff as the standard Python linter/formatter replacing three tools), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because the 'when' is entirely missing rather than merely imprecise.

3 / 5

Trigger Term Quality

Includes good natural keywords users would say: 'ruff', 'linter', 'formatter', 'python', plus tool names 'Flake8', 'Black', 'isort' that act as synonyms. Below anchor 5 because common variations like 'lint', 'code style', or 'code quality' are absent.

4 / 5

Distinctiveness Conflict Risk

Names a specific tool ('Ruff') with a clear niche (Python linting/formatting) and distinct trigger terms including the replaced tool names, giving minimal conflict risk with other skills. Matches anchor 5.

5 / 5

Total

15

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

fernandezbaptiste/cursor-multiagent-system

Path

skills/workflow/ruff/SKILL.md

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.