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.

Quality

73%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/iii-custom-triggers/SKILL.md

Quality

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 a well-defined 'Use when' clause containing natural trigger terms. The 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 helps establish distinctiveness.

Suggestions

Expand the capability description with more specific actions, e.g., 'Builds and configures custom trigger types, registers event handlers, and sets up listeners 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., configuring, registering, testing triggers).	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 types'. These cover a good range of variations a user might mention when needing this skill.	3 / 3
Distinctiveness Conflict Risk	The description carves out a clear niche around custom trigger types for non-native events in a specific system ('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

57%

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 well-organized overview of custom trigger creation with good progressive disclosure to reference implementations. Its main weaknesses are the lack of inline executable code (relying entirely on external files for working examples) and some redundancy across sections. Adding a minimal inline code snippet and validation/error-handling guidance would significantly improve it.

Suggestions

Add a minimal inline code example (e.g., a 10-15 line registerTriggerType call with registerTrigger/unregisterTrigger callbacks) so the skill is actionable without navigating to reference files.

Add error handling and validation guidance — what happens if registerTrigger fails, if the external source disconnects, or if iii.trigger returns an error? Include a retry or logging checkpoint.

Consolidate the 'When to Use' and 'Boundaries' sections into 'Pattern Boundaries' to reduce redundancy and save tokens.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient but has some redundancy — the 'When to Use' and 'Boundaries' sections at the bottom repeat information already conveyed in 'Pattern Boundaries'. The 'Common Patterns' section largely restates what's already in 'Key Concepts' and the primitives table. Some phrasing like 'Use the concepts below when they fit the task' and 'Use the adaptations below when they apply to the task' is filler.	2 / 3
Actionability	The skill provides API signatures and a clear architecture flow, but contains no inline executable code examples — it defers entirely to external reference files. The 'Common Patterns' section lists function calls but doesn't show them assembled into working code. A developer would need to navigate to the reference files to get copy-paste ready code.	2 / 3
Workflow Clarity	The architecture section provides a clear high-level flow, and 'Adapting This Pattern' gives a reasonable sequence (register → listen → unregister). However, there are no explicit validation checkpoints, no error handling guidance, and no feedback loops for when trigger registration fails or events are lost. For a pattern involving external connections and resource management, this is a gap.	2 / 3
Progressive Disclosure	The skill is well-structured as an overview with clear one-level-deep references to implementation files in JS, Python, and Rust. Sections are logically organized from concepts → architecture → primitives → references → patterns → adaptation → boundaries. Navigation is straightforward.	3 / 3
	Total	9 / 12 Passed

Validation

100%

Warnings & errors only

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: 1 day ago

Table of Contents

Discovery Implementation Validation

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.