angular-rxjs-interop
Bridge Observables and Signals using toSignal and toObservable in Angular. Use when converting between RxJS Observables and Angular Signals.
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-rxjs-interop/SKILL.mdQuality
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, focused skill description that clearly identifies its niche at the intersection of RxJS Observables and Angular Signals. It includes an explicit 'Use when' clause and strong trigger terms. The main weakness is that the 'what' portion could be more specific about the concrete actions beyond just 'bridging' (e.g., handling initial values, managing subscriptions, error handling).
Suggestions
Expand the capabilities list with more concrete actions, e.g., 'Bridge Observables and Signals using toSignal and toObservable in Angular, including handling initial values, managing subscription lifecycle, and configuring requireSync options.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Angular Signals/RxJS Observables) and the specific functions (toSignal, toObservable), but doesn't list multiple concrete actions beyond 'bridge' and 'converting'. Could elaborate on specific use cases like handling initial values, error handling, or cleanup. | 2 / 3 |
Completeness | Clearly answers both 'what' (bridge Observables and Signals using toSignal and toObservable in Angular) and 'when' (Use when converting between RxJS Observables and Angular Signals) with an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'toSignal', 'toObservable', 'Observables', 'Signals', 'RxJS', 'Angular', and 'converting'. These cover the main terms a developer would use when seeking help with this specific task. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting the interop between RxJS Observables and Angular Signals with named functions (toSignal, toObservable). Unlikely to conflict with general Angular skills or general RxJS skills due to the precise scope. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides useful, domain-specific guidance for Angular RxJS-Signal interop with appropriate anti-patterns and practical tips. However, it lacks complete executable code examples (e.g., a full component showing the toSignal/toObservable pattern), has some redundancy (auto-unsubscribe mentioned twice), and the workflow for common patterns could be more explicitly sequenced. The referenced bundle file is missing, weakening progressive disclosure.
Suggestions
Add a complete, executable component example showing the full toSignal + toObservable workflow (e.g., a search component with debounceTime and switchMap) instead of inline fragments.
Remove the redundant 'Auto-Unsubscribe' bullet under Principles since it's already stated in the first bullet point.
Provide the referenced 'references/observables-vs-signals.md' file or remove the reference if it doesn't exist.
Structure the HTTP request guidance as a numbered workflow with explicit steps (create observable → add error handling → convert to signal → use in template).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but has some redundancy — 'Auto-Unsubscribe' is stated as a principle and then repeated verbatim. Some bolding is excessive. The content generally assumes Claude's competence with Angular/RxJS concepts but could be tighter. | 2 / 3 |
Actionability | Provides inline code snippets and specific API calls (toSignal, toObservable, takeUntilDestroyed) but lacks complete, executable code examples. The snippets are fragments rather than copy-paste ready blocks showing full component usage patterns. | 2 / 3 |
Workflow Clarity | The Sync-to-Async flow (Signal → toObservable → RxJS operators → toSignal → template) is described but not laid out as a clear step-by-step sequence. The HTTP request guidance is useful but lacks explicit validation or error-handling checkpoints beyond a brief catchError mention. | 2 / 3 |
Progressive Disclosure | References a file 'references/observables-vs-signals.md' which is good progressive disclosure, but no bundle files are provided to verify it exists. The content is reasonably organized into sections but the Principles section is dense and could benefit from splitting detailed patterns into a referenced file. | 2 / 3 |
Total | 8 / 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
556618c
- 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.