angular-architecture
Angular architecture: Scope Rule, project structure, file naming, style guide. Trigger: When structuring Angular projects or deciding where to place components.
Install with Tessl CLI
npx tessl i github:Yoizen/dev-ai-workflow --skill angular-architecture86
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
67%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 covers the 'when' with an explicit trigger clause, which is a strength. However, it lacks concrete action verbs and reads more like a topic list than a capability description. The trigger terms are reasonable but could include more natural user phrasings.
Suggestions
Rewrite capabilities with action verbs: 'Enforces Angular Scope Rule, organizes project structure, applies file naming conventions, implements style guide standards'
Expand trigger terms to include natural user phrases: 'folder organization', 'where should I put this service', 'naming conventions', 'Angular best practices', 'module structure'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Angular) and lists some areas (Scope Rule, project structure, file naming, style guide), but these are categories rather than concrete actions. Missing specific verbs like 'organize', 'create', 'enforce'. | 2 / 3 |
Completeness | Explicitly answers both what (Angular architecture topics) and when with a clear 'Trigger:' clause specifying 'When structuring Angular projects or deciding where to place components'. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'Angular projects', 'components', 'structuring', but missing common variations users might say like 'folder structure', 'naming conventions', 'where to put files', 'Angular best practices'. | 2 / 3 |
Distinctiveness Conflict Risk | Specific to Angular which helps distinguish it, but 'project structure' and 'style guide' could overlap with general code organization skills. The Angular focus provides some distinctiveness but could conflict with broader architecture skills. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill file that exemplifies concise, actionable documentation. The Scope Rule is clearly articulated with a decision table, file structures are concrete with examples, and the style guide efficiently communicates deviations from Angular defaults with clear rationale. The content respects Claude's intelligence while providing project-specific conventions.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Uses tables for quick reference, minimal prose, no explanation of what Angular is or how components work. Every section delivers actionable information without padding. | 3 / 3 |
Actionability | Provides concrete file structures, exact naming conventions, executable ng commands, and a complete code example showing component organization. Copy-paste ready throughout. | 3 / 3 |
Workflow Clarity | For an architecture/structure skill, the workflow is clear: determine scope → place in appropriate folder → follow naming conventions. The decision table at the top provides an unambiguous decision tree for component placement. | 3 / 3 |
Progressive Disclosure | Well-organized sections with clear headers. Content is appropriately contained in a single file given its scope. Links to external Angular style guide for deeper reference without nesting complexity. | 3 / 3 |
Total | 12 / 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.
- 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.