Compose HostDirectives and Pure Pipes in Angular. Use when creating attribute directives with HostDirectives or writing pure pipes in Angular.
76
72%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/angular/angular-directives-pipes/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 well-structured with a clear 'Use when' clause and targets a specific Angular niche, making it distinctive and complete. However, it could benefit from more concrete action verbs describing what the skill actually does (e.g., 'chain directives, expose inputs/outputs, create data transformation pipes') and additional trigger term variations to improve discoverability.
Suggestions
Add more specific concrete actions, e.g., 'Compose HostDirectives to chain behavior on components, expose directive inputs/outputs, and create pure pipes for data transformation in Angular.'
Include additional trigger term variations such as 'directive composition', 'Angular pipe', 'transform pipe', '@Pipe decorator', or 'hostDirectives array' to improve matching.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Angular) and two specific concepts (HostDirectives, Pure Pipes), but doesn't list concrete actions beyond 'compose' and 'writing'. Lacks detail on what specific operations are performed (e.g., chaining directives, transforming data, exposing inputs/outputs). | 2 / 3 |
Completeness | Explicitly answers both 'what' (compose HostDirectives and Pure Pipes in Angular) and 'when' (Use when creating attribute directives with HostDirectives or writing pure pipes in Angular), with a clear 'Use when...' clause. | 3 / 3 |
Trigger Term Quality | Includes relevant Angular-specific terms like 'HostDirectives', 'pure pipes', and 'attribute directives', which are terms a developer would use. However, it misses common variations like 'directive composition', 'transform pipe', 'Angular directive', or 'hostDirectives array'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly specific to Angular's HostDirectives and Pure Pipes, which are distinct Angular features unlikely to overlap with other skills. The niche is narrow and well-defined. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides solid structural organization with clear anti-patterns and principles for Angular directives and pipes. Its main weakness is the lack of executable code examples — showing a complete HostDirective composition or a pure pipe implementation would significantly improve actionability. Some phrasing is awkward or redundant (e.g., '** not set pure: false**' reads like a formatting error).
Suggestions
Add a complete, executable code example for hostDirectives composition (e.g., a component composing a TooltipDirective with exposed inputs/outputs)
Add a complete pure pipe implementation example showing the @Pipe decorator and transform method together
Fix formatting artifacts like '** not set pure: false**' and '** not declare in NgModule**' which appear to be malformed bold markers that reduce readability
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but has some redundant phrasing (e.g., explaining that pure is the default twice, restating standalone requirements). Some sentences are awkwardly constructed with bold formatting that adds noise rather than clarity. | 2 / 3 |
Actionability | Provides specific decorator syntax, property names, and patterns (hostDirectives, @Pipe decorator options, host object), but lacks any executable code examples. The guidance is concrete in naming conventions but never shows a complete, copy-paste-ready directive or pipe implementation. | 2 / 3 |
Workflow Clarity | This is a simple, single-purpose skill covering directive composition and pure pipes — there's no multi-step destructive workflow requiring validation checkpoints. The principles, guidelines, and anti-patterns sections provide clear, unambiguous guidance for when and how to apply these patterns. | 3 / 3 |
Progressive Disclosure | The skill is concise with a clear overview structure (Principles, Guidelines, Anti-Patterns) and appropriately references a separate composition.md file for deeper detail. For a skill of this size, the organization is well-suited. | 3 / 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 | |
4c72e76
Table of Contents
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.