CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

uncle-bob-craft

Use when performing code review, writing or refactoring code, or discussing architecture; complements clean-code and does not replace project linter/formatter.

Quality

57%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/uncle-bob-craft/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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, actionable skill with concrete review/refactoring workflows and real supporting reference files, scoring well on actionability and workflow clarity. Its two real weaknesses are repeated linter/formatter disclaimers that pad the token budget, and a phantom ./reference.md referenced six times that doesn't exist in the bundle, which breaks navigation to the deep content.

Suggestions

Create ./reference.md (or repoint all six citations to existing files) — the Aggregators table, Smells section, and Limitations all link to it for the full heuristic lists and "Scope and attribution" content that exists nowhere in the bundle.

State the "does not replace linter/formatter" caveat once (e.g., in Limitations) and cut it from Overview, When to Use, Best Practices, and Common Pitfalls — it currently consumes ~6 repetitions.

Merge the Aggregators-by-Source table into When to Use or Related Skills to remove the duplicated routing information.

DimensionReasoningScore

Conciseness

Mostly efficient curated guidance (smells table, tight review steps), but the "does not replace the linter/formatter" caveat is repeated roughly six times (Overview, When to Use, Best Practices ✅/❌, Common Pitfalls, Limitations) and the Aggregators table duplicates When-to-Use and Related-Skills content. Fits anchor 3 (some unnecessary repetition that could be tightened) rather than 2, since each section is individually tight and the padding is one recurring theme.

3 / 5

Actionability

Concrete guidance throughout: a 5-step review checklist, a copy-pasteable review prompt, an executable before/after Python example, and specific refactor phrasings ("Introduce an interface so this layer does not depend on the concrete DB client"). Anchor 4 (concrete examples with minor gaps) rather than 5 because the core guidance remains judgment heuristics ("SOLID in context") rather than fully executable commands covering the common cases.

4 / 5

Workflow Clarity

Both main workflows are clearly sequenced — "When reviewing code" gives 5 numbered steps ending in a tests/craft check, and "When writing or refactoring" gives 4 steps with the checkpoint "refactor in small steps with tests staying green". Anchor 4 (clear sequence with most checkpoints) rather than 5 because there is no explicit verify-and-recover loop around its own steps; no destructive/batch operations, so the cap-of-3 rule does not apply.

4 / 5

Progressive Disclosure

The four real references (references/clean-architecture.md, clean-coder.md, clean-agile.md, design-patterns.md) are clearly signaled one level deep from the Aggregators table and How It Works — but reference.md, cited six times as the holder of "Full lists" and "Scope and attribution", does not exist in the bundle, so the primary deep-dive pointer is dead. This fits anchor 3 (structure present but needs better organization/consistency); it is not anchor 4 because a broken central reference is more than a minor gap.

3 / 5

Total

14

/

20

Passed

Description

36%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 an explicit, well-formed trigger clause with sensible boundary marking against clean-code and the linter, but it omits any statement of what the skill actually does. Without a 'what' (e.g., applying Uncle Bob's Clean Code/Architecture/Coder/Agile criteria) and without key domain terms like SOLID or clean architecture, it under-informs and risks mis-triggering versus sibling skills.

Suggestions

State the 'what' up front in third person, e.g., "Applies Robert C. Martin (Uncle Bob) criteria — Clean Architecture, SOLID, code smells, design-pattern use vs misuse — to code review, refactoring, and architecture discussion", then keep the existing Use-when clause.

Add the domain's natural trigger terms users actually say: "SOLID", "clean architecture", "Uncle Bob", "design patterns", "code smells".

Sharpen distinctiveness by one clause, e.g., "Use for boundaries, Dependency Rule, and SOLID in context; use @clean-code for naming and function-level detail" — making the split with the sibling skill explicit.

DimensionReasoningScore

Specificity

The description names the domain ("code review, writing or refactoring code, or discussing architecture") but never states a concrete capability the skill itself performs — only user activities and the relationship note "complements clean-code and does not replace project linter/formatter". This matches anchor 2 ("names the domain but actions are minimal or generic"), not anchor 3, which requires at least 1-2 concrete skill actions.

2 / 5

Completeness

The "when" is explicit ("Use when performing code review, writing or refactoring code, or discussing architecture") but the "what" is absent — the description never says what the skill does (e.g., applies Robert C. Martin's craft/architecture criteria). This is precisely anchor 2 ("only 'when' is present without 'what'"), not anchor 3, which requires a clear 'what'.

2 / 5

Trigger Term Quality

"code review", "refactoring", and "architecture" are natural phrases users would say, but the description omits the domain's most characteristic trigger terms — "SOLID", "Uncle Bob", "clean architecture", "design patterns", "code smells" — which are exactly what users would mention when needing this skill. Some relevant keywords with common variations missing fits anchor 3 rather than 4.

3 / 5

Distinctiveness Conflict Risk

It explicitly positions itself against clean-code ("complements clean-code and does not replace project linter/formatter"), but its trigger terms — code review, refactoring, architecture — are broad and would fire for many overlapping skills including the sibling @clean-code skill. Somewhat specific with real overlap risk fits anchor 3; not 4 because the overlap with closely related code-quality skills is more than minor.

3 / 5

Total

10

/

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

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 6 missing

Warning

Total

14

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills/skills/uncle-bob-craft/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.