CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

angular-dependency-injection

Configure DI, inject() usage, and providers in Angular. Use when configuring Angular dependency injection, using inject(), or defining providers.

Quality

83%

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

78%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 lean, well-structured Angular DI reference with concrete API-level guidance and an appropriately used one-level reference file. The main weaknesses are fragment-level snippets with grammar errors in the body, a noise-value P0 priority heading, and an inline Angular version qualifier without deprecated-pattern context.

Suggestions

Remove the "## **Priority: P0 (CRITICAL)**" heading (it is metadata, not guidance) and fix grammar slips such as "to collects all multi providers" and "This creates instance destroyed when leaving route" so directives read as copy-ready instructions.

Move version-sensitive guidance out of inline parentheticals: state "provideAppInitializer (Angular 19+)" in a dedicated versioning note that also tells pre-19 apps to use the APP_INITIALIZER token it says it replaces.

Add a one-line decision summary at the top (e.g., "providedIn: 'root' by default; route providers only for route-scoped state; InjectionToken for config/primitives") to sequence the Principles and Guidelines rules.

DimensionReasoningScore

Conciseness

The body is lean and assumes Angular competence — e.g., "Use inject(MyService) function in class fields... It works in any injection context" with no basic-concept padding. Not 5 because of trimmable noise: the "## **Priority: P0 (CRITICAL)**" heading adds no guidance, and the inline version qualifier "(Angular 19+)" is time-sensitive information not placed in a deprecated/old-patterns section.

4 / 5

Actionability

Concrete API usage appears throughout — "provideAppInitializer(() => inject(ConfigService).load())", "{ provide: TOKEN, useClass: Impl, multi: true }", "{ provide: API_URL, useValue: 'https://api.example.com' }". Not 5 because guidance is fragment-level rather than copy-paste-ready in the body (full code lives in references/di-patterns.md) and grammar slips like "to collects all multi providers into array" and "This creates instance destroyed when leaving route" blur the instructions; well above 3 since nearly every directive names an exact API and location (app.config.ts, route config).

4 / 5

Workflow Clarity

As a decision-guidance skill with no multi-step process or destructive/batch operations, each rule is unambiguous and consistently organized Principles → Guidelines → Anti-Patterns (e.g., "Use 'root' scoping; reserve platform only for Micro Frontend sharing"). Not 5 because the multi-faceted rules have no decision ordering or summary to guide which rule applies when; not 3 because nothing is unclear and no risky operation lacks validation.

4 / 5

Progressive Disclosure

The body is a ~26-line overview with a single clearly signaled, one-level-deep reference — "[DI Patterns](references/di-patterns.md)" — which exists and holds the concrete code examples. Content is appropriately split between overview rules inline and code patterns in the reference, matching the under-50-line simple-skill exception.

5 / 5

Total

17

/

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 concise, third-person description that explicitly covers both what the skill does and when to use it, with natural trigger phrases. Main gaps are modest keyword coverage (missing "DI", "providedIn", "service") and slight overlap risk with other Angular skills.

DimensionReasoningScore

Specificity

"Configure DI, inject() usage, and providers in Angular" lists several specific capabilities rather than vague abstractions. Not 5 because coverage has minor gaps — injection tokens, factories, and app initializers (covered in the body) are absent from the description; not 3 because more than 1-2 concrete actions are named.

4 / 5

Completeness

Clearly answers "what" ("Configure DI, inject() usage, and providers in Angular") and "when" with an explicit "Use when..." clause listing concrete triggers. Uses third-person imperative voice throughout.

5 / 5

Trigger Term Quality

"configuring Angular dependency injection, using inject(), or defining providers" are phrases users would naturally say. Not 5 because common variations like "DI", "providedIn", "InjectionToken", or "service" are missing from the description itself (some appear only in frontmatter metadata triggers, which the description does not surface).

4 / 5

Distinctiveness Conflict Risk

The Angular DI niche is clear and every trigger is anchored to "Angular", keeping conflict risk low. Not 5 because generic terms like "providers" and "inject" leave minor overlap risk with other Angular skills (routing, testing, standalone components).

4 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

HoangNguyen0403/agent-skills-standard

Path

skills/angular/angular-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.