angular-new-app
Creates a new Angular app using the Angular CLI. This skill should be used whenever a user wants to create a new Angular application and contains important guidelines for how to effectively create a modern Angular application.
60
70%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/dev-skills/angular-new-app/SKILL.mdQuality
Discovery
75%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 communicates its purpose and includes an explicit 'when to use' clause, which is a strength. However, it could be more specific about the concrete actions involved (e.g., configuring standalone components, setting up routing, choosing CSS preprocessors) and include more natural trigger terms users might say. The second sentence is somewhat redundant and padded rather than adding new information.
Suggestions
Add more specific concrete actions beyond just 'creates a new Angular app', such as 'scaffolds project structure, configures standalone components, sets up routing and styling options'.
Include additional natural trigger terms users might say, such as 'ng new', 'scaffold Angular project', 'start new Angular project', 'bootstrap Angular app', or 'initialize Angular'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Angular) and one action (creates a new Angular app using Angular CLI), but doesn't list multiple specific concrete actions like setting up routing, configuring standalone components, adding dependencies, etc. | 2 / 3 |
Completeness | Clearly answers both what ('Creates a new Angular app using the Angular CLI') and when ('whenever a user wants to create a new Angular application'), with an explicit trigger clause. | 3 / 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', 'start a new project', or 'Angular project'. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to creating new Angular applications specifically, which is a distinct niche unlikely to conflict with other skills like general Angular development, testing, or other framework scaffolding. | 3 / 3 |
Total | 10 / 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 is a solid, actionable skill for creating Angular applications with clear CLI commands and a logical workflow. Its main weaknesses are verbosity (repeated MCP note, exhaustive generate subcommand list, unnecessary persona preamble) and missing explicit validation/error-recovery steps after key operations like project creation and build. The content would benefit from tightening and adding verification checkpoints.
Suggestions
Remove the persona preamble ('You are an expert in...') and the duplicate MCP server note to reduce token waste.
Condense the `ng generate` list to a single pattern like `npx ng generate <schematic> <name>` with a note that schematics include component, service, pipe, directive, etc.
Add explicit validation after `ng new` (e.g., 'Verify the project directory was created and `cd` into it') and a feedback loop after `npx ng build` (e.g., 'If build fails, review errors, fix, and rebuild before proceeding').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary verbosity—the opening persona statement ('You are an expert in TypeScript, Angular...') is filler Claude doesn't need, and the exhaustive list of all `ng generate` subcommands (component, service, pipe, directive, interface, guard, interceptor, resolver, enum, class) could be condensed to a single pattern. The MCP server note is repeated twice. However, the core workflow steps are reasonably focused. | 2 / 3 |
Actionability | The skill provides specific, executable commands throughout: `which ng`, `npm install -g @angular/cli`, `npx ng new <app-name> [flags] --interactive=false`, `npx ng generate component <name>`, `npx ng add tailwindcss`, and `npx ng build`. Flag options are concrete and well-documented with clear guidance on when to use each. | 3 / 3 |
Workflow Clarity | The steps are clearly numbered and sequenced, with a good check-before-proceed pattern for the CLI installation. However, there's no explicit validation checkpoint after `ng new` (e.g., verify the project was created successfully), and step 3 mentions `npx ng build` for error checking but doesn't provide a feedback loop for handling build failures. The workflow for destructive/generative operations lacks explicit verify-then-proceed gates. | 2 / 3 |
Progressive Disclosure | The content is reasonably structured with numbered steps and important callouts, but it's a single monolithic file with no references to supporting documents. The lengthy `ng generate` list and Tailwind section could be split into separate reference files. The external link to Tailwind docs is appropriate, but there are no bundle files to support progressive disclosure. | 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.
- Repository
- angular/angular
- Commit
642fd43
- 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.