iii-functions-and-triggers
Registers functions and triggers on the iii engine across TypeScript, Python, and Rust. Use when creating workers, registering function handlers, binding triggers, or invoking functions across languages.
83
78%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/iii-functions-and-triggers/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 well-crafted skill description that clearly identifies a specific domain (iii engine), lists concrete actions, and includes an explicit 'Use when' clause with natural trigger terms. The description is concise yet comprehensive, covering both the capabilities and the activation conditions effectively. The domain-specific terminology ('iii engine') provides strong distinctiveness.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'registers functions', 'triggers on the iii engine', and specifies languages (TypeScript, Python, Rust). The 'Use when' clause adds further specifics: creating workers, registering function handlers, binding triggers, invoking functions. | 3 / 3 |
Completeness | Clearly answers both 'what' (registers functions and triggers on the iii engine across TypeScript, Python, and Rust) and 'when' (explicit 'Use when' clause covering creating workers, registering function handlers, binding triggers, or invoking functions across languages). | 3 / 3 |
Trigger Term Quality | Includes natural keywords a developer would use: 'workers', 'function handlers', 'triggers', 'invoking functions', 'TypeScript', 'Python', 'Rust', and the domain-specific 'iii engine'. These are terms a user working in this domain would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | The 'iii engine' is a very specific domain identifier that creates a clear niche. Combined with the specific actions (registering function handlers, binding triggers) and multi-language scope, this is unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 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 is well-organized with good progressive disclosure and clear references to related skills and language-specific implementations. Its main weaknesses are the lack of fully executable inline code examples (relying on external reference files) and the absence of an explicit step-by-step workflow with validation checkpoints. Some sections contain redundant meta-instructions that could be trimmed.
Suggestions
Add at least one complete, executable inline example (e.g., a minimal TypeScript worker that registers a function and an HTTP trigger) rather than relying entirely on external reference files.
Add an explicit numbered workflow showing the sequence: connect worker → register functions → bind triggers → invoke, with notes on what to verify at each step (e.g., confirming worker connection before registering functions).
Remove or consolidate the 'When to Use' and 'Boundaries' sections — these repeat generic meta-instructions that don't add actionable value for Claude.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but has some redundancy — the 'When to Use' and 'Boundaries' sections at the end repeat obvious meta-instructions that Claude doesn't need. The 'Architecture' paragraph largely restates what the primitives table already shows. Some trimming would improve token efficiency. | 2 / 3 |
Actionability | Provides concrete API signatures and common patterns with inline code snippets, but lacks fully executable, copy-paste-ready code examples — instead deferring to external reference files. The inline examples are registration calls without surrounding boilerplate, making them incomplete for direct execution. | 2 / 3 |
Workflow Clarity | The implicit workflow (registerWorker → registerFunction → registerTrigger → trigger) is discernible from the primitives table and common patterns, but there's no explicit sequenced workflow with numbered steps or validation checkpoints. For a multi-step registration process, the lack of explicit ordering and error handling guidance is a gap. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear sections, a concise overview, a primitives table, and well-signaled one-level-deep references to language-specific implementation files and related skills (iii-http-endpoints, iii-queue-processing, etc.). Navigation is straightforward and content is appropriately split. | 3 / 3 |
Total | 9 / 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
8921efa
- 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.