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.
80
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 an explicit 'Use when' clause covering multiple scenarios). The description uses third person voice, includes specific technical terms alongside natural language 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, checking permissions, validating data, etc.). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'condition function', 'gating triggers', 'business rules', 'user permissions', 'validating data', 'filtering', 'rate-limiting events', 'conditionally skipping handlers', 'payload content'. Good coverage of variations and use cases. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific technical concepts 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 skill provides a reasonable overview of trigger conditions with useful code fragments and cross-references, but falls short of excellence in several areas. The content includes some redundancy and boilerplate sections that don't earn their tokens, and the actionable guidance relies heavily on reference files that aren't available in the bundle. Adding a complete inline example and trimming repetitive sections would significantly improve quality.
Suggestions
Include a minimal but complete inline code example (register condition + register handler + register trigger) that is copy-paste ready, rather than relying entirely on external reference files
Remove or consolidate the redundant 'When to Use' and 'Boundaries' sections which repeat information already conveyed in 'Pattern Boundaries' and 'Key Concepts'
Add error handling guidance: what happens when a condition function throws an exception, and how to debug conditions that unexpectedly return false
Trim the 'Key Concepts' bullet about 'returns a boolean (true or false)' — Claude knows what a boolean is
| 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 sequence of registrations. 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 to verify these references exist, and the 'Pattern Boundaries' section references other skills without linking to them. 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
d51a06d
- 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.