angular-http-client
Integrate HttpClient, Interceptors, and API interactions in Angular. Use when integrating HttpClient, writing interceptors, or handling API calls in Angular.
79
76%
Does it follow best practices?
Impact
Pending
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
67%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 functional and includes both 'what' and 'when' clauses, which is good for completeness. However, the 'Use when' clause largely restates the first sentence rather than adding new trigger terms or scenarios. The description would benefit from more specific concrete actions and broader natural language trigger terms.
Suggestions
Expand trigger terms to include natural variations users would say, such as 'HTTP requests', 'REST API', 'backend calls', 'auth headers', 'Observable', or 'error handling'.
Add more specific concrete actions beyond 'integrate' and 'handle', such as 'configure request/response interceptors, set authentication headers, handle HTTP errors, manage API retry logic'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Angular) and some specific actions (integrate HttpClient, write interceptors, handle API calls), but doesn't list multiple concrete granular actions 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' with an explicit 'Use when...' clause specifying trigger conditions. | 3 / 3 |
Trigger Term Quality | Includes relevant keywords like 'HttpClient', 'Interceptors', 'API interactions', and 'Angular', but misses common variations users might say such as 'HTTP requests', 'REST API', 'backend calls', 'auth token', 'headers', or 'Observable'. | 2 / 3 |
Distinctiveness Conflict Risk | The Angular + HttpClient combination is fairly specific, but 'API interactions' is broad and could overlap with general API skills or other framework-specific HTTP skills. The interceptors mention adds some distinctiveness. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
85%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 and anti-patterns. Its main weakness is that several guidelines (caching, error handling, HttpContext) are described abstractly without executable code examples, reducing actionability. The progressive disclosure and organization are strong, with appropriate use of a reference file for interceptor details.
Suggestions
Add executable code examples for caching with shareReplay(1) in a service and error handling with catchError to make those guidelines fully actionable.
Include a concrete HttpContext example showing how to pass metadata (e.g., skip error handling) to an interceptor, since this is a less commonly known pattern.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, assuming Claude's familiarity with Angular and HTTP concepts. Every section delivers actionable information without explaining basics like what HTTP clients are or how Angular services work. | 3 / 3 |
Actionability | The skill provides some concrete code snippets (e.g., the httpResource example and the interceptor pattern), but many guidelines are described rather than demonstrated with executable code. For instance, caching with shareReplay(1), error handling with catchError, and HttpContext usage lack concrete examples. | 2 / 3 |
Workflow Clarity | This is a pattern/convention skill rather than a multi-step workflow skill. The single-task guidance is unambiguous: use functional interceptors, register via provideHttpClient, encapsulate HTTP in services, prefer httpResource for GETs. The sequencing of setup (app.config.ts registration) and usage is clear. | 3 / 3 |
Progressive Disclosure | The skill provides a clear overview with well-organized sections (Principles, Signal-Based HTTP, Guidelines, Anti-Patterns) and appropriately references a deeper file for interceptors. Content is not monolithic and navigation is straightforward with one-level-deep references. | 3 / 3 |
Total | 11 / 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
4c72e76
- 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.