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 is functional and clearly communicates its purpose and trigger conditions. Its main weakness is a lack of specificity about what concrete actions or guidelines it provides beyond 'creates a new Angular app,' and it could benefit from additional natural trigger terms users might use. The second sentence ('contains important guidelines for how to effectively create a modern Angular application') is vague filler that doesn't add actionable detail.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Scaffolds project structure, configures standalone components, sets up routing and lazy loading'
Include more natural trigger terms users might say, such as 'ng new', 'scaffold Angular project', 'start new Angular app', 'bootstrap 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 Angular CLI with guidelines for modern Angular) 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 React app creation, Angular component editing, or general web development skills. | 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 skill provides solid, actionable guidance for creating Angular applications with specific CLI commands and useful flags. Its main weaknesses are moderate verbosity (repeated MCP note, exhaustive generate subcommand list, persona preamble) and implicit rather than explicit error-recovery loops in the workflow. The content would benefit from tightening the generate commands into a pattern and adding explicit validation feedback loops.
Suggestions
Condense the 10 `ng generate` subcommands into a single pattern like `npx ng generate <schematic> <name>` with a brief note that schematics include component, service, pipe, directive, etc.—Claude already knows these.
Remove the opening persona statement ('You are an expert in...') as it wastes tokens on self-description Claude doesn't need.
Add an explicit error-recovery loop after `npx ng build`: 'If build fails, review errors → fix → rebuild until clean.'
Remove the duplicate MCP server note (appears both in step 1 and at the end) to improve conciseness.
| 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 since Claude already knows these. The MCP server note is repeated twice. However, the core workflow steps are reasonably focused. | 2 / 3 |
Actionability | The skill provides specific, executable commands at every step: `which ng`, `npm install -g @angular/cli`, `npx ng new <app-name> [flags] --interactive=false`, `npx ng build`, `npx ng generate component <name>`, and `npx ng add tailwindcss`. Flag options are concrete with clear usage context. Commands are copy-paste ready. | 3 / 3 |
Workflow Clarity | The steps are clearly sequenced (check CLI → create app → build features → generate code → add Tailwind), and step 3 includes a validation checkpoint (`npx ng build` to check for errors). However, there's no explicit error-recovery loop for the build step (e.g., 'if build fails, fix errors and rebuild'), and the workflow for CLI installation lacks a verification step after install. The sequence is good but validation/feedback loops are implicit rather than explicit. | 2 / 3 |
Progressive Disclosure | The content is a single file with no bundle files, which is acceptable for a skill of this scope. It references an external URL (Tailwind upgrade guide) and the MCP server for best practices, which is good. However, the long list of `ng generate` commands could be split into a reference file, and the content is somewhat monolithic—all inline with no clear separation between quick-start and reference material. | 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
06b004e
- 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.