CtrlK
BlogDocsLog inGet started
Tessl Logo

angular-rxjs-interop

Bridge Observables and Signals using toSignal and toObservable in Angular. Use when converting between RxJS Observables and Angular Signals.

64

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/angular/angular-rxjs-interop/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 well-structured, actionable patterns skill with good progressive disclosure via one real reference file. The main gap is the absence of a sequenced workflow with validation checkpoints, which keeps workflow clarity mid-range.

Suggestions

Remove the duplicated auto-unsubscribe statement (present in both the first principle and the 'Auto-Unsubscribe' bullet) to tighten conciseness.

Add one complete, copy-paste-ready component example (e.g. a search box wiring toObservable -> debounceTime -> switchMap -> toSignal) to lift actionability to fully executable.

Add a short ordered workflow for the common HTTP-to-template flow (fetch -> toSignal with initialValue -> render {{ users() }}) with an explicit checkpoint for handling undefined/error states.

DimensionReasoningScore

Conciseness

Mostly lean bullet structure that assumes Angular competence, with minor redundancy such as restating 'toSignal auto-unsubscribes' across the Principles and Auto-Unsubscribe bullets.

4 / 5

Actionability

Provides concrete, near-executable snippets ('http.get<User[]>(...).pipe(catchError(() => of([])))', 'toSignal(..., { initialValue: [] })', 'toObservable(this.query)', 'takeUntilDestroyed(destroyRef)'), though they are fragmentary rather than full copy-paste components.

4 / 5

Workflow Clarity

Guidance is organized by category (Async->Sync, Sync->Async, Cleanup) but there is no sequenced multi-step workflow with explicit validation checkpoints; acceptable for a patterns reference, though the anchors cap at this level without clearer sequencing.

3 / 5

Progressive Disclosure

Clear sectioned overview (Principles, Guidelines, Anti-Patterns, References) with a single, well-signaled one-level-deep link to the real references/observables-vs-signals.md file; minor room to split more detail out.

4 / 5

Total

15

/

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 tight, third-person description that cleanly answers both what the skill does and when to use it, with strong natural trigger terms. Slightly more breadth in listed actions would push specificity and trigger coverage to the top level.

DimensionReasoningScore

Specificity

Names the Angular/RxJS domain and concrete APIs ('toSignal', 'toObservable') as the bridging actions, but stops at two functions rather than a fuller action set, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly states the 'what' ('Bridge Observables and Signals using toSignal and toObservable in Angular') and the 'when' ('Use when converting between RxJS Observables and Angular Signals') with concrete trigger phrasing.

5 / 5

Trigger Term Quality

Includes natural user-facing terms ('Observables', 'Signals', 'toSignal', 'toObservable', 'RxJS', 'Angular') plus the phrase 'converting between RxJS Observables and Angular Signals'; a few synonyms or casual variants are missing.

4 / 5

Distinctiveness Conflict Risk

The RxJS-to-Signals interop niche with named APIs is sharply distinct from generic Angular skills and unlikely to trigger incorrectly.

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.