CtrlK
BlogDocsLog inGet started
Tessl Logo

business-layer-extensions

Use when adding a cross-cutting concern (OTEL tracing, logging, metrics, caching, auth) to a business domain, creating files under business/domain/*/extensions/*, or adding the extension seam (ExtBusiness/Extension) to a *bus package.

74

Quality

91%

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

82%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 tight, highly actionable skill body with complete executable examples and a clear sequenced workflow. Its only weaknesses are minor: a few redundant phrases and an inlined metrics variant that could be split into a reference.

Suggestions

Add an explicit validation checkpoint to the checklist (e.g., 'Build the package and confirm it compiles; a missing pass-through method surfaces as an interface error') so the workflow has a visible verify step rather than relying on Common mistakes.

Trim redundant phrasing — 'The whole point is to leave core logic untouched' repeats 'Wrap, never modify the core Business' — to push conciseness to a 5.

Consider moving the full Metrics variant into a references/ file linked from Piece 2 to keep the core SKILL.md overview shorter and improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is lean with no concept-padding (no 'what is OTEL/decorator' exposition) and every section earns its place; a few minor restatements ('The whole point is to leave core logic untouched' vs 'Wrap, never modify the core Business') could be trimmed, keeping it just below a 5.

4 / 5

Actionability

Provides complete, copy-paste-ready Go for all three pieces plus a full Prometheus metrics variant and concrete wiring, covering the common cases with executable code and specific file paths.

5 / 5

Workflow Clarity

A clear 4-step checklist (seam exists → create → implement every method → wire in order) with the compile-error feedback loop surfaced in Common mistakes, but there is no explicit validate/verify checkpoint in the main sequence so it sits at 4 rather than 5.

4 / 5

Progressive Disclosure

Well-organized into Checklist, Piece 1/2/3, and Common mistakes with no nested references and no bundle files to navigate; the inlined metrics variant is content that could arguably live in a reference, which is the minor gap preventing a 5.

4 / 5

Total

17

/

20

Passed

Description

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

An excellent description: specific, trigger-rich, explicit on both what and when, and highly distinct from other skills. It reads exactly like the phrase a user would say when they need this skill.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — adding named cross-cutting concerns (OTEL tracing, logging, metrics, caching, auth), creating files under business/domain/*/extensions/*, and adding the ExtBusiness/Extension seam — giving comprehensive, specific coverage rather than vague language.

5 / 5

Completeness

Explicitly answers both 'what' (decorator-style cross-cutting extensions on a business domain) and 'when' via a clear 'Use when…' clause with three concrete triggering situations.

5 / 5

Trigger Term Quality

Includes the natural terms a developer in this repo would say ('OTEL tracing', 'logging', 'metrics', 'caching', 'auth') plus concrete path and type-name triggers, with no common variation obviously missing.

5 / 5

Distinctiveness Conflict Risk

The niche is tightly scoped by architecture-specific signals (ExtBusiness/Extension seam, *bus packages, business/domain/*/extensions/* paths), making conflict with unrelated skills minimal.

5 / 5

Total

20

/

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.