angular-style-guide
Naming conventions, file structure, and coding standards for Angular projects. Use when naming Angular files, organizing project structure, or following Angular style guide.
65
79%
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/angular/angular-style-guide/SKILL.mdQuality
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid description that clearly communicates its purpose and includes explicit trigger guidance. Its main weakness is that the capability descriptions are somewhat categorical rather than listing specific concrete actions, and the 'coding standards' aspect could overlap with other style-related skills. The explicit 'Use when...' clause with multiple trigger scenarios is a strength.
Suggestions
Add more specific concrete actions like 'enforce kebab-case file naming, organize by feature modules, apply component/service/directive suffixes' to increase specificity.
Narrow the 'coding standards' language to be more Angular-specific (e.g., 'Angular-specific patterns like smart/dumb components, dependency injection conventions') to reduce overlap with general coding style skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Angular projects) and some actions (naming conventions, file structure, coding standards), but these are categories rather than concrete specific actions like 'enforce kebab-case file naming' or 'organize modules by feature'. | 2 / 3 |
Completeness | Clearly answers both 'what' (naming conventions, file structure, coding standards for Angular projects) and 'when' with an explicit 'Use when...' clause covering three trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'naming conventions', 'file structure', 'coding standards', 'Angular', 'naming Angular files', 'project structure', 'Angular style guide'. These cover common variations of how users would phrase requests. | 3 / 3 |
Distinctiveness Conflict Risk | While Angular-specific, 'coding standards' and 'file structure' could overlap with general coding style guides or other framework-specific skills. The Angular focus helps but 'coding standards' is broad enough to potentially conflict. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, concise Angular style guide that efficiently communicates naming conventions, folder structure, and anti-patterns. Its main strength is token efficiency and clear organization. Its weakness is moderate actionability—while the rules are specific, the skill could benefit from a few more concrete examples showing correct vs. incorrect patterns, and the single reference file cannot be verified.
Suggestions
Add a concrete before/after example showing a correctly named and structured feature module to improve actionability
Verify that 'references/naming-convention.md' exists in the bundle, or remove the reference if it doesn't exist
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It uses bullet points, bold formatting, and concrete examples without explaining basic concepts Claude already knows. Every line adds value—no padding or unnecessary context about what Angular is or why conventions matter. | 3 / 3 |
Actionability | The skill provides specific naming patterns and concrete examples (e.g., 'hero-list.component.ts', 'appHighlight'), but it's primarily a set of rules rather than executable guidance. There are no code snippets showing how to generate or scaffold files, and some guidance like 'Move to component class or computed() signal' is somewhat vague without a concrete example. | 2 / 3 |
Workflow Clarity | This is a conventions/standards skill rather than a multi-step process skill. The single-purpose nature (naming and structure conventions) is presented clearly and unambiguously. The LIFT acronym provides a clear decision framework, and the anti-patterns section serves as a validation checklist. | 3 / 3 |
Progressive Disclosure | There is a reference to 'references/naming-convention.md' which is good, but the bundle shows no files were provided, so we can't verify the reference exists. The content is well-structured with clear sections, but only one reference is provided—additional references for folder structure details or anti-pattern examples could improve navigation. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
- Repository
- HoangNguyen0403/agent-skills-standard
- Commit
3df717f
- 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.