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.
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-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 strong skill description that clearly identifies a specific domain (iii engine), lists concrete actions (registering functions, binding triggers, creating workers), and provides explicit 'Use when' guidance with natural trigger terms. The multi-language scope is well-articulated and the description is concise without being vague.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'registers functions', 'triggers on the iii engine', and specifies three languages (TypeScript, Python, Rust). The actions are concrete and domain-specific. | 3 / 3 |
Completeness | Clearly answers both what ('Registers functions and triggers on the iii engine across TypeScript, Python, and Rust') and when ('Use when creating workers, registering function handlers, binding triggers, or invoking functions across languages') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'workers', 'function handlers', 'triggers', 'invoking functions', 'TypeScript', 'Python', 'Rust', and 'iii engine'. These cover the main terms a developer would use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | The 'iii engine' is a very specific platform/domain, and the combination of function registration, trigger binding, and multi-language support (TypeScript, Python, Rust) creates a clear niche 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 solid conceptual overview of the iii functions and triggers system with good API surface coverage and clear cross-references to related skills. However, it falls short on actionability by lacking complete executable examples in the body itself, and the workflow for registering and connecting components is implicit rather than explicitly sequenced with validation steps. The content has some redundancy across sections that could be tightened.
Suggestions
Add at least one complete, executable end-to-end example (e.g., a minimal TypeScript worker that registers a function, binds an HTTP trigger, and invokes another function) directly in the skill body rather than deferring all code to reference files.
Add an explicit numbered workflow sequence (e.g., 1. Connect worker → 2. Register functions → 3. Bind triggers → 4. Verify registration) with validation checkpoints such as checking connection status or confirming trigger binding.
Consolidate the 'When to Use', 'Boundaries', and 'Pattern Boundaries' sections into a single section to reduce redundancy and save tokens.
Remove or condense the 'Architecture' paragraph since it largely restates information already conveyed by the primitives table.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some redundancy — the 'Architecture' section restates what the primitives table already shows, the 'When to Use' and 'Boundaries' sections overlap with 'Pattern Boundaries', and some explanatory text (e.g., 'Comparable to: Serverless function runtimes') adds little value for Claude. | 2 / 3 |
Actionability | The skill provides concrete API signatures and common patterns with inline code snippets, but lacks fully executable, copy-paste-ready code examples. The actual executable code is deferred to reference files which are not provided in the bundle, so the skill body itself contains only fragments and pseudocode-level patterns rather than complete working examples. | 2 / 3 |
Workflow Clarity | The implicit workflow (registerWorker → registerFunction → registerTrigger → trigger) is discernible from the primitives table and common patterns, but there is no explicit numbered sequence, no validation checkpoints, and no error handling or feedback loops for the multi-step registration process. | 2 / 3 |
Progressive Disclosure | The skill references three language-specific reference files and cross-references other iii skills (iii-http-endpoints, iii-queue-processing, etc.), which is good structure. However, no bundle files were provided to verify these references exist, and the 'Pattern Boundaries' section listing related skills is helpful but the main content itself could benefit from better separation — the common patterns section is quite long and could be split. | 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.