CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

auto-docstring-rules

Enforces dlt docstring conventions. Use when writing or modifying docstrings, classes, or function signatures in Python files.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/auto-docstring-rules/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 maximally concise redirect stub that delegates everything to an external repo path. While token-efficient, it provides no actionable content of its own: the referenced file is outside the bundle, "Use" is ambiguous, and "regardless of path setting" is unexplained, leaving the reader unable to act confidently from the skill alone.

Suggestions

State the action concretely, e.g. "Before writing or modifying a docstring, read @.claude/rules/docstrings.md and apply its conventions" — 'Use' alone is ambiguous about whether to read, apply, or validate.

Bundle the conventions file (e.g. in references/) or inline the core rules, since .claude/rules/docstrings.md lives outside the skill and is not part of the bundle, making the skill break if that path moves.

Explain or drop "regardless of path setting" — the clause is cryptic without context; either clarify what path setting it overrides or remove it.

DimensionReasoningScore

Conciseness

The body is a single lean line — "Use @.claude/rules/docstrings.md regardless of path setting" — with no padding and no explanation of concepts Claude already knows. Every token earns its place; this matches the anchor for lean and efficient content.

5 / 5

Actionability

The only guidance is a pointer to an external file with no code, commands, or statement of what to do with it; the referenced file is not part of this skill's bundle (no references/ directory exists). This is minimal concrete guidance missing the specific steps to execute — anchor 2, not 3, since almost nothing is executable from the body itself.

2 / 5

Workflow Clarity

The single action (use the rules file) is present but ambiguous — "Use" never says whether to read, apply, or validate against it, and "regardless of path setting" is cryptic without context. Under the simple-skill exception this could be 5 only if the action were unambiguous; it is not, so 3 fits.

3 / 5

Progressive Disclosure

The body is a one-level-deep pointer, but it targets a path outside the skill bundle (.claude/rules/docstrings.md does not exist in this skill's directory tree), with no signaling of the file's contents and no fallback. Structure exists but is weakly organized and fragile — anchor 3.

3 / 5

Total

13

/

20

Passed

Description

70%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 concise, well-structured description with an explicit and fairly specific 'Use when' clause and a distinct dlt-scoped niche. Its main weakness is an abstract 'what' — "Enforces dlt docstring conventions" leaves the actual capability vague — plus missing a few natural trigger synonyms like ".py" or "methods".

Suggestions

Make the 'what' concrete: state what enforcing involves, e.g. "Checks docstrings against dlt's docstring conventions and fixes violations" instead of the generic "Enforces dlt docstring conventions".

Add natural trigger variations such as ".py files", "methods", "modules", or "docstring style" to broaden keyword coverage.

Clarify scope boundaries, e.g. whether it applies to new docstrings only or also audits existing ones, to sharpen distinctiveness from general Python style skills.

DimensionReasoningScore

Specificity

"Enforces dlt docstring conventions" names the domain (dlt docstrings) and states a single action, but "enforces" is generic — it never says what is actually done (checking, writing, fixing, formatting). Matches anchor 3 (domain plus 1-2 actions, not comprehensive) rather than 4, which requires several specific actions.

3 / 5

Completeness

Both parts are present: an explicit "Use when writing or modifying docstrings, classes, or function signatures in Python files" trigger and a stated 'what' ("Enforces dlt docstring conventions"). Falls short of 5 because the 'what' is abstract — what enforcing entails is never made concrete.

4 / 5

Trigger Term Quality

"docstrings, classes, function signatures, Python files" are natural terms users would say, giving good keyword coverage. Not 5 because common variations like ".py", "methods", "modules", or "docstring style" are missing.

4 / 5

Distinctiveness Conflict Risk

"dlt docstring conventions" carves out a clear niche that is mostly distinct, but the trigger terms ("docstrings", "Python files") could overlap with general Python linting/style skills. Anchor 4 (mostly distinct, minor overlap risk with closely related skills) fits best.

4 / 5

Total

15

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

dlt-hub/dlt

Path

.claude/skills/auto-docstring-rules/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.