angular-new-app
Creates a new Angular app using the Angular CLI. This skill should be used whenver a user wants to create a new Angular application and contains important guidelines for how to effectively create a modern Angular application.
69
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
57%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 adequately identifies its niche (Angular app creation) but suffers from circular 'when' guidance and lacks specific capability details. The phrase 'important guidelines for how to effectively create a modern Angular application' is vague padding that doesn't help Claude select this skill. Stronger trigger terms and concrete actions would improve selection accuracy.
Suggestions
Replace the circular 'when' clause with explicit trigger terms: 'Use when user mentions Angular, ng new, Angular CLI, or wants to scaffold a new frontend project with Angular'
Add specific capabilities beyond 'creates': e.g., 'Scaffolds Angular projects with routing, standalone components, and modern best practices'
Remove vague filler ('important guidelines for how to effectively create') and replace with concrete details about what the skill actually does
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Angular app) and one action (creates), but lacks comprehensive details about what specific capabilities or features are involved beyond 'create'. The phrase 'important guidelines for how to effectively create' is vague filler. | 2 / 3 |
Completeness | Answers 'what' (creates Angular app using CLI) but the 'when' clause ('whenever a user wants to create a new Angular application') is essentially a tautology that restates the what, not explicit trigger guidance. | 2 / 3 |
Trigger Term Quality | Includes 'Angular app', 'Angular CLI', and 'Angular application' which are relevant keywords, but misses common variations like 'ng new', 'scaffold', 'bootstrap', 'frontend project', or 'web app'. | 2 / 3 |
Distinctiveness Conflict Risk | Angular CLI and Angular application are specific enough to distinguish from other framework skills (React, Vue, etc.) and general coding skills. Clear niche with low conflict risk. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable guidance for creating Angular applications with specific CLI commands and clear steps. However, it has some redundancy (duplicate MCP server mentions, repeated expert intro), and the workflow could benefit from explicit validation checkpoints and error recovery guidance. The structure is adequate but could better separate quick-start content from advanced features.
Suggestions
Remove the duplicate 'expert Angular developer' introduction and the repeated MCP server note to improve conciseness
Add explicit validation steps after app creation and code generation (e.g., 'Run npx ng build to verify, if errors occur: review output, fix issues, rebuild')
Consider splitting the ng generate guidelines into a separate reference file and keeping only the most common ones inline
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Contains some redundancy (expert intro repeated, MCP server note mentioned twice) and could be tightened, but mostly stays focused on actionable content without over-explaining basic concepts. | 2 / 3 |
Actionability | Provides specific, executable commands throughout (ng new, ng generate, npx ng add tailwindcss) with concrete flags and options. Commands are copy-paste ready with clear parameter placeholders. | 3 / 3 |
Workflow Clarity | Steps are numbered and sequenced, but lacks explicit validation checkpoints. Step 3 mentions running build to check errors but doesn't provide a clear feedback loop for error recovery. The workflow could benefit from explicit validation steps. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with numbered steps, but includes inline details that could be separated. References external resources (tailwind docs, MCP server) but the structure is somewhat flat without clear signposting to advanced topics. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.