CtrlK
BlogDocsLog inGet started
Tessl Logo

common-best-practices

Enforce SOLID principles, guard-clause style, function size limits, and intention-revealing naming across all languages. Use when refactoring for readability, applying clean-code patterns, reviewing naming conventions, or reducing function complexity.

64

Quality

76%

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 ./.github/skills/common/common-best-practices/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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-organized, concise instruction skill with appropriately offloaded one-level references that all resolve to real files. Its only weakness is a stray empty "Priority: P0 (CRITICAL)" section header that mildly affects conciseness and workflow clarity.

Suggestions

Remove or fill the empty "## Priority: P0 (CRITICAL)" section header that currently has no content beneath it, as it adds noise and ambiguity.

Consider adding a one-line pointer under each reference link describing when to consult it (e.g. "consult CODE_STRUCTURE.md when reorganizing files/functions"), to sharpen navigation cues.

If applying these rules in a review/refactor loop, add a brief validate-then-proceed checkpoint (review -> flag violations -> confirm fix) to lift workflow clarity toward 5.

DimensionReasoningScore

Conciseness

Lean bullet-based content that assumes Claude's competence and avoids explaining what SOLID/KISS mean; the only blemish is a stray empty "Priority: P0 (CRITICAL)" section header that could be trimmed, keeping it just below the fully-lean 5-anchor.

4 / 5

Actionability

Concrete, specific rules ("Functions < 30 lines. Services < 600 lines. Utils < 400 lines.") and a clear anti-pattern list give actionable guidance; as an instruction-only skill the absence of executable code is acceptable, matching the 4-anchor with minor gaps.

4 / 5

Workflow Clarity

A single-purpose instructional skill with no destructive/batch operation, so the validation cap does not apply; the application action is largely unambiguous but the stray empty "Priority: P0" header adds slight ambiguity versus the 5-anchor.

4 / 5

Progressive Disclosure

A concise overview body with a References section that clearly signals two one-level-deep, descriptively-labeled references (CODE_STRUCTURE.md, EFFECTIVENESS.md), both verified to exist, matching the 5-anchor for clear navigation.

5 / 5

Total

17

/

20

Passed

Description

75%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 third-person, specific, and clearly pairs a concrete capability statement with an explicit Use-when trigger clause. It lands solidly at the 4-anchor across all dimensions, just short of the 5-anchor's comprehensive keyword/trigger coverage.

DimensionReasoningScore

Specificity

Names the clean-code domain plus several concrete actions ("SOLID principles, guard-clause style, function size limits, and intention-revealing naming") matching the anchor that lists several specific actions with minor coverage gaps.

4 / 5

Completeness

Both a clear "what" (enforce SOLID/guard-clause/size-limits/naming) and an explicit "when" ("Use when refactoring for readability...") are present and concrete, matching the 4-anchor rather than the 5-anchor's more exhaustive bullet-list trigger phrasing.

4 / 5

Trigger Term Quality

Good natural keyword coverage ("refactoring for readability, applying clean-code patterns, reviewing naming conventions, or reducing function complexity") with only a few synonyms (e.g. maintainability, code review) missing, matching the 4-anchor.

4 / 5

Distinctiveness Conflict Risk

Carves a distinct clean-code niche with specific triggers (SOLID, guard-clause, function-size limits) with only minor overlap risk against generic code-review skills, matching the 4-anchor.

4 / 5

Total

16

/

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.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
HoangNguyen0403/agent-skills-standard
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.