CtrlK
BlogDocsLog inGet started
Tessl Logo

angular-ssr

Implement Angular SSR with hydration, TransferState caching, and per-route render modes. Use when configuring Angular Universal SSR, client hydration, static prerendering, or preventing double-fetching.

74

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is lean, highly actionable, and uses progressive disclosure well via one real reference file. Its main weaknesses are missing validation checkpoints in the SSR setup workflow and a direct contradiction between the body (recommends isPlatformBrowser for recurring checks) and references/hydration.md ("Do not use isPlatformBrowser").

Suggestions

Add explicit validation checkpoints to the workflow, e.g., after enabling hydration verify the browser console shows no NG0500+ hydration errors and that TransferState payload is populated.

Resolve the contradiction between section 2 (recommending isPlatformBrowser for recurring checks) and references/hydration.md ("Do not use isPlatformBrowser. Use Lifecycle hooks.") so the body and reference agree.

Remove the duplicate References section at the bottom, since references/hydration.md is already linked inline in section 1, or keep only one of the two links.

DimensionReasoningScore

Conciseness

Lean bullet points assume Claude's Angular competence (no explanation of what SSR/hydration is); "ng add @angular/ssr", provideClientHydration, and @defer triggers are dense and every token earns its place.

3 / 3

Actionability

Concrete commands and copy-paste API calls throughout (ng add, provideClientHydration(withEventReplay()), afterNextRender, ServerRoute[], @defer triggers) give executable guidance rather than abstractions.

3 / 3

Workflow Clarity

Steps are numbered 1-5 with a clear sequence, but there are no explicit validation/verification checkpoints (e.g., checking the browser console for hydration warnings), so checkpoints are implicit rather than enforced.

2 / 3

Progressive Disclosure

A concise overview body points to a single one-level-deep, verified reference file (references/hydration.md) signaled both inline and in a References section, with detail appropriately split out.

3 / 3

Total

11

/

12

Passed

Description

100%

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 strong, concise description that names concrete capabilities and provides an explicit Use-when trigger clause in third-person voice. It cleanly satisfies all four dimensions without fluff or over-claims.

DimensionReasoningScore

Specificity

"Implement Angular SSR with hydration, TransferState caching, and per-route render modes" lists multiple concrete, distinct capabilities rather than vague language.

3 / 3

Completeness

Explicitly answers what ("Implement Angular SSR with hydration, TransferState caching, and per-route render modes") and when ("Use when configuring Angular Universal SSR, client hydration, static prerendering, or preventing double-fetching").

3 / 3

Trigger Term Quality

"Angular Universal SSR, client hydration, static prerendering, or preventing double-fetching" covers natural terms a developer would actually say when needing this skill.

3 / 3

Distinctiveness Conflict Risk

Angular SSR is a clear niche with distinct, framework-specific triggers unlikely to collide with other skills.

3 / 3

Total

12

/

12

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.