CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

angular-rxjs-interop

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

Quality

79%

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

78%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 tight, well-organized reference skill: concrete API guidance, clear direction-selection rules, useful anti-patterns, and exemplary offloading of detail to a single real reference file. Weaknesses are minor — a duplicated auto-unsubscribe bullet, one vague loading-state guideline, and code fragments with ellipses instead of complete examples.

Suggestions

Remove the duplicate auto-unsubscribe bullet and fold it into the first Principle to save tokens.

Replace the vague "Handle async loading states" with a concrete pattern, e.g. a loading signal fed by toSignal over a status$ stream.

Complete the http.get fragment (show the inject(HttpClient) call and full pipe) or point to the reference file for the full HTTP example instead of using ellipses.

DimensionReasoningScore

Conciseness

The body is lean and assumes Angular competence with no conceptual padding, but it states the same fact twice — "toSignal auto-unsubscribes on component destroy" in the first Principle and again in a dedicated "Auto-Unsubscribe: toSignal automatically unsubscribes" bullet — which could be trimmed.

4 / 5

Actionability

Concrete API signatures appear throughout ("toSignal(observable$, { initialValue: defaultValue })", "takeUntilDestroyed(destroyRef)", "{{ users() }}"), but several snippets are fragments with ellipses, e.g. "http.get<User[]>(...).pipe(...)", rather than copy-paste-ready code in the body.

4 / 5

Workflow Clarity

For a single-purpose guidance skill the direction-selection is unambiguous (async→sync via toSignal, sync→async via toObservable, manual cleanup via takeUntilDestroyed), but the "Race Conditions: Handle async loading states" guidance is vague about how, leaving a minor gap.

4 / 5

Progressive Disclosure

A ~30-line well-sectioned overview (Principles, Guidelines, Anti-Patterns) with a single clearly-signaled one-level-deep reference — references/observables-vs-signals.md, verified to exist — that appropriately holds the comparison table and full code examples.

5 / 5

Total

17

/

20

Passed

Description

73%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 concise, well-targeted description in third person with both a what and a when clause and strong, specific trigger terms. Its main limitation is that the when-clause is circular (restates the what) and the action coverage stops at the two conversion functions.

Suggestions

Expand the 'Use when' clause with concrete scenarios beyond restating the what, e.g. "Use when rendering Observables in templates, debouncing signal-driven searches, or cleaning up manual subscriptions in Angular components".

Mention the cleanup capability (takeUntilDestroyed / auto-unsubscribe on destroy) in the what-clause to broaden action coverage beyond the two conversion functions.

Add natural synonym phrasings users might say, such as "convert an Observable to a Signal" or "reactive state in Angular", to strengthen trigger coverage.

DimensionReasoningScore

Specificity

"Bridge Observables and Signals using toSignal and toObservable in Angular" names the domain and exactly two concrete actions, matching the 1-2-actions anchor; it omits cleanup (takeUntilDestroyed) and HTTP/loading use cases the skill body covers, so it is not the several-actions level above.

3 / 5

Completeness

Both what ("Bridge Observables and Signals using toSignal and toObservable") and an explicit when ("Use when converting between RxJS Observables and Angular Signals") are present, but the when-clause merely restates the what instead of adding concrete trigger scenarios, so it falls short of the fully-explicit anchor 5.

4 / 5

Trigger Term Quality

Includes natural terms users would say — "toSignal", "toObservable", "rxjs angular", "converting between RxJS Observables and Angular Signals" — but misses common variations like "observable to signal" or "reactive state", fitting the good-coverage-with-a-few-missing anchor.

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche — Angular RxJS/Signals interop with named functions — so it is highly distinguishable from other skills with minimal wrong-trigger risk.

5 / 5

Total

16

/

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.

Validation — 14 / 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

Path

skills/angular/angular-rxjs-interop/SKILL.md

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.