angular-http-client
Integrate HttpClient, Interceptors, and API interactions in Angular. Use when integrating HttpClient, writing interceptors, or handling API calls in Angular.
59
70%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/angular/angular-http-client/SKILL.mdQuality
Discovery
75%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description is structurally sound with a clear 'what' and 'when' clause, and targets a distinct Angular HTTP niche. However, it is somewhat tautological—the 'Use when' clause nearly repeats the first sentence verbatim rather than adding new trigger scenarios. The specificity of concrete actions and breadth of trigger terms could be improved.
Suggestions
Expand concrete actions beyond 'integrate' and 'handle'—e.g., 'Configure HttpClient, write request/response interceptors, handle errors, set headers, manage authentication tokens, and make REST API calls in Angular.'
Add more natural trigger term variations such as 'HTTP requests', 'REST API', 'backend integration', 'auth token', 'error handling', 'Observable', or 'subscribe' to improve matching.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Angular) and some specific concepts (HttpClient, Interceptors, API interactions), but doesn't list concrete actions beyond 'integrate' and 'handle'. Missing specifics like error handling, retry logic, request/response transformation, etc. | 2 / 3 |
Completeness | Clearly answers both 'what' (integrate HttpClient, Interceptors, and API interactions in Angular) and 'when' (Use when integrating HttpClient, writing interceptors, or handling API calls in Angular) with an explicit 'Use when...' clause. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'HttpClient', 'Interceptors', and 'API calls' which users would naturally mention, but misses common variations like 'HTTP requests', 'REST API', 'backend calls', 'auth interceptor', 'error handling', or 'Observable/subscribe'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of Angular-specific HTTP concepts (HttpClient, Interceptors) creates a clear niche that is unlikely to conflict with general API skills or other framework-specific skills. The Angular specificity and HTTP focus make it distinctly identifiable. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
64%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-structured, concise Angular HTTP skill that efficiently communicates modern patterns (functional interceptors, httpResource, signal-based approaches) without over-explaining. Its main weaknesses are incomplete actionability—several patterns are described at a high level without fully executable examples—and the lack of supporting bundle files for the referenced interceptors.md. The anti-patterns section is a useful addition that adds clear guardrails.
Suggestions
Add a complete, executable example for interceptor registration in app.config.ts showing provideHttpClient(withInterceptors([...]), withFetch()) with an actual interceptor function
Provide a concrete caching example using shareReplay(1) in a service, rather than just mentioning it as a strategy
Include the referenced 'references/interceptors.md' file in the bundle, or remove the reference if it doesn't exist
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It assumes Claude knows Angular, HTTP concepts, and RxJS. Every section delivers new, specific information without explaining basics. The inline code snippets are terse but informative. | 3 / 3 |
Actionability | Provides concrete patterns like the interceptor function signature and httpResource usage, but most guidance is fragmentary rather than fully executable. For example, the interceptor registration pattern mentions `withInterceptors([...])` but doesn't show a complete app.config.ts setup, and the caching guidance is vague ('implement caching in interceptors or using shareReplay(1)') without a concrete example. | 2 / 3 |
Workflow Clarity | The skill covers multiple concerns (interceptors, services, httpResource, error handling, caching) but doesn't sequence them into a clear workflow. For a reference-style skill this is acceptable, but the error handling section lacks a concrete feedback loop or validation pattern, and there's no guidance on how to wire everything together step-by-step. | 2 / 3 |
Progressive Disclosure | There is a reference to 'references/interceptors.md' which is good, but the bundle has no files to support it. The content itself is reasonably structured with clear sections, but caching, error handling, and HttpContext could benefit from their own reference files rather than being briefly mentioned inline. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
- Repository
- HoangNguyen0403/agent-skills-standard
- Commit
3df717f
- 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.