CtrlK
BlogDocsLog inGet started
Tessl Logo

codebase-design

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

65

Quality

79%

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 ./.agents/skills/codebase-design/SKILL.md

The canonical home for this skill is codebase-design in mattpocock/skills

SKILL.md
Quality
Evals
Security

Quality

Content

71%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 well-structured, mostly lean reference skill with concrete actionable design guidance, undermined only by progressive disclosure: its two 'Going deeper' links point to bundle files that do not exist.

Suggestions

Create the referenced DEEPENING.md and DESIGN-IT-TWICE.md files (or add them to the bundle) so the 'Going deeper' links resolve.

If those files are not yet available, remove the dangling links or mark them as forthcoming to avoid broken navigation.

Tighten glossary qualifiers (e.g. 'Deliberately scale-agnostic: a function, class, package, or tier-spanning slice') to shave a few tokens without losing clarity.

DimensionReasoningScore

Conciseness

Lean glossary and principles that assume competence without explaining basic concepts, with minor over-explanation in glossary qualifiers and the somewhat lavish ASCII diagrams and rejected-framings sections.

4 / 5

Actionability

Provides concrete design questions, the deletion test, explicit testability rules, and executable TypeScript examples (processOrder, calculateDiscount); as an instruction skill its guidance is specific with only minor gaps.

4 / 5

Workflow Clarity

Numbered testability principles and an explicit 'When designing an interface, ask:' sequence give a clear, unambiguous flow; no destructive/batch operation applies, so the validation cap does not bind.

4 / 5

Progressive Disclosure

Body is well-sectioned and the 'Going deeper' references are clearly signaled and one level deep, but the referenced files (DEEPENING.md, DESIGN-IT-TWICE.md) are not present in the bundle, leaving the navigation targets broken.

3 / 5

Total

15

/

20

Passed

Description

87%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, distinctive description that clearly answers both what the skill provides and when to use it, with concrete triggers and low conflict risk. Minor room for more natural, less jargon-flavored trigger terms.

DimensionReasoningScore

Specificity

Lists several concrete actions ('design or improve a module's interface', 'find deepening opportunities', 'decide where a seam goes', 'make code more testable or AI-navigable') with minor gaps versus a fully comprehensive action list.

4 / 5

Completeness

Explicitly states both what ('Shared vocabulary for designing deep modules') and when ('Use when the user wants to...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural-term coverage ('design or improve a module's interface', 'make code more testable') though a few terms like 'deepening opportunities' and 'AI-navigable' lean toward jargon users may not naturally say.

4 / 5

Distinctiveness Conflict Risk

The 'deep-module vocabulary' niche and seam/interface/design triggers are distinctive and unlikely to fire for unrelated skills, minimizing conflict risk.

5 / 5

Total

18

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 missing

Warning

Total

15

/

16

Passed

Repository
The-Vibe-Company/companion
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.