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. (triggers: **/*.server.ts, server.ts, hydration, transferState, afterNextRender, isPlatformServer, RenderMode)
86
82%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
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 clearly defines specific capabilities (SSR, hydration, TransferState caching, render modes), provides explicit 'Use when' guidance with multiple trigger scenarios, and includes concrete file patterns and API-level trigger terms. It is concise, uses third-person voice, and would be highly distinguishable in a large skill library.
| Dimension | Reasoning | Score |
|---|---|---|
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, plus explicit trigger patterns). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Angular Universal SSR', 'client hydration', 'static prerendering', 'double-fetching', plus explicit file pattern triggers like '**/*.server.ts', 'transferState', 'afterNextRender', 'isPlatformServer', 'RenderMode'. These are terms developers would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Angular SSR specifically, with unique triggers like 'isPlatformServer', 'RenderMode', 'TransferState', and '*.server.ts' file patterns. Unlikely to conflict with general Angular or general SSR skills due to the specificity of the combined domain. | 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 Angular SSR comprehensively across multiple Angular versions. Its main weaknesses are the lack of executable code examples (particularly for TransferState and render mode configuration) and the absence of validation/verification steps for an operation that can silently produce incorrect behavior. The progressive disclosure is partially implemented with only one reference file linked.
Suggestions
Add executable code snippets for TransferState usage and `app.routes.server.ts` configuration, as these are the most error-prone areas and currently only have abstract descriptions.
Add validation checkpoints such as 'Verify hydration is working: check browser console for Angular hydration warnings' or 'Confirm TransferState: inspect Network tab to verify no duplicate API calls on client.'
Add reference links for render modes and incremental hydration (e.g., `references/render-modes.md`, `references/incremental-hydration.md`) to match the progressive disclosure pattern already started with `references/hydration.md`.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Every section is tightly written with no unnecessary explanations of what SSR is or how Angular works. Each bullet earns its place by providing specific APIs, methods, or patterns. | 3 / 3 |
Actionability | Provides specific API names and commands (e.g., `ng add @angular/ssr`, `provideClientHydration(withEventReplay())`), but lacks executable code examples for key steps like TransferState usage, render mode configuration in `app.routes.server.ts`, or the `@defer` syntax in context. The guidance is concrete but not copy-paste ready. | 2 / 3 |
Workflow Clarity | Steps are numbered and sequenced logically (enable hydration → guard browser code → prevent double-fetching → configure render modes → incremental hydration), but there are no validation checkpoints or verification steps. For SSR setup, which can silently fail or produce hydration mismatches, explicit validation steps (e.g., checking hydration warnings in console, verifying TransferState is working) would be valuable. | 2 / 3 |
Progressive Disclosure | There is a reference to `references/hydration.md` mentioned twice, but the other topics (TransferState, render modes, incremental hydration) lack corresponding reference links despite being complex enough to warrant detailed examples in separate files. The structure is reasonable but the reference coverage is incomplete. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- HoangNguyen0403/agent-skills-standard
- Commit
19a1140
- 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.