Compose HostDirectives and Pure Pipes in Angular. Use when creating attribute directives with HostDirectives or writing pure pipes in Angular.
58
68%
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-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 beyond 'compose' and 'write', and could include more natural trigger term variations that developers might use.
Suggestions
Add more specific concrete actions, e.g., 'Compose HostDirectives to chain reusable attribute behaviors, expose directive inputs/outputs, and create pure pipes for data transformation in Angular templates.'
Expand trigger terms to include variations like 'directive composition', 'Angular pipe', 'transform pipe', '@Pipe decorator', or 'hostDirectives property'.
| 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 API'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of Angular-specific concepts (HostDirectives and Pure Pipes) creates a clear niche that is unlikely to conflict with other skills. These are distinct Angular features that wouldn't overlap with general Angular component or service skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides reasonably focused guidance on Angular directive composition and pure pipes with clear anti-patterns and guidelines. Its main weaknesses are the lack of complete, executable code examples and some formatting issues that reduce clarity. The content is appropriately scoped but would benefit from concrete code blocks showing full directive/pipe implementations.
Suggestions
Add at least one complete, executable code example for a hostDirective composition and one for a pure pipe implementation, rather than relying on inline fragments.
Fix formatting issues like '** not set pure: false**' and '** not declare in NgModule**' — use proper markdown emphasis and clearer phrasing (e.g., 'Do not set pure: false unless...').
Provide the referenced 'references/composition.md' bundle file or remove the reference if it doesn't exist.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but has some awkward phrasing and redundancy. Phrases like '** not set pure: false**' and '** not declare in NgModule**' are oddly formatted and could be tighter. Some explanations (e.g., explaining what pure pipes cache) border on things Claude already knows, but overall it's reasonably lean. | 2 / 3 |
Actionability | Provides specific decorator syntax, property names, and patterns (e.g., hostDirectives config, host object syntax), but lacks complete executable code examples. The guidance is concrete enough to follow but no copy-paste-ready code blocks are provided — everything is inline fragments rather than full working examples. | 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 | References a 'references/composition.md' file for deeper content, which is good structure, but no bundle files were provided to verify it exists. The main content is reasonably organized into sections but could benefit from additional references for pipes and directive patterns rather than inlining everything. | 2 / 3 |
Total | 9 / 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 | |
556618c
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.