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.

63

Quality

75%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/angular-best-practices/SKILL.md

The canonical home for this skill is angular-best-practices in sickn33/agentic-awesome-skills

SKILL.md
Quality
Evals
Security

Quality

Content

72%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-organized Angular performance reference with strong executable examples, weakened only by its monolithic single-file structure and absence of an explicit optimization workflow with validation steps.

Suggestions

Move detailed pattern catalogs (e.g., SSR/TransferState, virtual scrolling) into one-level-deep reference files linked from SKILL.md to improve progressive disclosure.

Remove the duplicated 'When to Use' section and the generic closing sentence to tighten token efficiency.

Add a short prioritized 'how to audit an existing Angular app' workflow with explicit validation checkpoints so the rules map onto a concrete sequence.

DimensionReasoningScore

Conciseness

The body is mostly lean, actionable CORRECT/WRONG code with little concept re-explanation, but minor padding could be trimmed: the duplicated "When to Use" section and the generic closing line "This skill is applicable to execute the workflow or actions described in the overview."

4 / 5

Actionability

It provides abundant copy-paste-ready TypeScript and HTML examples across change detection, async, bundling, rendering, SSR, and memory, with explicit CORRECT/WRONG comparisons covering the common Angular performance cases.

5 / 5

Workflow Clarity

Content is organized as a prioritized rule catalog with review checklists, but there is no explicit multi-step optimization workflow with validation checkpoints; the sequence is implied by priority ordering rather than sequenced steps.

3 / 5

Progressive Disclosure

No bundle files exist and the entire ~560-line guide is inlined in SKILL.md; while it is well-sectioned with a priority table and checklists, detailed pattern catalogs that could live in one-level-deep reference files are not split out.

3 / 5

Total

15

/

20

Passed

Description

78%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 cleanly answers both what the skill does and when to use it with concrete, natural trigger terms in third-person voice. It is slightly held back by an abstract capability statement ("best practices guide") rather than enumerated concrete actions.

DimensionReasoningScore

Specificity

Names the Angular performance domain and lists activities ("writing, reviewing, or refactoring Angular code"), but the stated capability is an abstract "best practices guide" rather than concrete skill-specific actions, so it stops at naming the domain with 1-2 concrete actions.

3 / 5

Completeness

It explicitly states what it is ("Angular performance optimization and best practices guide") and gives concrete trigger phrases for when to use it ("Use when writing, reviewing, or refactoring Angular code for optimal performance, bundle size, and rendering efficiency"), satisfying both what and when.

5 / 5

Trigger Term Quality

Natural terms a developer would say are present ("Angular", "writing", "reviewing", "refactoring", "bundle size", "rendering"), giving good keyword coverage, though a few common synonyms like "optimization" or "change detection" are absent.

4 / 5

Distinctiveness Conflict Risk

The Angular performance niche is clear and unlikely to trigger for unrelated skills, with only minor overlap risk against a generic Angular or code-review skill.

4 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (563 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
administrakt0r/AI-Agents-Safe-Coding-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.