CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

76%

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 ./skills/dev-skills/angular-new-app/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a highly actionable, command-first guide with a clear sequenced workflow and appropriate validation guidance for a scaffold task. Its main inefficiencies are persona boilerplate and a duplicated MCP best-practices note that could be trimmed to one callout.

DimensionReasoningScore

Conciseness

Mostly efficient command-first content, but the role-play boilerplate ("You are an expert in TypeScript, Angular, and scalable web application development...") and the near-duplicate MCP best-practices note (repeated in step 1 and step 5) are unnecessary padding.

3 / 5

Actionability

Fully executable, copy-paste-ready commands cover the common cases: `which ng` / `where ng`, `npm install -g @angular/cli`, `npx ng new <app-name> [flags] --interactive=false --ai-config=...`, the full `npx ng generate` catalog, and `npx ng add tailwindcss`, plus concrete flag examples (`--style=scss|css|less`, `--routing`, `--ssr`).

5 / 5

Workflow Clarity

A clear five-step sequence with checkpoints (confirm CLI presence, ask before installing, load the AI config, do not start the app until features exist) and a build-check feedback loop, but the validation step is offered only optionally ("You can always run `npx ng build`"), leaving a minor checkpoint gap versus anchor 5.

4 / 5

Progressive Disclosure

A single-file, single-purpose skill with well-organized numbered steps and bold labels; no bundle files exist and none are strictly needed, though the ten-item generate-command catalog and the duplicated best-practices note sit inline without section headers for navigation.

4 / 5

Total

16

/

20

Passed

Description

66%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 clearly states a single concrete capability and an explicit use-when clause in third person, with negligible conflict risk. Its weaknesses are repetitive trigger vocabulary and a padded trailing clause that adds no specific capability.

Suggestions

Replace the filler clause 'contains important guidelines for how to effectively create a modern Angular application' with a second concrete capability (e.g., 'configures styling, routing, SSR, and tailwind') to raise specificity.

Add natural trigger variations such as 'project', 'scaffold', or 'Angular workspace' to the when clause so it reads like 'Use when the user wants to create, scaffold, or start a new Angular app or project.'

Add a couple of concrete trigger phrases to the when clause (e.g., 'when the user mentions ng new or starting an Angular project') to reach full completeness.

DimensionReasoningScore

Specificity

"Creates a new Angular app using the Angular CLI" is one concrete action, but the rest ("contains important guidelines for how to effectively create a modern Angular application") is vague filler, so coverage is not comprehensive enough for anchor 4.

3 / 5

Completeness

Both what ("Creates a new Angular app using the Angular CLI") and when ("should be used whenever a user wants to create a new Angular application") are explicit, but the when clause merely restates the what without additional concrete trigger phrases, falling short of anchor 5.

4 / 5

Trigger Term Quality

Relevant keywords ("Angular", "Angular CLI", "new Angular app(lication)") exist but are repetitive variants of a single term; common variations like "project", "scaffold", or "workspace" are missing.

3 / 5

Distinctiveness Conflict Risk

"Angular" and "Angular CLI" carve out a clear niche with distinct triggers; minimal overlap with any other skill, matching the anchor-5 example pattern.

5 / 5

Total

15

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

angular/angular

Path

skills/dev-skills/angular-new-app/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.