CtrlK
BlogDocsLog inGet started
Tessl Logo

fix-members-short-description

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

57

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

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

Quality

Content

72%

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

The body is concise, well-organized, and appropriately scoped for a simple single-task skill, but it lacks an explicit wrapping algorithm and any verification step for what is effectively a batch edit. Adding a validation checkpoint and a concrete wrapping rule would raise the actionability and workflow scores.

Suggestions

Add an explicit verification step for the batch edit, e.g. re-run a line-length check or docstring parser after applying fixes to confirm every docstring is valid.

Specify the wrapping algorithm concretely (e.g., break the first sentence at the latest whitespace before 88 chars and join continuation lines with ` \`), so the transformation is unambiguous.

Clarify what counts as the "first sentence" boundary (period ending the first sentence) to remove ambiguity when applying the fix.

DimensionReasoningScore

Conciseness

The body is lean, assumes Claude knows docstrings and dataclasses, and every line (examples, the 88-char rule, the noqa fallback) earns its place, matching the score-3 anchor for lean, efficient content.

3 / 3

Actionability

Guidance is specific (concatenate with backslash, 88-char limit, `# noqa: E501` on the closing `"""` line) with illustrative examples, but it lacks an explicit wrapping algorithm and copy-paste executable code, fitting the score-2 anchor of concrete-but-incomplete guidance.

2 / 3

Workflow Clarity

The single task and scope (all members of all types) are stated, but this is a batch operation with no validation or verification step mentioned, so per the batch-operation guideline workflow clarity is capped at 2.

2 / 3

Progressive Disclosure

The skill is under 50 lines, needs no external references, and is organized into clear Inputs/Instructions sections with examples, matching the score-3 allowance for short single-purpose skills.

3 / 3

Total

10

/

12

Passed

Description

57%

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 concise and targets a distinct niche with an explicit trigger, but it is thin on what the skill actually does and on trigger-term coverage. Expanding the capability description would lift it above the mid range.

Suggestions

Add a clause describing the concrete action, e.g. "Use when asked to fix short descriptions of Python type members — wraps multi-line first sentences with backslash continuations and enforces an 88-char line limit."

Include more natural trigger variations such as "docstring short descriptions", "member docstrings", or "first line of a docstring" to broaden coverage.

Briefly signal the scope (works on properties, methods, classes, enums) so the "what" is not just a restatement of the trigger.

DimensionReasoningScore

Specificity

Names the domain ("Python type members") and a single action ("fix short descriptions"), but does not list multiple concrete actions, matching the score-2 anchor of naming domain and some actions without being comprehensive.

2 / 3

Completeness

The "when" is explicit ("Use when asked to fix short descriptions of Python type members."), but the "what" merely restates the trigger without describing what the fix entails, so it does not clearly answer both what and when.

2 / 3

Trigger Term Quality

Phrases like "fix short descriptions" and "Python type members" are natural terms a user might say, but coverage is limited with no common variations, matching the score-2 anchor rather than broad coverage.

2 / 3

Distinctiveness Conflict Risk

Targeting "short descriptions of Python type members" is a clear, narrow niche with a distinct trigger unlikely to conflict with other skills, matching the score-3 anchor.

3 / 3

Total

9

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
flet-dev/flet
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.