CtrlK
BlogDocsLog inGet started
Tessl Logo

service-layer

Defines application service structure and business orchestration boundaries

53

Quality

67%

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 ./.claude/skills/service-layer/SKILL.md
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.

The content is a concise, well-structured set of architectural rules with concrete code and path examples and no padding. Its main gap is the absence of an explicit apply/verify workflow and any progressive disclosure to deeper reference material.

DimensionReasoningScore

Conciseness

The body is lean and rule-driven with no padding or explanation of concepts Claude already knows; every section (MUST/MUST NOT lists, injection snippet, DTO guidance, file shape) earns its place, matching the 5-anchor 'lean and efficient; assumes Claude's competence'.

5 / 5

Actionability

It gives executable guidance — a constructor-injection PHP snippet, the concrete path shape 'app/Services/{Domain}/{Model}Service.php', and named standard methods — but the examples are illustrative fragments rather than fully copy-pasteable service classes, fitting the 4-anchor 'mostly executable; minor gaps'.

4 / 5

Workflow Clarity

As a prescriptive rules skill it has no multi-step destructive workflow requiring validation checkpoints, and its rules are clearly sequenced by section; it sits at 4 rather than 5 because there is no explicit workflow or checklist tying the rules into an apply-then-verify sequence.

4 / 5

Progressive Disclosure

Content is well-organized into labeled one-level sections with no nested or buried references and no bundle files to navigate; it is 4 rather than 5 only because everything is inlined in SKILL.md with slightly more than the ~50-line threshold where well-organized sections alone would justify a 5.

4 / 5

Total

17

/

20

Passed

Description

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

The description clearly identifies its architectural domain but is abstract and lacks concrete actions or any 'use when' trigger guidance. It is distinguishable yet generic enough to risk overlap with related architecture skills.

Suggestions

Add concrete actions the skill governs, e.g. 'Defines where business logic lives, how services inject dependencies, and when to use DTOs'.

Append an explicit trigger clause such as 'Use when structuring application services or deciding where business logic belongs'.

Include natural synonyms a developer would say (e.g. 'service layer', 'business logic', 'service classes') to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain ('application service structure', 'business orchestration boundaries') but the only action verb is the generic 'Defines', with no concrete capabilities enumerated — matching the 'names the domain but actions are minimal or generic' anchor rather than the 3-anchor which requires 1-2 concrete actions.

2 / 5

Completeness

It states a clear 'what' (defines service structure and orchestration boundaries) but provides no 'when'/Use-when trigger guidance, so per the judging guideline a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

It relies on technical jargon ('service structure', 'business orchestration boundaries') with only one or two generic keywords ('service'); it lacks the natural phrases or synonyms a user would actually say, fitting the 2-anchor better than the 3-anchor's 'some relevant keywords'.

2 / 5

Distinctiveness Conflict Risk

'Service layer' is a recognizable niche but the phrasing is abstract enough to overlap with other architecture/structuring skills, matching the 3-anchor 'somewhat specific but could still overlap' rather than the more sharply distinct 4-anchor.

3 / 5

Total

10

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
Bottelet/DaybydayCRM
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.