angular-http-client
Integrate HttpClient, Interceptors, and API interactions in Angular. Use when integrating HttpClient, writing interceptors, or handling API calls in Angular. (triggers: **/*.service.ts, **/*.interceptor.ts, HttpClient, HttpInterceptorFn, withInterceptors, httpResource, resource)
85
81%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description with strong trigger term coverage and clear completeness. Its main weakness is that the capability description could be more specific about concrete actions beyond 'integrate' and 'handle'. The explicit trigger list and 'Use when' clause make it highly functional for skill selection.
Suggestions
Add more specific concrete actions such as 'configure request/response interceptors, set authentication headers, handle API error responses, manage HTTP caching' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Angular HTTP) and some actions (integrate HttpClient, write interceptors, handle API calls), but the actions are somewhat generic and not deeply specific—e.g., it doesn't mention concrete tasks like 'configure retry logic', 'set auth headers', or 'parse response bodies'. | 2 / 3 |
Completeness | Clearly answers both 'what' (integrate HttpClient, interceptors, API interactions in Angular) and 'when' (explicit 'Use when...' clause plus trigger terms), satisfying the completeness requirement. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including file patterns ('**/*.service.ts', '**/*.interceptor.ts') and specific Angular APIs ('HttpClient', 'HttpInterceptorFn', 'withInterceptors', 'httpResource', 'resource'). These are terms a developer would naturally use or encounter. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with Angular-specific HTTP terminology and file patterns. The combination of HttpClient, interceptors, and Angular-specific APIs like 'httpResource' and 'withInterceptors' creates a clear niche unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-organized, concise Angular HTTP skill that effectively communicates modern patterns (functional interceptors, httpResource, signal-based approaches) and anti-patterns. Its main weakness is that actionability could be improved with more complete, executable code examples—particularly for interceptor registration, error handling patterns, and caching implementations. The progressive disclosure and conciseness are strong.
Suggestions
Add a complete, executable example showing a service with HttpClient injection, a functional interceptor, and the provideHttpClient registration in app.config.ts as a 'Quick Start' section.
Provide a concrete error handling example using catchError in a service method, rather than just describing the pattern.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, assuming Claude's familiarity with Angular and HTTP concepts. No unnecessary explanations of what HttpClient is or how HTTP works—every line conveys actionable, Angular-specific guidance. | 3 / 3 |
Actionability | The skill provides some concrete code snippets (httpResource usage, interceptor pattern inline), but most guidance is descriptive rather than fully executable. For example, the interceptor setup with provideHttpClient and the caching/error handling sections lack complete, copy-paste-ready code examples. | 2 / 3 |
Workflow Clarity | The skill covers what to do (use functional interceptors, register in app.config.ts, encapsulate in services) but doesn't provide a clear sequenced workflow for setting up HTTP integration from scratch. For a reference-style skill this is acceptable, but there are no validation checkpoints or explicit step ordering. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections (Principles, Signal-Based HTTP, Guidelines, Anti-Patterns) and appropriately references a deeper file for interceptors. The main file stays concise as an overview with one-level-deep navigation. | 3 / 3 |
Total | 10 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- HoangNguyen0403/agent-skills-standard
- Commit
19a1140
- 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.