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.
87
86%
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 concisely covers specific capabilities, includes natural trigger terms developers would use, explicitly states both what it does and when to use it, and occupies a clear niche. It uses proper third-person voice and avoids vague language or unnecessary verbosity.
| 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). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Angular SSR', 'hydration', 'TransferState', 'Angular Universal', 'static prerendering', 'double-fetching', 'render modes'. These cover the main terms developers would use when seeking help with this topic. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche in Angular SSR/Universal. The specific terms like 'TransferState', 'hydration', 'per-route render modes', and 'Angular Universal' are unlikely to conflict with other skills, as they target a very specific Angular feature set. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%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 configuration effectively. Its main weakness is the lack of executable code examples for key configurations (TransferState, server routes, @defer) and the absence of validation steps to confirm SSR and hydration are working correctly.
Suggestions
Add a copy-paste ready code example for app.routes.server.ts showing ServerRoute[] configuration with different RenderMode values
Add a brief validation step, e.g., 'Verify SSR: run `ng serve --ssr` and check page source for server-rendered HTML' or 'Confirm hydration: look for no console warnings about hydration mismatch'
Include a concrete TransferState code snippet showing manual usage pattern, since the current guidance only names the API without showing how to use it
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It assumes Claude knows Angular concepts and doesn't waste tokens explaining what SSR, hydration, or TransferState are. Every section delivers actionable information without padding. | 3 / 3 |
Actionability | Provides specific commands (ng add), specific API calls (provideClientHydration, withEventReplay), and named types (RenderMode.Prerender), but lacks executable code examples for key steps like TransferState usage, render mode configuration in app.routes.server.ts, or the @defer syntax. The guidance is concrete but not fully copy-paste ready. | 2 / 3 |
Workflow Clarity | Steps are numbered and logically sequenced from enabling hydration through configuring render modes, but there are no validation checkpoints. There's no guidance on how to verify SSR is working correctly, no feedback loops for common errors, and no way to confirm hydration or TransferState are functioning as expected. | 2 / 3 |
Progressive Disclosure | The skill provides a clear, concise overview with well-signaled one-level-deep references to hydration.md. Content is appropriately split between the overview and reference material, and the structure is easy to navigate. | 3 / 3 |
Total | 10 / 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.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
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
- Commit
4c72e76
- 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.