angular-best-practices

Angular performance optimization and best practices guide. Use when writing, reviewing, or refactoring Angular code for optimal performance, bundle size, and rendering efficiency.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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

The body is highly actionable with concrete executable examples and clear prioritization, but it is a long monolithic file that trades conciseness and progressive disclosure for inlined detail. Splitting deep-dive categories into reference files and trimming redundant WRONG blocks would raise the weaker dimensions.

Suggestions

Move the larger deep-dive sections (SSR/TransferState, State Management, Memory Management) into reference files under references/ and summarize them one level deep in SKILL.md to improve progressive_disclosure and reduce inline length.

Trim or consolidate redundant WRONG examples where the CORRECT example already makes the contrast clear, to tighten conciseness toward the token budget.

Confirm version-sensitive guidance (e.g. 'Zoneless Angular (v20+)', experimental zoneless link) lives in a clearly marked version/compatibility note so time-sensitive details don't clutter the core rules.

Dimension	Reasoning	Score
Conciseness	Sections avoid basic-concept exposition and use lean CORRECT/WRONG pairs, but at ~560 lines across 8 categories much content (e.g. duplicated WRONG examples, full SSR TransferState service) could be tightened or offloaded; verbosity is penalized even when accurate.	2 / 3
Actionability	Every rule ships copy-paste-ready, executable TypeScript/HTML with explicit CORRECT vs WRONG contrasts and specific APIs (signals, @defer, provideZonelessChangeDetection, takeUntilDestroyed).	3 / 3
Workflow Clarity	A prioritized rule catalog rather than a fragile multi-step operation; the priority table, section ordering, and Quick Reference checklists give clear sequencing without needing validation feedback loops.	3 / 3
Progressive Disclosure	Well-organized via sections and tables, but it is a single ~560-line monolith with no references/scripts/assets bundle to offload detail (e.g. full SSR, state-management, and memory-management deep dives) that would read better one level deep.	2 / 3
	Total	10 / 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.

The description is specific, complete, and distinctive, stating concrete capabilities and an explicit 'Use when' trigger clause in third-person voice. It cleanly satisfies all four dimensions.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('writing, reviewing, or refactoring Angular code') and concrete outcomes ('performance, bundle size, and rendering efficiency') rather than vague language.	3 / 3
Completeness	Clearly answers both 'what' (Angular performance optimization and best practices guide) and 'when' via an explicit 'Use when...' clause with specific triggers.	3 / 3
Trigger Term Quality	Uses natural phrasing users would say ('writing, reviewing, or refactoring Angular code', 'performance', 'bundle size', 'rendering') with good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Clearly scoped to Angular performance with distinct, domain-specific triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (564 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: boisenoise/skills-collections
Commit: f36337d

Reviewed: about 3 hours ago

Table of Contents

Discovery Implementation Validation

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.