CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

factory-function-composition

Factory function patterns to compose clients and services. Use when wrapping resources with domain methods, refactoring mixed client/service/method options, or documenting returned factory methods.

Quality

79%

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 ./.agents/skills/factory-function-composition/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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-structured pattern skill with concrete, actionable guidance and properly organized one-level-deep bundle references. Its main weakness is token efficiency: a padded Benefits section, an explanation of structural typing Claude already knows, and redundant anti-pattern examples inflate the body without adding value.

Suggestions

Remove the 'Benefits' section and the 'Why this works' structural-typing explanation — both restate knowledge Claude already has and add ~15 lines of padding.

Merge Anti-Pattern 2 (hidden client creation) and Anti-Pattern 4 (multiple layers hidden) into a single anti-pattern about hidden layers, since their bad/good examples are nearly identical.

Move links outside the skill directory (../collapse-pass/... and ../../../docs/articles/...) into the references/ bundle or summarize their content inline, so the skill remains self-contained when ported.

DimensionReasoningScore

Conciseness

Mostly dense, genuinely non-obvious convention content, but it includes unnecessary padding: a motivational "Benefits" section, a "Why this works" paragraph explaining TypeScript structural typing (a concept Claude already knows), and significant overlap between Anti-Pattern 2 and Anti-Pattern 4.

3 / 5

Actionability

Concrete TypeScript examples throughout — bad/good anti-pattern pairs, a zone-ordered internal shape, a `this` decision table, and explicit adapter collapse/stay criteria — though many snippets have elided bodies ({ ... }), making them shape templates rather than copy-paste executable code.

4 / 5

Workflow Clarity

A pattern/reference skill with a logical progression (signature → anti-patterns → internal shape → advanced patterns), explicit recognition triggers, and clear decision points like the `this` table and adapter signs; no validation steps are needed since operations are non-destructive.

4 / 5

Progressive Disclosure

The three bundle references (single-or-array-pattern, sync-construction-render-gate, method-documentation-and-sibling-calls) all exist, are one level deep, and are clearly signaled under "Load on demand" with per-file descriptions. Minor gaps: several links point outside the skill directory (../collapse-pass/..., ../../../docs/articles/...) and won't travel with the bundle, and some advanced sections could be split into reference files.

4 / 5

Total

15

/

20

Passed

Description

83%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 description with an explicit 'Use when' clause carrying three concrete triggers and a clear statement of what the skill does. It occupies a distinct niche; the only weaknesses are slightly abstract action verbs and minor overlap with generic refactoring skills.

DimensionReasoningScore

Specificity

Lists three specific actions — "wrapping resources with domain methods", "refactoring mixed client/service/method options", "documenting returned factory methods" — but they are pattern-level abstractions rather than fully concrete operations like extract/fill/merge, leaving minor gaps in coverage.

4 / 5

Completeness

Clearly answers both what ("Factory function patterns to compose clients and services") and when ("Use when wrapping resources with domain methods, refactoring mixed client/service/method options, or documenting returned factory methods") with explicit, concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural developer terms like "factory function", "compose clients and services", "refactoring", and "wrapping resources" are present, but common variations and synonyms (e.g. "dependency injection", "service layer") are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche with distinct factory-composition triggers, but the "refactoring" trigger has minor overlap risk with closely related general refactoring skills.

4 / 5

Total

17

/

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

relative_links

Relative link issues: 7 suspicious

Warning

Total

15

/

16

Passed

Repository

EpicenterHQ/epicenter

Path

.agents/skills/factory-function-composition/SKILL.md

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.