services-layer

Service layer patterns: defineErrors, namespace exports, Result types. Use when: "create a service", "service layer", creating services, defining domain-specific errors.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable skill body with executable TypeScript examples, a clear rules checklist, and exemplary conditional-loading references. The main weakness is a redundant error-example section that restates patterns already demonstrated.

Suggestions

Remove or consolidate the "Error Type Examples from the Codebase" section, since its RecorderError and HttpError examples duplicate the ones already shown under "How defineErrors Works"; reference error-anti-patterns.md instead for additional cases.

Consider moving the extended multi-variant HttpError namespace example into a reference file to keep the core body focused on the single canonical defineErrors pattern.

Dimension	Reasoning	Score
Conciseness	Mostly lean and code-driven with minimal concept padding, but the "Error Type Examples from the Codebase" section restates the RecorderError/HttpError patterns already shown in the preceding "How defineErrors Works" examples, adding redundant tokens that do not fully earn their place.	2 / 3
Actionability	Provides complete, executable TypeScript examples for defineErrors, InferError/InferErrors type derivation, and variant call sites, plus 10 concrete numbered Key Rules — copy-paste ready and specific.	3 / 3
Workflow Clarity	This is a patterns/standards skill rather than a multi-step operational workflow, but the three-layer architecture diagram and 10 numbered Key Rules form a clear, well-sequenced checklist, and there are no destructive or batch operations that would require validation feedback loops.	3 / 3
Progressive Disclosure	Clear overview in the body with a well-signaled References section that gives condition-based on-demand loading guidance, and all four referenced files (error-anti-patterns.md, service-implementation-pattern.md, service-organization-platforms.md, error-message-best-practices.md) exist one level deep in references/.	3 / 3
	Total	11 / 12 Passed

Description

90%

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 description that answers both what and when, with an explicit 'Use when' clause and natural trigger phrases. Its only weakness is specificity: it names a few patterns rather than a comprehensive action list.

Suggestions

Expand the capability list beyond three named patterns to mention the concrete actions the skill guides (e.g., defining domain errors, deriving error types, structuring factory + Live exports) for a fuller 'score 3' specificity.

Dimension	Reasoning	Score
Specificity	Names the domain and three specific concrete patterns ("defineErrors, namespace exports, Result types") but does not comprehensively enumerate the full range of actions the service skill performs, so it falls short of the multi-action 'score 3' anchor.	2 / 3
Completeness	Clearly states what the skill covers ("Service layer patterns: defineErrors, namespace exports, Result types") and includes an explicit "Use when:" clause with multiple triggers, answering both what and when.	3 / 3
Trigger Term Quality	Includes natural trigger phrases a user would actually say — quoted "create a service", "service layer" plus "creating services" and "defining domain-specific errors" — giving good coverage of common phrasings.	3 / 3
Distinctiveness Conflict Risk	Carves a clear niche around service layer architecture with distinctive technical triggers ("service layer", "defineErrors", "Result types") unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: EpicenterHQ/epicenter
Path: .agents/skills/services-layer/SKILL.md
Commit: cb12bcc

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.