CtrlK
BlogDocsLog inGet started
Tessl Logo

angular-dependency-injection

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

66

Quality

81%

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

75%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 concise, actionable Angular DI reference with concrete code patterns and a properly structured single reference file. It is strongest in actionability and conciseness, with only minor organization and completeness gaps.

DimensionReasoningScore

Conciseness

The body is lean and directive with bolded code terms and no over-explanation of Angular DI basics, though phrases like "for cleaner injection" and "replaces old APP_INITIALIZER token pattern" add minor padding.

4 / 5

Actionability

Concrete, copy-paste-ready patterns (inject(MyService), providedIn: 'root', InjectionToken<T>, provideHttpClient(), provideAppInitializer()) cover common cases, with the reference file holding fuller examples; a few snippets remain fragments rather than complete runnable files.

4 / 5

Workflow Clarity

This is a single-purpose reference skill with no destructive/batch operation, so the destructive-cap does not apply; content is organized into clear Principles/Guidelines/Anti-Patterns sections with unambiguous guidance, though no multi-step sequence or checkpoints exist.

4 / 5

Progressive Disclosure

A concise overview links one real, one-level-deep reference (references/di-patterns.md) that exists and holds expanded examples, but the inline "Canonical response anchors" section is an unusual organization element that keeps it from the top anchor.

4 / 5

Total

16

/

20

Passed

Description

87%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 well-crafted description that covers what the skill does and when to use it with concrete, framework-specific trigger phrases. Minor gains possible by adding common synonyms like "DI" and "services" to the trigger list.

DimensionReasoningScore

Specificity

"Configure DI, inject() usage, and providers in Angular" names the domain plus three concrete action areas, but coverage is not fully comprehensive (e.g., tokens and factories only appear in the body).

4 / 5

Completeness

It gives a clear "what" ("Configure DI, inject() usage, and providers") and an explicit "Use when..." clause with concrete triggers, matching the highest anchor.

5 / 5

Trigger Term Quality

"Angular dependency injection", "inject()", "providers" are natural terms developers say, but common synonyms ("DI", "services", "InjectionToken") are absent from the description.

4 / 5

Distinctiveness Conflict Risk

The Angular DI niche with framework-specific triggers is clearly distinguishable from other skills with minimal conflict risk.

5 / 5

Total

18

/

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.

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