CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

code-quality

Load for any coding or development task in any repository: writing, changing, fixing, refactoring, or testing code or scripts in any language.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/code-quality/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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.

This is a well-built instruction-only skill: dense, unpadded rules with many concrete directives and a clean per-stack reference structure that is loaded conditionally. The main weaknesses are a very long inline body that could shed some test-specific detail into references, and a must-fail-control procedure split across two cross-referenced sections.

DimensionReasoningScore

Conciseness

The body is dense rule prose with no padding and no explanation of concepts Claude already knows; sentences like "A test is kept for the protection it gives, judged against its cost" carry rules per token. Not 5 because a few passages (e.g. the multi-clause check-selection rule in § Tests) are convoluted and could be tightened; not 3 because verbosity is minor, not a pattern.

4 / 5

Actionability

Concrete, executable specifics appear throughout: git attributes "text eol=lf", "binary", "-text" for fixtures, the four XDG variables a HOME-replacing test must set, the literal finding-line format in a code block, and conditional reference loading per stack. Not 5 because sections like Core Principle state principles rather than directives an agent can directly execute; not 3 because most guidance is specific and actionable.

4 / 5

Workflow Clarity

The one multi-step process — must-fail controls — is sequenced with explicit mechanics (run only named rows, mutate a disposable copy outside the worktree, remove it after) and cross-linked between § Prove Your Guards and § Tests; "Load only the references for the code being changed" gives a clear conditional loading rule. Not 5 because the control procedure is split across two sections rather than presented as one ordered sequence; not 3 because no validation gap exists for the operations it governs.

4 / 5

Progressive Disclosure

Four one-level-deep references (rust.md, bash.md, typescript.md, ui.md — all present in the bundle) are clearly signaled with when each applies, and the body is well-sectioned. Not 5 because the ~19KB body inlines test minutiae (process-id parsing, HOME/XDG handling) that could live in a reference; not 3 because structure and reference signaling are clearly better than adequate.

4 / 5

Total

16

/

20

Passed

Description

58%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 has an explicit, natural trigger clause with good action verbs, but it defines only when to load the skill, never what the skill provides (code-quality rules and standards). Its deliberate catch-all scope creates high conflict risk with other development-related skills.

Suggestions

State the capability explicitly, e.g. "Applies code-quality rules for correctness, structure, testing, and cleanup. Load for any coding or development task..." so the description answers both what and when.

Narrow the scope claim (e.g. "when changing code in a repository") or name the distinct niche (quality rules/standards) to reduce overlap with language- and task-specific skills.

Add one or two common trigger synonyms such as "debugging" or "code review" if those tasks are intended to invoke the skill.

DimensionReasoningScore

Specificity

"writing, changing, fixing, refactoring, or testing code or scripts in any language" lists several concrete actions, but these name trigger tasks rather than the skill's own capabilities, which are never described. Not 5 because coverage of what the skill does is incomplete; not 3 because the enumerated actions go beyond 1-2.

4 / 5

Completeness

The "when" is explicit ("Load for any coding or development task in any repository"), but the "what" is only implied through the skill name — the description never states what the skill does once loaded. It sits between anchor 3 and 4; the missing capability statement pulls it to 3, and the strong explicit trigger keeps it above 2.

3 / 5

Trigger Term Quality

"coding", "development task", "fixing", "refactoring", "testing code or scripts" are phrases users naturally say. Not 5 because common variations such as "debugging", "building", or "code review" are missing; not 3 because keyword coverage is good, not partial.

4 / 5

Distinctiveness Conflict Risk

"any coding or development task in any repository... in any language" is maximally broad and would trigger for virtually every coding request, overlapping language-specific skills, testing skills, and review skills. Matches anchor 2 (very broad, high overlap risk); not 3 because no scoping qualifier narrows it at all.

2 / 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

metadata_version

'metadata.version' is missing

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

14

/

16

Passed

Repository

vanillagreencom/kendex

Path

.agents/skills/code-quality/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.