iii-trigger-actions
Selects how functions are invoked — synchronous calls that return results, fire-and-forget void dispatches, or durable enqueue through named queues with retries. Use when deciding between blocking RPC calls, background job dispatch, async workers, or reliable message delivery with acknowledgement.
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-trigger-actions/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 defines a specific architectural decision domain — choosing between function invocation patterns. It provides concrete actions, a well-formed 'Use when' clause with natural trigger terms, and occupies a distinct niche that minimizes conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete invocation patterns: synchronous calls that return results, fire-and-forget void dispatches, and durable enqueue through named queues with retries. These are distinct, well-defined actions. | 3 / 3 |
Completeness | Clearly answers both 'what' (selects function invocation style among sync, fire-and-forget, and durable enqueue) and 'when' (explicit 'Use when' clause covering blocking RPC, background jobs, async workers, and reliable message delivery). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'synchronous calls', 'RPC calls', 'fire-and-forget', 'background job dispatch', 'async workers', 'message delivery', 'acknowledgement', 'retries', 'named queues'. Good coverage of variations across the domain. | 3 / 3 |
Distinctiveness Conflict Risk | Targets a very specific niche — function invocation strategy selection — with distinct triggers like 'RPC calls', 'fire-and-forget', 'durable enqueue', and 'named queues with retries' that are unlikely to overlap 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.
The skill covers the three invocation modes (sync, void, enqueue) with reasonable clarity and provides useful code snippets and CLI examples. Its main weaknesses are redundancy across sections (Architecture restates Key Concepts, boilerplate When to Use/Boundaries sections), lack of complete executable examples in the body itself, and missing error handling/validation guidance for what are potentially critical operations (especially enqueue for payments).
Suggestions
Remove the 'Architecture' section as it restates Key Concepts, and consolidate the 'When to Use' and 'Boundaries' boilerplate sections to save tokens.
Include at least one complete executable example inline (e.g., a handler that combines sync validation with enqueue processing) rather than deferring all complete examples to missing reference files.
Add error handling guidance — what happens on timeout for sync calls, how to check enqueue receipt status, and what to do when void dispatch silently fails for a critical path.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content has some redundancy — the 'Architecture' section restates what's already clear from Key Concepts, the 'When to Use' and 'Boundaries' sections are boilerplate that Claude doesn't need, and the decision guide in Key Concepts is repeated in Adapting This Pattern. However, the core technical content is reasonably efficient. | 2 / 3 |
Actionability | The Common Patterns section provides concrete code snippets and CLI commands that are close to copy-paste ready, but they're inline fragments rather than complete executable examples. The actual reference implementations are deferred to external files that aren't provided in the bundle, reducing actionability. | 2 / 3 |
Workflow Clarity | The decision guide (need result → sync, must complete → enqueue, optional → void) is clear, and the 'Combine modes' adaptation hints at multi-step workflows. However, there are no explicit validation checkpoints, no error handling guidance for failed triggers or timeouts, and no feedback loops for retry exhaustion scenarios. | 2 / 3 |
Progressive Disclosure | References to external files (trigger-actions.js/py/rs) and related skills (iii-engine-config, iii-dead-letter-queues, etc.) are well-signaled and one level deep. However, no bundle files were provided, so the referenced implementations don't actually exist, and the Pattern Boundaries section references skills by name without linking to them. | 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.