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.
85
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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 via a 'Use when' clause. Its main weakness is that the capability descriptions are somewhat categorical rather than listing specific concrete actions, and there's moderate overlap risk with general coding standards skills. The trigger terms are well-chosen and natural.
Suggestions
Add more specific concrete actions, e.g., 'Enforces kebab-case file naming, component/service/module suffixes, feature-based folder organization, and Angular style guide conventions.'
Strengthen distinctiveness by mentioning Angular-specific artifacts like 'components, directives, pipes, services, modules' to further differentiate from generic coding standards 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: naming files, organizing structure, or following the style guide. | 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, it could overlap with general coding standards skills or other framework-specific style guide skills. The terms 'coding standards' and 'file structure' are somewhat generic, though 'Angular' narrows the scope. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
85%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-crafted conventions skill that is concise, well-organized, and appropriately structured for its purpose. Its main weakness is that it's more of a reference/rules document than an actionable guide — it tells Claude what conventions to follow but doesn't show executable examples of applying them (e.g., generating a component with the right structure). The anti-patterns section is a nice touch that adds practical value.
Suggestions
Add a concrete example showing a complete feature folder structure with actual files to make the folder structure guidance more actionable (e.g., a tree view of a 'heroes' feature module).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. Every line conveys a specific rule or convention. No unnecessary explanations of what Angular is or how components work — assumes Claude's competence throughout. | 3 / 3 |
Actionability | Provides specific naming patterns and concrete examples (e.g., 'hero-list.component.ts', 'appHighlight'), but lacks executable code snippets showing how to apply these conventions in practice. The guidance is concrete but more descriptive than executable. | 2 / 3 |
Workflow Clarity | This is a conventions/standards skill rather than a multi-step process skill. The single-purpose nature (naming and structure rules) is presented unambiguously with clear, specific rules. No destructive or batch operations require validation checkpoints. | 3 / 3 |
Progressive Disclosure | Content is well-organized into logical sections (Principles, Naming, Folder Structure, Anti-Patterns) with a clear reference link to a deeper naming conventions file. For a skill of this size and scope, the structure is appropriate with one-level-deep references. | 3 / 3 |
Total | 11 / 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
4c72e76
- 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.