CtrlK
BlogDocsLog inGet started
Tessl Logo

angular-performance

Angular performance: NgOptimizedImage, @defer, lazy loading, SSR. Trigger: When optimizing Angular app performance, images, or lazy loading.

74

Quality

91%

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

SKILL.md
Quality
Evals
Security

Quality

Content

90%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, highly actionable reference with executable examples and minimal padding. The main gap is the absence of explicit validation feedback loops and external progressive-disclosure files, which cap workflow_clarity and progressive_disclosure at 4.

Suggestions

Add a brief validation/checklist step for performance-critical changes (e.g., 'verify LCP image has priority', 'confirm lazy chunks load on interaction') to introduce explicit feedback loops.

Move the deeper API detail (e.g., full @defer trigger matrix or SSR provider options) into a references/ file and link to it from the body to strengthen progressive disclosure.

Add a short decision sequence for choosing between SSR, CSR, and SSG/prerender so the SSR section reads as a guided workflow rather than only a comparison table.

DimensionReasoningScore

Conciseness

Lean, code-and-table-driven body that assumes Angular competence; it avoids explaining what Angular or its primitives are, so every token earns its place.

5 / 5

Actionability

Provides copy-paste-ready, executable code for NgOptimizedImage, @defer, lazy routes, and SSR, plus concrete rules and trigger tables covering the common cases.

5 / 5

Workflow Clarity

Content is well organized with explicit rules ('ALWAYS set width/height', 'NEVER trigger reflows'), but as a multi-topic reference it lacks an explicit multi-step sequence with validation checkpoints for risky operations, keeping it just below 5.

4 / 5

Progressive Disclosure

Clear section structure with well-signaled one-level external resource links, but no bundle/reference files are used to split detail out of the main body, leaving minor organization gaps versus the ideal split-content pattern.

4 / 5

Total

18

/

20

Passed

Description

92%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 that names concrete capabilities and provides an explicit trigger clause covering both what and when. Only minor gaps in synonym/extension trigger coverage prevent a perfect trigger_term_quality score.

DimensionReasoningScore

Specificity

Names multiple concrete Angular performance techniques ('NgOptimizedImage, @defer, lazy loading, SSR'), giving comprehensive coverage of specific capabilities rather than vague language.

5 / 5

Completeness

Explicitly states both what the skill does (the four named techniques) and when to use it via a concrete 'Trigger: When optimizing...' clause, matching the anchor for clearly answering both what and when.

5 / 5

Trigger Term Quality

Includes natural trigger terms ('optimizing Angular app performance, images, or lazy loading') with good coverage, though it omits some synonyms and lacks file-extension-style triggers that would push it to 5.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Angular performance) with distinct, framework-specific triggers, making conflict with unrelated skills minimal.

5 / 5

Total

19

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Gentleman-Programming/Gentleman-Skills
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.