angular-ui-patterns

Modern Angular UI patterns for loading states, error handling, and data display. Use when building UI components, handling async data, or managing component states.

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/antigravity-angular-ui-patterns/SKILL.md

The canonical home for this skill is angular-ui-patterns in sickn33/antigravity-awesome-skills

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.

The content is highly actionable with broad, executable Angular code covering loading, error, empty, form, and dialog patterns, supported by a decision tree and checklist. Its main weakness is progressive disclosure: everything is inlined in one long file with no reference files, plus minor redundancy in the error-handling and boilerplate sections.

Suggestions

Move the full component implementations (ErrorStateComponent, EmptyStateComponent, DialogService, UserFormComponent) into reference files under references/ and link to them from SKILL.md to enable progressive disclosure.

Consolidate the error-handling guidance that currently repeats across 'Error Handling Patterns', 'Anti-Patterns', and the core principles into one authoritative section.

Replace the generic 'When to Use' and 'Limitations' boilerplate with Angular-specific scope boundaries and deprecation notes (e.g. template-vs-control-flow syntax notes).

Dimension	Reasoning	Score
Conciseness	The body is dense with executable code and minimal prose, assuming Claude's competence, but error-handling guidance repeats across three sections and the trailing 'When to Use'/'Limitations' boilerplate is generic filler.	4 / 5
Actionability	Copy-paste-ready @Component examples with signals/inject, @defer blocks, a DialogService, and reactive forms cover the common cases fully and concretely.	5 / 5
Workflow Clarity	A loading-state decision tree and a 'UI State Checklist' provide clear sequencing and validation checkpoints; it is not a destructive/batch workflow so the strict validate-loop cap does not apply, but it stops short of explicit feedback loops.	4 / 5
Progressive Disclosure	Section headers are well organized but all ~510 lines live in a single SKILL.md with no bundle files; component and dialog examples that could be split into one-level references are inlined, fitting the 'content that should be separate is inline' anchor.	3 / 5
	Total	16 / 20 Passed

Description

75%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.

The description is concise, in third person, and clearly states both what the skill covers and when to use it with concrete trigger phrases. It is a solid, well-scoped description that only lacks the depth of synonyms and comprehensive action enumeration needed for a top score.

Dimension	Reasoning	Score
Specificity	Names the Angular UI domain plus several concrete action areas (loading states, error handling, data display), matching the 'lists several specific actions' anchor; not 5 because coverage is not comprehensive and actions are area-level rather than fully enumerated.	4 / 5
Completeness	Both a clear 'what' (Angular UI patterns for loading/error/data display) and an explicit 'Use when...' clause are present; the 'when' could be more specific, so it does not reach the 5 anchor.	4 / 5
Trigger Term Quality	Phrases like 'building UI components', 'handling async data', 'managing component states' are reasonably natural, but common synonyms (skeletons, spinners, empty states) and file/tech extensions are missing.	4 / 5
Distinctiveness Conflict Risk	Scoped to the Modern Angular UI-patterns niche with minimal overlap risk, though it can overlap with adjacent Angular skills like angular-state-management referenced in the body.	4 / 5
	Total	16 / 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 (518 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
Path: skills/antigravity-angular-ui-patterns/SKILL.md
Commit: 19c310e

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