CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

webiny-dependency-injection

The universal createImplementation DI pattern and all injectable services. Use this skill when the developer is writing any Webiny extension and needs to understand dependency injection, constructor injection, how to access Logger/BuildParams/IdentityContext, how to inject CMS use-cases (list/get/create/update/delete entries), or how the dependencies array works. This is the connective tissue across all extension types -- API, Admin, CLI, and Infrastructure.

Quality

84%

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

71%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 body delivers accurate, executable, domain-specific guidance that assumes Claude's competence and covers the DI pattern thoroughly across extension types, with a valuable security warning about resolver-scoped dependencies. Its main weaknesses are organization — advanced reference material is inlined in a single long file with no bundle files — plus minor duplication and a few non-executable fragments in the advanced examples.

Suggestions

Move the Container API Reference and the Advanced Dependency Options sections (multi-injection, optional, decorators, composites) into references/ files (e.g., references/container-api.md, references/advanced-dependencies.md), keeping SKILL.md as a concise overview with clearly signaled one-level-deep links.

Trim duplication: collapse the identical createAbstraction/createFeature rows in the Working Context table and remove the repeated 'connective tissue across all extension types' phrasing that already appears in the description.

Make the advanced code fragments executable by using concrete named abstractions and imports (e.g., replace 'Abstraction', 'RequiredService', 'PresenterAbstraction' with real examples) so every snippet is copy-paste ready.

DimensionReasoningScore

Conciseness

The body is dense with Webiny-specific knowledge Claude would not already have (custom factories, resolver-scoping rules, container API) and never explains generic DI/TypeScript concepts. Minor trimming is possible: the Working Context table repeats identical import paths across two rows, the 'connective tissue' phrase is repeated verbatim from the description, and three full extension-type examples could be condensed to two.

4 / 5

Actionability

The core examples (universal pattern, GraphQL schema, CLI command, Pulumi handler) are complete and copy-paste ready with imports. Minor gaps remain in the advanced sections, where fragments reference undefined abstractions ('Abstraction', 'RequiredService', 'PresenterAbstraction') without imports, and the Pulumi example uses 'execute(app: any)'.

4 / 5

Workflow Clarity

The 'how to write an extension with DI' flow is unambiguous: detect context (extensions/ vs packages/), implement the class, match the dependencies array to constructor order, export via createImplementation — reinforced by a numbered Key Rules section, the resolver-scoping warning, and the multi-injection registration example. No validation checkpoints are needed since the skill involves no destructive or batch operations, but there is no explicit end-to-end sequence either (e.g., when/how to register and verify an extension), keeping it just below a 5.

4 / 5

Progressive Disclosure

The file is well-sectioned with clear headers and correctly signals sibling skills ('See the webiny-custom-graphql-api skill'), but there is no bundle at all: roughly half of the ~365 lines (Container API Reference, multi-injection, optional dependencies, decorators, composites) is reference material that belongs in separate reference files, leaving SKILL.md as a near-monolithic document rather than an overview with one-level-deep references.

3 / 5

Total

15

/

20

Passed

Description

88%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: it names a precise niche, enumerates concrete capabilities and services, and gives an explicit 'Use this skill when...' trigger clause with specific conditions, all in third person. Its only weaknesses are a few missing natural synonyms ('DI', 'container') and a slight breadth-induced overlap with sibling Webiny skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete capabilities: 'createImplementation DI pattern and all injectable services', 'constructor injection', 'how to access Logger/BuildParams/IdentityContext', 'how to inject CMS use-cases (list/get/create/update/delete entries)', and 'how the dependencies array works' — comprehensive coverage of the skill's scope with no vague filler.

5 / 5

Completeness

Both 'what' ('The universal createImplementation DI pattern and all injectable services') and 'when' ('Use this skill when the developer is writing any Webiny extension and needs to understand...') are answered explicitly, with concrete trigger conditions enumerated (DI, constructor injection, accessing specific services, injecting CMS use-cases, the dependencies array).

5 / 5

Trigger Term Quality

Good natural keyword coverage — 'dependency injection', 'constructor injection', 'inject CMS use-cases', 'Webiny extension' are phrases a developer would naturally say. A few natural synonyms are missing (e.g., 'DI', 'service container', 'IoC'), and phrases like 'connective tissue' add no trigger value, so it falls just below the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

The niche is clear (Webiny-specific DI via createImplementation), so generic conflict risk is minimal. Minor overlap risk remains with sibling Webiny skills that also cover DI for specific extension types, which the description acknowledges by spanning 'all extension types -- API, Admin, CLI, and Infrastructure'.

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

webiny/webiny-js

Path

skills/user-skills/dependency-injection/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.