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

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

78%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 highly actionable, well-structured Angular performance guide built on executable CORRECT/WRONG code examples and priority ordering. Its main weakness is monolithic inline content with no progressive disclosure into reference files.

Suggestions

Move the per-category code examples or the SSR/TransferState deep dive into separate reference files (e.g., references/bundle-optimization.md) and link to them from SKILL.md to improve progressive disclosure.

Trim incidental commentary such as the 'Benefits' bullet lists under Zoneless where the code already conveys the point, to push conciseness toward the lean anchor.

Add a short validation/review checkpoint (e.g., 'run a bundle analysis or lighthouse audit after applying these rules') to strengthen workflow_clarity feedback loops.

Dimension	Reasoning	Score
Conciseness	Mostly lean CORRECT/WRONG code pairs with brief comments and minimal concept re-explanation; a few 'Benefits' lists and incidental commentary could be trimmed, keeping it just below the lean/efficient anchor of 5.	4 / 5
Actionability	Provides fully executable, copy-paste-ready TypeScript/HTML examples for each rule with concrete CORRECT and WRONG variants covering the common Angular performance cases.	5 / 5
Workflow Clarity	The priority-ordered category table supplies a clear sequence and the Quick Reference Checklists act as checkpoints; not a 5 because there are no explicit validate-then-proceed feedback loops, though the task is non-destructive so the cap does not apply.	4 / 5
Progressive Disclosure	Well-organized with clear section headers, but all ~555 lines are inlined in SKILL.md with no references to separate detail files; content that could be split (e.g., per-category deep dives) remains inline.	3 / 5
	Total	16 / 20 Passed

Description

87%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 well-constructed description that clearly states both purpose and trigger conditions with Angular-specific framing. Minor room to broaden trigger-term synonyms and sharpen the 'what' beyond 'best practices guide'.

Dimension	Reasoning	Score
Specificity	Names the Angular domain and several concrete actions ('writing, reviewing, or refactoring') plus specific goals ('performance, bundle size, and rendering efficiency'); falls short of 5 because the 'best practices guide' framing is slightly generic rather than enumerating the full range of optimization actions.	4 / 5
Completeness	Explicitly answers both what ('Angular performance optimization and best practices guide') and when ('Use when writing, reviewing, or refactoring Angular code...') with concrete trigger phrases, matching the anchor structure.	5 / 5
Trigger Term Quality	Includes natural terms users would say ('Angular', 'performance', 'bundle size', 'rendering', 'refactoring'); not a 5 because it omits common synonyms or explicit file/extension triggers that would round out coverage.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (Angular-specific performance) with distinct, framework-scoped triggers, minimizing overlap with non-Angular skills.	5 / 5
	Total	18 / 20 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: sickn33/antigravity-awesome-skills
Path: skills/angular-best-practices/SKILL.md
Commit: 1f67c44

Reviewed: about 15 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.