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

69%

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 ./skills/code-quality/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 dense, highly actionable standards document with no wasted tokens, concrete directives, and an exemplary progressive-disclosure split between universal rules and verified stack references. Its only real costs are compression that borders on opaque in places and mild redundancy between the guard-proofing and testing sections.

DimensionReasoningScore

Conciseness

The body is dense rule-per-sentence prose with no padding and no explanations of concepts Claude already knows — e.g. "One lifetime, one owner" and "A defect has a class" state rules, not tutorials. Minor trimming is possible (the must-fail control mechanics are restated across § Prove Your Guards and § Tests, and some sentences are compressed to the edge of readability), so anchor 4 fits better than 5.

4 / 5

Actionability

For an instruction-only skill the guidance is unusually concrete: exact settings ("under git, `text eol=lf` for text a test parses"), named variables ("`XDG_CONFIG_HOME`, `XDG_DATA_HOME`, `XDG_STATE_HOME` and `XDG_CACHE_HOME`"), and a copy-ready output template ("code-quality: [misled|missing|not followed]: [reason]; owner: [guidance or route]"). Not 5 because a substantial share of the rules are judgment-level principles ("state what it protects and for whom") without worked examples showing a rule applied.

4 / 5

Workflow Clarity

The procedures that exist are clearly sequenced with safeguards: "Before changing code, load the reference for each affected stack under § Language Discipline", the must-fail control ("Run only the rows under proof, by name", "Mutate a disposable copy of the source outside the worktree"), and the finding-evaluation decision tree (misled / missing / not followed with owners). Not 5 because the skill is a rulebook rather than an end-to-end workflow, and applying the standards during a task has no overall ordering beyond the reference-loading step.

4 / 5

Progressive Disclosure

Structure is exactly the anchor-5 pattern: universal rules inline, stack specifics split into four real one-level-deep reference files ([references/rust.md], [references/bash.md], [references/typescript.md], [references/ui.md] — all verified present), each clearly signaled with an explicit load condition ("Load only the references for the code being changed") and per-stack bullet links. In-document navigation via § cross-references (§ Tests, § Core Principle) is consistent.

5 / 5

Total

17

/

20

Passed

Description

50%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 a strong, explicit trigger clause with good natural keyword coverage, but it says nothing about what the skill actually contains or does, and its deliberately universal scope creates high conflict risk with other coding skills. It reads as half of a good description — the 'when' without the 'what'.

Suggestions

State the skill's function before the trigger clause, e.g. "Applies code-quality standards for correctness, structure, guards, and tests... Load for any coding or development task", so the description answers both 'what' and 'when'.

Add distinguishing terms tied to the skill's actual content (quality standards, review findings, test contracts, ownership rules) so it does not collide with every other coding skill on "writing, changing, fixing, refactoring, or testing".

Include the natural trigger terms users say that are currently missing, such as "debugging" or "implementing", to round out keyword coverage.

DimensionReasoningScore

Specificity

"writing, changing, fixing, refactoring, or testing code or scripts in any language" lists several distinct task actions with minor gaps. Not 5 because the actions are generic verbs on "code or scripts" rather than concrete capabilities (nothing like the anchor's "fill forms, merge documents"); not 3 because coverage goes well beyond 1-2 actions.

4 / 5

Completeness

The description is entirely a trigger clause — "Load for any coding or development task in any repository" — and never states what the skill provides (code-quality standards, review rules, test contracts). This matches anchor 2 ("only 'when' is present without 'what'"); it cannot be 3 because anchor 3 requires a clear 'what', which is absent.

2 / 5

Trigger Term Quality

Natural keywords users would say are present: "coding", "writing", "fixing", "refactoring", "testing", "scripts". A few common natural terms are missing (e.g., "debugging", "implementing", "code review"), so it fits anchor 4 rather than the comprehensive synonym/extension coverage of 5.

4 / 5

Distinctiveness Conflict Risk

"any coding or development task in any repository" and "in any language" claim maximal breadth, so it would trigger alongside virtually any other coding-related skill. Anchor 2 ("very broad; high overlap risk with many similar skills") is the best fit; not 1 only because it is confined to the coding domain rather than being cross-domain generic.

2 / 5

Total

12

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

13

/

16

Passed

Repository

vanillagreencom/kendex

Path

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.