iii-trigger-conditions
Registers a boolean condition function and attaches it to triggers via condition_function_id so handlers only fire when the condition passes. Use when gating triggers on business rules, checking user permissions, validating data before processing, filtering high-value orders, rate-limiting events, or conditionally skipping handlers based on payload content.
83
78%
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/iii-trigger-conditions/SKILL.mdQuality
Discovery
100%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 strong skill description that clearly articulates what the skill does (registers boolean condition functions and attaches them to triggers) and when to use it (six specific scenarios). The description uses third person voice, includes domain-specific trigger terms, and occupies a distinct niche that minimizes conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists multiple concrete actions: 'registers a boolean condition function', 'attaches it to triggers via condition_function_id', and 'handlers only fire when the condition passes'. These are specific, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (registers a boolean condition function and attaches it to triggers via condition_function_id) and 'when' (explicit 'Use when' clause listing six distinct trigger scenarios like gating triggers on business rules, checking permissions, etc.). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'condition function', 'triggers', 'business rules', 'user permissions', 'validating data', 'filtering', 'rate-limiting', 'gating triggers', 'conditionally skipping handlers', 'payload content'. Good coverage of variations and use cases. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche around condition functions attached to triggers via condition_function_id. The technical specificity of 'condition_function_id', 'boolean condition function', and 'gating triggers' makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a reasonably well-structured skill that clearly explains the trigger conditions pattern and provides good progressive disclosure with references to full implementations in multiple languages. Its main weaknesses are that the inline code examples are fragments rather than complete executable blocks, and there's some redundancy in the boilerplate sections and concept restatement. Adding a complete inline example and tightening the repeated guidance would improve it significantly.
Suggestions
Include at least one complete, copy-paste-ready inline example (all three registration calls together) rather than relying entirely on external reference files for the full implementation.
Remove or consolidate the redundant 'When to Use' and 'Boundaries' boilerplate sections — the 'Pattern Boundaries' section already covers this more effectively.
Add a brief numbered workflow sequence (1. Register condition function, 2. Register handler, 3. Register trigger with condition_function_id) to make the implementation steps explicit.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some redundancy — the 'When to Use' and 'Boundaries' sections at the bottom repeat generic boilerplate, and the 'Architecture' section restates what's already clear from 'Key Concepts'. The 'Common Patterns' section's inline comments ('condition returns true — handler executes') also restate known behavior. | 2 / 3 |
Actionability | The 'Common Patterns' section provides concrete code snippets showing registerFunction and registerTrigger calls, which is helpful. However, the actual implementation is deferred to external reference files rather than being inline and copy-paste ready, and the snippets in Common Patterns are fragments rather than a complete executable example. | 2 / 3 |
Workflow Clarity | The architecture section describes the flow (trigger fires → condition checked → handler runs or skips), and the common patterns show the three registration steps. However, there's no explicit numbered sequence for implementation, no validation checkpoints, and no error handling guidance for when conditions fail unexpectedly or are misconfigured. | 2 / 3 |
Progressive Disclosure | The skill provides a clear overview with well-signaled one-level-deep references to implementation files in JS, Python, and Rust. The 'Pattern Boundaries' section effectively directs to related skills. Content is appropriately split between the overview here and detailed implementations in reference files. | 3 / 3 |
Total | 9 / 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.
- Repository
- iii-hq/iii
- Commit
8921efa
- 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.