iii-workflow-orchestration
Orchestrates durable multi-step workflow pipelines on the iii engine. Use when building order fulfillment, data pipelines, task orchestration, or any sequential process requiring retries, backoff, step tracking, scheduled cleanup, or dead letter queue (DLQ) handling.
64
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-workflow-orchestration/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 communicates what the skill does (orchestrate durable workflow pipelines on a specific engine) and when to use it (with an explicit 'Use when' clause covering multiple trigger scenarios). The description is concise yet comprehensive, uses third-person voice correctly, and includes distinctive technical terms that minimize conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: orchestrating durable multi-step workflow pipelines, with explicit mention of retries, backoff, step tracking, scheduled cleanup, and dead letter queue handling. | 3 / 3 |
Completeness | Clearly answers both 'what' (orchestrates durable multi-step workflow pipelines on the iii engine) and 'when' (explicit 'Use when' clause listing order fulfillment, data pipelines, task orchestration, or sequential processes requiring specific capabilities). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'order fulfillment', 'data pipelines', 'task orchestration', 'retries', 'backoff', 'step tracking', 'scheduled cleanup', 'dead letter queue', 'DLQ', 'workflow', 'sequential process'. Good coverage of both domain terms and technical terms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific platform ('iii engine'), the focus on durable workflow pipelines, and the enumeration of specific features like DLQ handling, backoff, and step tracking. 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 architectural overview of workflow orchestration on the iii engine with clear step sequencing and well-organized primitive references. Its main weaknesses are the lack of inline executable code (relying entirely on an external reference file that isn't bundled), missing explicit validation/error-recovery checkpoints in the workflow, and some redundancy between the Common Patterns and Primitives sections.
Suggestions
Include at least a minimal executable code snippet inline (e.g., a single registerFunction step that enqueues the next step) rather than deferring all code to an external reference file.
Add explicit validation checkpoints or error-handling feedback loops in the workflow description (e.g., what to check after each step, how to detect and recover from partial failures).
Consolidate the 'Common Patterns' and 'iii Primitives Used' sections to reduce redundancy — the primitives table already covers most of what Common Patterns restates.
Remove or condense the 'When to Use' and 'Boundaries' boilerplate sections, which add little value for Claude and consume tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary sections like 'When to Use' and 'Boundaries' that restate obvious meta-instructions. The 'Adapting This Pattern' and 'Common Patterns' sections have some overlap. The architecture diagram and primitives table are useful but the overall content could be tightened. | 2 / 3 |
Actionability | Provides API signatures and a primitives table with clear purpose descriptions, and references a full working example. However, the skill itself contains no executable code — only an architecture diagram in text and API call patterns described in prose. The actual implementation is deferred entirely to a reference file that wasn't provided in the bundle. | 2 / 3 |
Workflow Clarity | The architecture diagram clearly shows the step sequence (validate → payment → ship), and the 'Adapting This Pattern' section mentions DLQ handling and retry exhaustion. However, there are no explicit validation checkpoints or error recovery feedback loops within the workflow steps themselves — just a mention that failed jobs go to DLQ. | 2 / 3 |
Progressive Disclosure | References to external files (workflow-orchestration.js, iii-config.yaml, dead-letter-queues HOWTO) are well-signaled and one level deep. However, no bundle files were provided, so the referenced paths cannot be verified. The inline content includes both a primitives table and a 'Common Patterns' section that partially duplicate each other, suggesting some content could be better organized. | 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
a7ebbbb
- 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.