CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

angular-development

Comprehensive Angular framework development covering components, directives, services, dependency injection, routing, and reactive programming based on official Angular documentation

Quality

56%

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/luxor-frontend-essentials/skills/angular-development/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

This is a documentation-style dump of standard Angular patterns: the code is high quality and mostly executable, but the skill assumes Claude knows nothing about one of the most widely documented frameworks, burning enormous context on material Claude already has. It defines no task workflows despite advertising many, and makes no use of progressive disclosure — everything lives in a single 1,600-line file.

Suggestions

Cut the body to a lean overview (trigger guidance plus the few genuinely non-obvious patterns, e.g., current signal/model/input APIs and control-flow syntax) and move the example library, testing guide, migration guide, and RxJS patterns into references/ files linked one level deep.

Delete explanatory prose for basics Claude knows ('Components are the fundamental building blocks...') and redundant good/avoid pairs for well-known patterns; keep only version-sensitive or commonly-misused material.

Add at least one task-oriented workflow with ordered steps and a verification checkpoint — e.g., a migration sequence (audit for NgModules → convert to standalone → run build/tests → verify) — since the skill claims to support migration and optimization tasks.

DimensionReasoningScore

Conciseness

The body is ~1,600 lines / 39KB that extensively restates core Angular knowledge Claude already has — e.g., 'Components are the fundamental building blocks of Angular applications' and 'Services provide shared functionality across components' — followed by dozens of standard documentation examples (basic component, lifecycle hooks, CRUD service, form validation, control flow). This is the anchor-1 pattern: severely verbose, extensively explaining known concepts; virtually none of it is knowledge Claude lacks, and every token competes with the conversation for context.

1 / 5

Actionability

The code examples are concrete, typed, and mostly copy-paste ready (standalone bootstrap with provideRouter/provideHttpClient, inject()-based services, functional guards, model()/input()/output()), matching anchor 4's 'mostly executable... minor gaps'. It misses anchor 5 because several snippets are not self-contained — the routes example calls inject(AuthGuard) with no import, UserDetailComponent references an undefined UserService import path, and the smart/container and virtual-scroll examples depend on components and interfaces never defined in the skill.

4 / 5

Workflow Clarity

Despite claiming to cover eleven task types (building, migrating, optimizing, testing...), the body contains no sequenced workflow for any of them — it is a topic-organized reference dump with no steps, no order of operations, and no validation or verification checkpoints (not even in the Migration Guide, which shows before/after code but no process). This matches anchor 2 ('rough sequence present but many gaps... steps poorly defined') more than 3, since not even an implicit step sequence exists for accomplishing a task.

2 / 5

Progressive Disclosure

There are no bundle files at all, so everything — testing guide, migration guide, RxJS patterns, performance section, ~15 full code examples — is inlined in one monolithic SKILL.md. Section headers do provide navigation, lifting it above anchor 2's 'minimal structure... no section headers', but anchor 3's core clause applies strongly: content that clearly belongs in separate reference files is inline, and there are no external references to signal.

3 / 5

Total

10

/

20

Passed

Description

61%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 identifies its niche clearly and uses mostly natural trigger terms, but it reads as a topic inventory rather than a capability statement: no concrete actions, no 'when to use' guidance, and mild filler ('Comprehensive', 'based on official Angular documentation'). It sits solidly at the middling anchors across all dimensions.

Suggestions

Add an explicit trigger clause, e.g., 'Use when building, debugging, or migrating Angular applications, or when the user mentions Angular, components, services, RxJS, or signals.'

Replace the topic list with concrete actions: 'Build standalone components and services, set up routing with guards, write reactive forms, migrate NgModule apps to standalone' instead of 'covering components, directives, services...'.

Drop the filler 'Comprehensive' and 'based on official Angular documentation' — they add no trigger value and read as over-claim padding.

DimensionReasoningScore

Specificity

The description names the domain ('Angular framework development') and lists topical areas ('components, directives, services, dependency injection, routing, and reactive programming') but these are noun-phrase topics, not concrete actions — there is no verb beyond 'covering'. It matches anchor 3 (domain plus some specifics, not comprehensive) better than anchor 4, which requires several specific actions (e.g., 'build', 'migrate', 'test'), none of which are stated.

3 / 5

Completeness

The 'what' is reasonably clear (Angular development covering the listed areas), but there is no 'Use when...' clause or any equivalent trigger guidance — 'based on official Angular documentation' is provenance, not a when-to-use condition. Per the judging guideline, a missing 'Use when...' clause caps completeness at 3, which is exactly the anchor: clear 'what', 'when' missing.

3 / 5

Trigger Term Quality

Terms like 'Angular', 'components', 'services', 'dependency injection', 'routing', and 'reactive programming' are natural phrases users would say, giving good keyword coverage. It falls short of anchor 5's 'comprehensive coverage of natural terms including synonyms' because common variations users actually say — TypeScript, RxJS, signals, standalone components, Angular CLI — are absent from the description (they appear only in frontmatter tags, which is not the evaluated text).

4 / 5

Distinctiveness Conflict Risk

'Angular framework development' carves out a clear niche distinct from other framework skills and is unlikely to trigger the wrong skill, matching anchor 4 ('mostly distinct; minor overlap risk'). It is not a 5 because 'Comprehensive... development' is broad enough to overlap with generic frontend/TypeScript skills, and the buzzword 'Comprehensive' adds no distinguishing trigger.

4 / 5

Total

14

/

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (1629 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

manutej/luxor-claude-marketplace

Path

plugins/luxor-frontend-essentials/skills/angular-development/SKILL.md

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.