CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

64

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/angular-best-practices/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 well-structured, token-efficient overview that practices clean progressive disclosure by deferring detail to a single verified reference. Its main weakness is actionability: the body contains no concrete Angular guidance or executable examples, relying entirely on the referenced guide for the actual procedure.

Suggestions

Add 2-3 concise inline code snippets or concrete rules (e.g., a canonical OnPush + Signals example or a trackBy pattern) so the body offers immediately actionable guidance without requiring the reference for common cases.

Surface one prioritized quick-win checklist inline (e.g., top 3 performance rules by impact) to give Claude a concrete starting point before loading the full guide.

Make the body's workflow slightly more explicit by numbering the steps (read guide -> apply mandatory safety/validation -> ask if inputs missing) so the sequence and checkpoint are unambiguous.

DimensionReasoningScore

Conciseness

The body is lean (~25 lines), assumes Claude's competence, and avoids explaining concepts Claude already knows; the brief intro line is the only mild restatement of the description and every token earns its place.

5 / 5

Actionability

The body itself provides only high-level pointers ('Read the detailed guide', 'Treat its safety, prerequisites, and validation requirements as mandatory') with no concrete Angular code, commands, or specific steps; executable guidance is entirely deferred to the reference, so it sits below the midpoint rather than at 3 where partial concrete guidance appears.

2 / 5

Workflow Clarity

A reading workflow is implied (read the guide, follow its mandatory requirements, load sections vs. read fully) with an explicit 'Stop and ask for clarification' checkpoint, but there is no sequenced multi-step operational process with concrete validation checkpoints in the body itself.

3 / 5

Progressive Disclosure

A clear overview with a single well-signaled one-level-deep reference (references/detailed-guide.md, verified to exist at 549 lines), clean section structure (Detailed Guide, When to Use, Limitations), and easy navigation; content is appropriately split between overview and reference.

5 / 5

Total

15

/

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 strong, third-person description that clearly states both capability and activation triggers with Angular-specific scoping. It is concise and well-targeted, with only minor room for more granular action verbs and synonym coverage.

DimensionReasoningScore

Specificity

Names the Angular performance domain plus several concrete actions ('writing, reviewing, or refactoring') and focus areas ('performance, bundle size, and rendering efficiency'), with only minor coverage gaps; not a 5 because the actions are somewhat generic across code skills rather than uniquely specific to performance work.

4 / 5

Completeness

Explicitly answers both what ('Angular performance optimization and best practices guide') and when ('Use when writing, reviewing, or refactoring Angular code for optimal performance, bundle size, and rendering efficiency') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ('writing, reviewing, or refactoring Angular code', 'bundle size', 'rendering') with good coverage; not a 5 because it lacks common synonyms or variant phrasings a user might naturally use.

4 / 5

Distinctiveness Conflict Risk

Angular-specific niche with distinct performance/refactoring triggers and minimal overlap risk; the framework scoping makes it unlikely to fire for non-Angular skills.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
sickn33/agentic-awesome-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.