CtrlK
BlogDocsLog inGet started
Tessl Logo

minimalist

Use when the user asks to write code efficiently, avoid over-engineering, reduce dependencies, or prevent unnecessary abstractions. Enforces a strict efficiency ladder: YAGNI, reuse, stdlib, native platform, existing deps — before writing any new code.

75

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

The risk profile of this skill

The canonical home for this skill is minimalist in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

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

A tightly written, single-purpose behavioral skill with a concrete ladder, rules, and an anti-pattern table that make its guidance genuinely actionable. Its only gap is the absence of an explicit verification step in the workflow.

Suggestions

Add an explicit validation checkpoint to the Workflow (e.g., 'Verify the minimal code actually solves the request before finishing') to lift workflow_clarity toward 5.

Consider a one-line 'When NOT to use this' note to sharpen distinctiveness and reduce overlap with general coding skills.

DimensionReasoningScore

Conciseness

Lean and efficient: no explanation of concepts Claude already knows, every line earns its place, and the brief aphoristic opener stays on-brand without padding.

5 / 5

Actionability

As an instruction-only skill it delivers concrete, executable guidance — a ranked efficiency ladder, explicit rules of engagement, a concrete bad→good anti-pattern table, and a worked example utterance — so the absence of copy-paste code is not penalized per the code-vs-instruction note.

5 / 5

Workflow Clarity

The Workflow section gives a clear 5-step sequence reinforced by guardrails in Rules of Engagement, but it lacks an explicit verification checkpoint (e.g., 'confirm the code runs'), leaving a minor validation gap versus the anchor above.

4 / 5

Progressive Disclosure

At well under 50 lines with no need for external references (the cross-references point to sibling skills, not bundle files), the well-organized sections satisfy the simple-skill exception for a top score.

5 / 5

Total

19

/

20

Passed

Description

91%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 strong description with an explicit 'Use when...' trigger, multiple natural synonyms, and a concrete efficiency ladder that clearly communicates what the skill does and when to use it. Voice is appropriately imperative/third person, with only minor distinctiveness overlap risk from its broad efficiency framing.

DimensionReasoningScore

Specificity

Names several concrete actions ('avoid over-engineering, reduce dependencies, prevent unnecessary abstractions') plus an enumerated efficiency ladder, but the actions are behavioral/process-level rather than discrete operations, leaving a minor coverage gap versus a fully comprehensive operational list.

4 / 5

Completeness

Explicitly answers 'when' with an 'Use when...' clause listing concrete triggers, and 'what' with 'Enforces a strict efficiency ladder: YAGNI, reuse, stdlib, native platform, existing deps — before writing any new code.'

5 / 5

Trigger Term Quality

Includes natural user phrases with synonyms — 'write code efficiently', 'avoid over-engineering', 'reduce dependencies', 'prevent unnecessary abstractions' — giving comprehensive coverage of the terms a user would actually say when needing this skill.

5 / 5

Distinctiveness Conflict Risk

The anti-over-engineering niche and named ladder are mostly distinct, but the broad 'write code efficiently' trigger could plausibly fire for many general coding requests, creating minor overlap risk with related coding skills.

4 / 5

Total

18

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
alirezarezvani/claude-skills
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.