fix-members-short-description

Use when asked to fix short descriptions of Python type members.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/fix-members-short-description/SKILL.md

Quality

Content

72%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, well-structured instruction skill: it teaches exactly one transformation with a clear before/after example and precise edge-case rules, and it avoids padding. Its main weakness is the absence of any verification step for what is inherently a batch edit, and the noqa fallback is stated but not shown.

Suggestions

Add a verification step, e.g. after editing, re-scan each docstring to confirm the first sentence ends with the continuation backslash and no line exceeds 88 characters.

Show a compact example of the '# noqa: E501' fallback and of a first sentence starting on the same line as the opening triple quote, since both cases are asserted by rule only.

Trim the second code example to show just the continued first sentence rather than repeating the full class block.

Dimension	Reasoning	Score
Conciseness	The body is lean and every section earns its place (context, before/after example, goal, edge rules), but the second code example repeats the entire class block including the unchanged full-description lines when only the backslash continuation differs — a minor trim opportunity.	4 / 5
Actionability	Concrete before/after examples plus explicit rules (88-char limit, '# noqa: E501' fallback, same-line vs following-line start) give mostly executable guidance, but the noqa variant and the same-line-start case are covered by rule only, without an example — minor gaps.	4 / 5
Workflow Clarity	The single task is unambiguously stated, but this is a batch operation over all members of all types in a file or directory, and there is no validation/verification step (e.g., re-checking line lengths or docstring validity after edits), which caps workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	The skill is under 50 lines, needs no external references, and is organized into clear 'Inputs' and 'Instructions' sections, satisfying the simple-skill exception for full marks.	5 / 5
	Total	16 / 20 Passed

Description

62%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, correctly scoped, and uses the 'Use when...' pattern, but it is minimal: a single clause carries both the what and the when, and it lacks the trigger synonyms and concrete keyword variations that would make discovery reliable. It is solid but not comprehensive.

Suggestions

Add concrete trigger phrases and synonyms, e.g. 'Use when asked to fix short descriptions, docstring summaries, or first sentences of Python type members'.

Mention the key file/module context (e.g. 'in Python source files or docstrings') to strengthen trigger-term coverage.

Consider hinting at the transformation performed (breaking the first sentence across lines with backslash continuation) to differentiate it from generic docstring-linting skills.

Dimension	Reasoning	Score
Specificity	Names the domain ("Python type members", "short descriptions") and a single concrete action ("fix"), but does not list several specific actions or comprehensive coverage, matching the '1-2 concrete actions' anchor.	3 / 5
Completeness	Both what ("fix short descriptions of Python type members") and when ("Use when asked to fix...") are explicitly present, but the trigger phrasing is a single combined clause without concrete trigger phrases or keyword variations, so it falls short of the anchor-5 example.	4 / 5
Trigger Term Quality	Terms like "fix", "short descriptions", and "Python type members" are relevant, but common variations users would say ("docstrings", "summaries", "first line of docstring") are missing, matching the 'some relevant keywords but missing synonyms' anchor.	3 / 5
Distinctiveness Conflict Risk	The niche (docstring short-description formatting for Python type members) is fairly distinct, but it could plausibly overlap with generic docstring-formatting or linting skills, matching the 'mostly distinct; minor overlap risk' anchor.	4 / 5
	Total	14 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: flet-dev/flet
Path: .agents/skills/fix-members-short-description/SKILL.md
Commit: 9748de3

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