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.

67

Quality

82%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Discovery

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.

This is an excellent skill description that concisely covers specific capabilities, includes a clear 'Use when' clause with natural trigger terms, and occupies a distinct niche. It uses proper third-person voice and avoids vague language or unnecessary verbosity. The description effectively enables Claude to distinguish this skill from other Angular or general web development skills.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'implement Angular SSR with hydration', 'TransferState caching', and 'per-route render modes'. These are precise, actionable capabilities rather than vague language.

3 / 3

Completeness

Clearly answers both 'what' (implement Angular SSR with hydration, TransferState caching, per-route render modes) and 'when' (explicit 'Use when' clause covering configuring Angular Universal SSR, client hydration, static prerendering, or preventing double-fetching).

3 / 3

Trigger Term Quality

Includes strong natural keywords users would search for: 'Angular SSR', 'hydration', 'TransferState', 'Angular Universal', 'static prerendering', 'double-fetching', 'render modes'. These cover the main terms developers would naturally use when seeking help with this topic.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with Angular-specific SSR terminology (TransferState, Angular Universal, hydration, per-route render modes). Unlikely to conflict with general web development or other framework-specific skills.

3 / 3

Total

12

/

12

Passed

Implementation

64%

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 skill that covers the key aspects of Angular SSR configuration. Its main weakness is the gap between describing what to do and showing exactly how to do it—several sections mention APIs and patterns without providing executable code snippets. Adding validation steps (e.g., how to verify hydration is active) and more concrete code examples would significantly improve it.

Suggestions

Add executable code examples for TransferState usage, ServerRoute[] configuration in app.routes.server.ts, and @defer hydration syntax—these are currently described but not shown.

Add a validation/verification step, such as checking the browser console for hydration mismatch warnings or inspecting the server-rendered HTML to confirm SSR is working.

Ensure the referenced references/hydration.md file exists in the bundle, or inline the critical hydration setup code directly in the skill.

DimensionReasoningScore

Conciseness

The content is lean and efficient. Every section delivers specific, actionable information without explaining what SSR is or how Angular works. No unnecessary padding or concept explanations.

3 / 3

Actionability

Provides specific commands (ng add), specific API names, and clear guidance on which render mode to use when. However, it lacks executable code examples for key steps like TransferState usage, render mode configuration in app.routes.server.ts, and the defer hydration syntax—these are described rather than shown as copy-paste ready code.

2 / 3

Workflow Clarity

Steps are numbered and logically sequenced from enabling hydration through configuring render modes. However, there are no validation checkpoints—no way to verify hydration is working, no testing steps to confirm SSR output, and no feedback loop for diagnosing common SSR failures like missing platform checks.

2 / 3

Progressive Disclosure

References a hydration.md file for detailed examples which is good structure, but the bundle has no files provided so we can't verify the reference exists. Other sections (TransferState, render modes, incremental hydration) could benefit from their own reference files rather than being briefly described inline without executable examples.

2 / 3

Total

9

/

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.

Validation9 / 11 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

9

/

11

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.