CtrlK
BlogDocsLog inGet started
Tessl Logo

service-layer

Defines application service structure and business orchestration boundaries

59

Quality

68%

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

87%

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

The body is concise, concrete, and well-organized, providing executable examples and specific standards without padding. Its only weakness is that it is a static reference rather than a guided workflow, so it lacks sequencing and validation checkpoints.

DimensionReasoningScore

Conciseness

The body is lean and rule-based (MUST/MUST NOT lists, a compact code snippet, terse DTO guidance) with no padding of concepts Claude already knows, matching the 'lean and efficient; every token earns its place' anchor.

3 / 3

Actionability

It gives a concrete executable PHP constructor-injection example, an exact file-path shape with real examples, named standard methods, and specific checkable rules, fitting the 'fully executable code/commands; specific examples' anchor for an instruction/standards skill.

3 / 3

Workflow Clarity

The content is a static architectural reference organized into numbered sections rather than a sequenced multi-step process, so it has structure but no workflow sequence or validation checkpoints, matching the score-2 anchor.

2 / 3

Progressive Disclosure

It is a self-contained skill under 50 lines with no external bundle files and no nested references, well-organized into clear sections, which per the guidelines can score 3 with just well-organized sections.

3 / 3

Total

11

/

12

Passed

Description

50%

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 identifies a clear architectural niche but stays abstract, lacking concrete actions, natural trigger terms, and any "Use when" guidance. It is distinguishable but would benefit from explicit invocation triggers and more user-facing language.

Suggestions

Add a "Use when..." clause stating when to apply this skill, e.g. "Use when creating or refactoring service classes, reviewing service-layer structure, or enforcing business-logic boundaries."

Include natural trigger terms users would actually say ("service layer", "business logic", "services", "Laravel services") instead of abstract phrasing like "business orchestration boundaries".

Replace the abstract verb with concrete actions, e.g. "Structures application service classes, coordinates models, and enforces domain rules."

DimensionReasoningScore

Specificity

The phrase "Defines application service structure and business orchestration boundaries" names a concrete domain but relies on the abstract verb "Defines" with no list of specific actions, fitting the 'names domain and some actions, but not comprehensive' anchor rather than the multi-action score 3.

2 / 3

Completeness

It answers "what" (defines service structure and orchestration boundaries) but provides no "Use when..." or equivalent trigger guidance, so completeness is capped at 2 per the judging guidelines.

2 / 3

Trigger Term Quality

Terms like "application service" and "business orchestration" are relevant but jargon-heavy and miss common natural variations users would say ("service layer", "business logic", "services"), matching the 'some relevant keywords but missing common variations' anchor.

2 / 3

Distinctiveness Conflict Risk

The service-layer niche is fairly specific, but without explicit triggers and with broad architectural framing it could still overlap with general architecture or coding-standards skills, matching the 'somewhat specific but could still overlap' anchor.

2 / 3

Total

8

/

12

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.

Validation15 / 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.