CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

python-style

Validate Python code against style and architectural conventions

Quality

64%

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 ./plugins/pragma/skills/python-style/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 a well-structured, actionable rule set with concrete commands and an exact output schema, weakened mainly by restated scope and a batch workflow lacking verification checkpoints. Tightening the repetition and adding a batch-completion/validation checkpoint would lift conciseness and workflow clarity.

Suggestions

De-duplicate the scope statement: keep the Scope Declaration and remove the overlapping 'Your task is to validate...' list and the repeated ruff/mypy note in Assumptions.

Add a verification checkpoint for the batch workflow, e.g. confirm all listed files were read and that emitted JSON validates against the schema before finishing.

Consider extracting the long architecture-rules block into a referenced file if the skill grows, to keep SKILL.md a lean overview.

DimensionReasoningScore

Conciseness

The rules are mostly tight, but scope is restated three times (Scope Declaration, the 'Your task is to validate' list, and the Assumptions section repeating the ruff/mypy point), which is unnecessary padding.

3 / 5

Actionability

It provides a copy-paste bash command for gathering changed files, an exact JSON output schema, and concrete rule examples like `str | None` not `Optional[str]` and repository-vs-service behavior, with only minor gaps.

4 / 5

Workflow Clarity

The gather-read-evaluate-categorize-emit sequence is clear with a pass/fail rule, but this is a batch file scan with no verification checkpoint, so the batch-operations cap holds at anchor 3.

3 / 5

Progressive Disclosure

No bundle files exist; the skill is a single well-sectioned file with clearly signaled one-level normative URL references and no nesting, fitting anchor 4.

4 / 5

Total

14

/

20

Passed

Description

53%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 is clear and domain-specific but minimal: it states what the skill does without any usage trigger and with limited action specificity. Adding a 'Use when...' clause and more concrete actions would raise it across completeness and specificity.

Suggestions

Add an explicit trigger clause, e.g. 'Use when reviewing or validating Python code for style and architectural conventions.'

List a few concrete validation actions (e.g. 'checks docstring style, type hints, exception chaining, and layer separation') to lift specificity from 3 to 4-5.

Include natural synonyms users might say ('lint', 'review', 'idioms') to improve trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain ('Python code') and the validation targets ('style and architectural conventions') but offers only one action across two areas rather than a list of specific actions, matching anchor 3.

3 / 5

Completeness

It gives a clear 'what' but no 'Use when...' or equivalent trigger guidance, so per the missing-trigger cap it cannot exceed anchor 3.

3 / 5

Trigger Term Quality

Relevant terms ('Validate Python code', 'style', 'architectural conventions') are present but technical, missing natural synonyms users would say like 'lint', 'review', 'check', or 'idioms'.

3 / 5

Distinctiveness Conflict Risk

It carves a Python-specific style-and-architecture niche with only minor overlap risk against closely related security or formatting skills, fitting anchor 4.

4 / 5

Total

13

/

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

peteski22/agent-pragma

Path

plugins/pragma/skills/python-style/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.