Compose HostDirectives and Pure Pipes in Angular. Use when creating attribute directives with HostDirectives or writing pure pipes in Angular. (triggers: **/*.directive.ts, **/*.pipe.ts, hostDirectives, PipeTransform, pure)
84
80%
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
89%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 well-structured skill description that clearly identifies its niche (Angular HostDirectives and pure pipes), includes explicit 'Use when' guidance, and provides relevant trigger terms including file patterns. The main weakness is that the 'what' portion could be more specific about the concrete actions performed beyond just 'compose'.
Suggestions
Expand the capability description with more concrete actions, e.g., 'Compose HostDirectives for attribute directives, implement pure pipes with PipeTransform, configure directive composition and input/output aliasing in Angular.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Angular) and two specific actions (composing HostDirectives and pure pipes), but doesn't elaborate on what composing entails or list multiple concrete sub-actions like 'create attribute directives, transform data with pipes, compose directive behaviors'. | 2 / 3 |
Completeness | Clearly answers both 'what' (compose HostDirectives and Pure Pipes in Angular) and 'when' (explicit 'Use when...' clause with trigger terms and file patterns), meeting the criteria for a score of 3. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'HostDirectives', 'pure pipes', 'Angular', 'attribute directives', 'PipeTransform', plus file glob patterns (*.directive.ts, *.pipe.ts) that match real file triggers. These are terms Angular developers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Angular HostDirectives and pure pipes, which is a narrow niche unlikely to conflict with other skills. The file patterns and Angular-specific terminology (PipeTransform, hostDirectives) make it clearly distinguishable. | 3 / 3 |
Total | 11 / 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.
This skill provides solid directional guidance for Angular directives and pipes with good structure and appropriate anti-patterns. Its main weakness is the lack of executable code examples—a complete directive or pipe snippet would significantly improve actionability. Some phrasing is awkward with malformed bold markers that reduce readability.
Suggestions
Add a complete, executable code example for a HostDirective composition (e.g., a TooltipDirective composed into a component) and a pure pipe implementation with PipeTransform.
Fix malformed bold/emphasis markers like '** not set pure: false**' and '** not declare in NgModule**' — these appear to be intended as 'Do not' instructions but are syntactically broken.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but has some redundancy and awkward phrasing (e.g., '** not set pure: false**', '** not declare in NgModule**'). Some explanations like 'Angular only re-runs them when reference changes' are things Claude would already know, but overall it's reasonably tight. | 2 / 3 |
Actionability | Provides specific decorator syntax and property names but lacks executable code examples. The guidance is concrete in terms of what decorators/properties to use, but there are no copy-paste ready code snippets showing a complete 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 clearly communicate what to do and what to avoid. | 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 details. Content is well-organized with one-level-deep references. | 3 / 3 |
Total | 10 / 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.
19a1140
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.