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

70%

Does it follow best practices?

Impact

—

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 with a clear 'Use when' clause and good trigger term coverage across multiple event source types. Its main weakness is that the 'what' portion is somewhat thin—'builds custom trigger types' could be more specific about the concrete actions involved (e.g., configuring endpoints, registering handlers, testing triggers). The reference to 'iii' is unexplained, which could cause minor confusion.

Suggestions

Expand the capability description with more specific actions, e.g., 'Builds and configures custom trigger types, registers event handlers, and tests trigger pipelines 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 are terms a developer would naturally use when needing this functionality.	3 / 3
Distinctiveness Conflict Risk	The description carves out a clear niche: custom triggers for non-native event sources in a specific system ('iii'). The combination of custom triggers, webhooks, CDC, IoT, and file watchers creates a distinct profile 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 well-structured overview of custom trigger types with clear API surface documentation and good architectural framing. However, it lacks inline executable code examples (deferring everything to unverifiable reference files), includes some redundant sections, and misses validation/error-handling guidance that would be important for integrating external event sources.

Suggestions

Add at least one minimal inline code example showing a complete custom trigger registration (e.g., a simple interval-based trigger) so the skill is actionable without needing to reference external files.

Add validation/verification steps — e.g., how to confirm a trigger is registered correctly, how to handle errors when the external event source is unavailable, and how to test the trigger fires as expected.

Consolidate the redundant 'When to Use' and 'Boundaries' sections with 'Pattern Boundaries' to reduce token waste.

Remove the primitives table since it duplicates the Key Concepts bullet list, or merge them into a single section.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient but includes some redundancy — the 'When to Use' and 'Boundaries' sections at the bottom repeat information already conveyed in 'Pattern Boundaries', and phrases like 'Use the concepts below when they fit the task' and 'Use the adaptations below when they apply' are unnecessary filler. The primitives table partially duplicates the Key Concepts section.	2 / 3
Actionability	The skill describes the API surface and patterns clearly but provides no inline executable code — it relies entirely on external reference files for working examples. The 'Common Patterns' and 'Adapting This Pattern' sections describe what to do but don't show concrete, copy-paste-ready code snippets. The API calls are named but not demonstrated in context.	2 / 3
Workflow Clarity	The architecture diagram provides a clear high-level flow, and the common patterns section lists steps in a logical order. However, there are no explicit validation checkpoints, no error handling guidance, and no feedback loop for verifying the trigger is working correctly — important for integrations with external event sources that can fail silently.	2 / 3
Progressive Disclosure	The skill references external implementation files in three languages which is good structure, but since no bundle files were provided, we cannot verify these references exist. The skill itself is reasonably organized with clear sections, but the content split is questionable — too much is deferred to reference files while the SKILL.md lacks any inline code example, making it hard to use standalone.	2 / 3
	Total	8 / 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: d51a06d

Reviewed: 3 days 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.