CtrlK
BlogDocsLog inGet started
Tessl Logo

services-layer

Whispering service boundaries: UI-free capabilities, explicit app inputs, Result-typed fallibility, direct Live objects, lifecycle-earned factories, and build-time #platform implementations. Use when creating or refactoring services, service contracts, platform variants, provider dispatch, or the $lib/services barrel.

71

Quality

86%

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

86%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-architected skill body: lean, concrete, and properly split across two real one-level references with a closing validation checklist. The only gap is that code examples are illustrative patterns rather than copy-paste-runnable scripts, which keeps actionability just below perfect.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence throughout — it never explains what a service or platform seam is, and every section (Boundary, Fallibility, Direct Object or Factory, Platform, Barrel, Final Check) earns its place with no padding.

5 / 5

Actionability

Concrete executable TypeScript is provided (the DownloadService Result type and the services barrel object) alongside specific file paths and directives, but the examples are illustrative type signatures and a barrel literal rather than fully runnable end-to-end scripts.

4 / 5

Workflow Clarity

The body is organized into clearly delineated guidance sections and closes with a 'Final Check' validation checklist, giving a clear sequence with checkpoints; it is a reference/guidance skill rather than a linear multi-step procedure, so it stops just short of explicit error-recovery feedback loops.

4 / 5

Progressive Disclosure

The overview points to two well-signaled, one-level-deep references (references/service-implementation-pattern.md and references/service-organization-platforms.md, both present in the bundle) for deeper detail, keeping the body an appropriately scoped overview with easy navigation.

5 / 5

Total

18

/

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, well-scoped description that answers both what and when with concrete triggers and a distinct codebase niche. Slightly jargon-heavy phrasing in the capability list keeps trigger-term quality and specificity just short of perfect.

DimensionReasoningScore

Specificity

Lists several concrete capabilities ('UI-free capabilities, explicit app inputs, Result-typed fallibility, direct Live objects, lifecycle-earned factories, and build-time #platform implementations'), but they are domain properties rather than verb-led actions, leaving minor coverage gaps.

4 / 5

Completeness

It explicitly states what the skill governs (the colon-delimited capability list) and when to use it ('Use when creating or refactoring services, service contracts, platform variants, provider dispatch, or the $lib/services barrel'), with concrete trigger phrases.

5 / 5

Trigger Term Quality

The 'Use when creating or refactoring services, service contracts, platform variants, provider dispatch, or the $lib/services barrel' clause gives good natural-term coverage, though the leading jargon ('Result-typed fallibility', 'lifecycle-earned factories') is phrasing users would rarely say verbatim.

4 / 5

Distinctiveness Conflict Risk

The 'Whispering service boundaries' framing plus '$lib/services barrel' and '#platform implementations' carve a clear codebase-specific niche with minimal overlap risk against 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
EpicenterHQ/epicenter
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.