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.
64
75%
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/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 condition functions for triggers) and when to use it (with six specific use cases). The technical specificity of terms like 'condition_function_id' and 'boolean condition function' make it highly distinctive, while the varied trigger scenarios in the 'Use when' clause provide excellent keyword coverage for matching user requests.
| 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 distinctive with specific technical terms like 'condition_function_id', 'boolean condition function', and 'gating triggers'. This is a clear niche around conditional trigger execution that is unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a moderately well-structured skill that clearly explains the trigger conditions pattern and provides useful code fragments in the Common Patterns section. Its main weaknesses are verbosity from boilerplate sections (When to Use, Boundaries) that don't add actionable value, and the lack of a complete inline example since the referenced implementation files aren't available in the bundle. The workflow description is adequate but lacks error handling and validation guidance.
Suggestions
Include a minimal but complete inline example (register condition + register handler + register trigger) that is copy-paste ready, rather than relying entirely on external reference files that may not be available.
Remove or consolidate the boilerplate 'When to Use' and 'Boundaries' sections — these repeat generic guidance that doesn't help Claude execute the pattern.
Add guidance on error handling: what happens if the condition function throws an exception, and how to debug conditions that unexpectedly return false.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content has some unnecessary sections like 'When to Use' and 'Boundaries' that are boilerplate and don't add value. The 'Architecture' section restates what's already clear from 'Key Concepts'. The 'Comparable to: Middleware guards, event filters' line is helpful but some explanations like 'returns a boolean (true or false)' are redundant for Claude. | 2 / 3 |
Actionability | The 'Common Patterns' section provides concrete code snippets showing condition registration, handler registration, and trigger binding, which is useful. However, these are inline fragments rather than a complete, copy-paste-ready example. The full working example is deferred to reference files that aren't provided in the bundle, making it impossible to verify executability. | 2 / 3 |
Workflow Clarity | The architecture section describes the flow (trigger fires → condition evaluated → handler runs or skips), and the common patterns section shows the three registration steps in order. However, there are no explicit validation checkpoints or error handling guidance — what happens if the condition function throws? No feedback loop for debugging failed conditions. | 2 / 3 |
Progressive Disclosure | The skill references three language-specific implementation files (JS, Python, Rust) and cross-references related skills by name, which is good structure. However, no bundle files were provided, so the references can't be verified. The 'Pattern Boundaries' section effectively serves as navigation to related skills. The inline content could be tighter with more deferred to references. | 2 / 3 |
Total | 8 / 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
a7ebbbb
- 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.