CtrlK
BlogDocsLog inGet started
Tessl Logo

minimal-code-discipline

YAGNI-ladder coding discipline for writing changes — existence-first, reuse before writing, dependency ladder, shortest correct diff, with non-negotiables that must never be minimized away

61

Quality

72%

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 ./skills/minimal-code-discipline/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 concise, well-organized instruction skill with actionable principles and an explicit verification checklist; its only weak spot is the absence of a concrete worked example or stricter step sequencing.

DimensionReasoningScore

Conciseness

The body is lean throughout: each principle is a single crisp sentence, it assumes Claude's intelligence (no explanation of what YAGNI or a dependency is), and every line earns its place.

5 / 5

Actionability

Guidance is concrete and specific for an instruction-only skill ('Reach for the standard library first, then platform-native capability, then an already-installed dependency'), with the dependency ladder acting as an ordered procedure; minor gaps remain as it stops short of worked examples.

4 / 5

Workflow Clarity

The Verification section provides an explicit completion checklist with validation checkpoints, and the Non-Negotiables act as guards; it is not a strict linear sequence, so a couple of sequencing checkpoints are implicit rather than numbered.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references, and content is organized into clearly headed sections (When to Use, When Not to Use, The Discipline, Non-Negotiables, Verification), satisfying the simple-skill exception.

5 / 5

Total

18

/

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 is specific and reasonably distinct, but it lacks an explicit 'when to use' trigger clause and relies on some jargon over natural user phrasings.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when the user asks for a minimal, lean, YAGNI, or smallest-possible-diff change.'

Surface common user phrasings ('minimal', 'lean', 'smallest possible diff') alongside the technical terms to improve trigger-term quality.

Tighten 'with non-negotiables that must never be minimized away' — it adds length without a concrete capability a user would search for.

DimensionReasoningScore

Specificity

Lists several concrete actions/principles ('existence-first, reuse before writing, dependency ladder, shortest correct diff') rather than vague language, though the items are disciplines rather than a comprehensive action catalog.

4 / 5

Completeness

The 'what' is clear (a YAGNI-ladder coding discipline for writing changes), but there is no explicit 'Use when...' trigger clause, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

'YAGNI-ladder' and 'shortest correct diff' give some natural trigger terms, but common user phrasings like 'minimal', 'lean', or 'smallest possible diff' are absent and several phrases ('existence-first', 'dependency ladder') lean toward jargon.

3 / 5

Distinctiveness Conflict Risk

The YAGNI-ladder framing carves a fairly distinct niche from general coding skills, with only minor overlap risk against closely related code-review or cleanup skills.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
Yeachan-Heo/oh-my-claudecode
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.