CtrlK
BlogDocsLog inGet started
Tessl Logo

layered-architecture-types

Enforce primitive-at-edges / strong-types-in-Business layering and the toBus/fromBusResponse/toDB converter pattern. Use when writing, editing, or auditing Go files under app/*, business/domain/*, or .../stores/*db.

69

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 focused, actionable skill body with executable Go examples in both layer directions and an explicit validation checklist plus user-confirmation feedback loop. It is concise and assumes competence, with only minor redundancy and limited use of separate reference files.

Suggestions

Trim the Conformance checklist or convert it to a quick-reference that points back to the MUST sections, since it largely restates rules already stated above and costs tokens.

Add a one-line 'untrusted input' note for the storage toBus example instead of leaving the '// ... parse remaining native values' placeholder, so the example is fully executable as written.

Consider extracting the longer rule blocks (Pointer types, Foundation types are wrapped) into a reference file referenced from the body to improve progressive disclosure and reduce SKILL.md length.

DimensionReasoningScore

Conciseness

Dense, project-specific rules that assume Claude's competence and avoid generic concept explanations, but the conformance checklist substantially restates the MUST sections, adding tokens that could be trimmed.

4 / 5

Actionability

Provides complete, executable Go examples covering both App and Storage layers in both directions, with only minor placeholders ('// ... parse remaining native values') leaving small gaps.

4 / 5

Workflow Clarity

Sequences the work with an explicit conformance checklist acting as a validation gate before finalizing, plus a user-type-confirmation feedback loop ('state the concrete types ... get explicit confirmation before committing').

5 / 5

Progressive Disclosure

Well-organized into clearly headed ## sections with no nested references and no bundle files, though the single ~244-line file inlines several rule blocks (e.g. pointer-avoidance, foundation wrappers) that could be split into reference files.

4 / 5

Total

17

/

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 specific, well-scoped description that clearly states both the enforcement behavior and concrete use triggers tied to particular Go path patterns. Minor room for more enumerated actions and plainer synonyms, but it answers what and when distinctly.

DimensionReasoningScore

Specificity

Names concrete enforcement actions ('Enforce primitive-at-edges / strong-types-in-Business layering') and the specific converter pattern ('toBus/fromBusResponse/toDB'), but does not enumerate each direction individually so coverage is strong rather than fully comprehensive.

4 / 5

Completeness

Explicitly answers both what ('Enforce ... layering and the ... converter pattern') and when ('Use when writing, editing, or auditing Go files under app/*, business/domain/*, or .../stores/*db') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural user-facing verbs ('writing, editing, or auditing Go files') alongside scoped path globs, but leans on path patterns rather than plain synonyms a user would naturally say.

4 / 5

Distinctiveness Conflict Risk

Highly niche, path-scoped Go layering skill with a distinctive converter naming convention; minimal overlap risk with other skills.

5 / 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
ardanlabs/service
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.