iii-custom-triggers
Builds custom trigger types for events iii does not handle natively. Use when integrating webhooks, file watchers, IoT devices, database CDC, or any external event source.
60
70%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/iii-custom-triggers/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 solid description that clearly communicates both what the skill does and when to use it, with an explicit 'Use when' clause and good trigger term coverage. Its main weakness is that the 'what' portion could be more specific about the concrete actions performed beyond just 'builds'. The reference to 'iii' is somewhat opaque but serves to narrow the scope effectively.
Suggestions
Expand the specificity of actions beyond 'builds' — e.g., 'Builds and configures custom trigger types, including endpoint registration, payload parsing, and event routing, for events iii does not handle natively.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('custom trigger types') and lists several examples (webhooks, file watchers, IoT devices, database CDC), but doesn't describe concrete actions beyond 'builds'. It lacks detail on what specific operations are performed (e.g., configure endpoints, parse payloads, register listeners). | 2 / 3 |
Completeness | Clearly answers both 'what' (builds custom trigger types for events not handled natively) and 'when' (explicit 'Use when' clause listing webhooks, file watchers, IoT devices, database CDC, or any external event source). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'webhooks', 'file watchers', 'IoT devices', 'database CDC', 'external event source', 'custom trigger'. These are terms a user would naturally use when needing this capability. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche around custom trigger types and external event sources for a specific platform ('iii'). The combination of trigger types, webhooks, CDC, and IoT devices makes it highly distinctive and unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 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.
The skill provides a reasonable overview of custom trigger creation with clear API primitives and architecture, but suffers from redundancy across multiple overlapping sections (Key Concepts, Common Patterns, Authoring Guidance, Adapting This Pattern). The lack of inline executable code examples is a notable weakness — all working code is deferred to external reference files. The workflow could benefit from explicit step-by-step sequencing with validation checkpoints given the resource-management concerns involved.
Suggestions
Add at least one inline, minimal executable code example showing the full register → trigger → unregister lifecycle, rather than deferring all code to external files.
Consolidate 'Common Patterns', 'Authoring Guidance', and 'Adapting This Pattern' into a single section to eliminate redundancy and improve token efficiency.
Add an explicit numbered workflow with validation checkpoints (e.g., verify listener is active after registerTrigger, confirm cleanup after unregisterTrigger) to catch resource leaks.
Remove or significantly trim the generic 'When to Use' and 'Boundaries' boilerplate sections that don't add skill-specific value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but has some redundancy — the 'Common Patterns' section largely restates what's already in 'Key Concepts' and the primitives table. The 'Adapting This Pattern' section also overlaps significantly with 'Authoring Guidance'. The boilerplate 'When to Use' and 'Boundaries' sections at the end add little value. | 2 / 3 |
Actionability | The skill provides API signatures and a clear architecture diagram, but lacks inline executable code examples. It relies entirely on external reference files for working code. The guidance is specific but not copy-paste ready — a developer would need to consult the referenced files to actually implement anything. | 2 / 3 |
Workflow Clarity | The lifecycle flow (register type → register trigger → fire → unregister) is implied through the architecture diagram and authoring guidance, but there's no explicit step-by-step workflow with validation checkpoints. For a pattern involving long-lived resources and potential leaks, the absence of explicit verification steps (e.g., confirm listener is active, validate cleanup) is a gap. | 2 / 3 |
Progressive Disclosure | References to external files (custom-triggers.js/.py/.rs) are well-signaled and one level deep, which is good. However, no bundle files were provided, so the references cannot be verified. The main content itself has some sections that could be consolidated (overlapping guidance/patterns/adapting sections) rather than being cleanly separated. | 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.