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.
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-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 both what the skill does and when to use it. It uses third-person voice, lists concrete capabilities, and includes a rich set of natural trigger terms spanning multiple use cases. The specificity of the platform ('iii engine') and the detailed feature list make it highly distinctive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'durable multi-step workflow pipelines', 'retries', 'backoff', 'step tracking', 'scheduled cleanup', 'dead letter queue (DLQ) handling'. These are concrete, well-defined capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Orchestrates durable multi-step workflow pipelines on the iii engine') and when ('Use when building order fulfillment, data pipelines, task orchestration, or any sequential process requiring retries, backoff, step tracking, scheduled cleanup, or dead letter queue handling'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'order fulfillment', 'data pipelines', 'task orchestration', 'sequential process', 'retries', 'backoff', 'step tracking', 'scheduled cleanup', 'dead letter queue', 'DLQ'. Good coverage of both domain terms and technical variations. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific platform reference ('iii engine') and the combination of workflow orchestration with specific features like DLQ handling, backoff, and step tracking. Unlikely to conflict with generic coding or data processing 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-structured with good progressive disclosure and a clear architectural overview of the workflow orchestration pattern. Its main weaknesses are the lack of inline executable code examples (relying entirely on an external reference file) and missing explicit validation/error-recovery steps in the workflow description. Some sections contain redundant or boilerplate content that could be trimmed.
Suggestions
Add at least one inline, copy-paste-ready code snippet showing a minimal two-step workflow (e.g., validate → enqueue next step) so the skill is actionable without navigating to the reference file.
Add explicit validation/error-handling guidance in the workflow sequence — e.g., what to check after each enqueue, how to verify step completion, and how to handle partial pipeline failures beyond DLQ.
Consolidate the 'When to Use', 'Boundaries', and 'Pattern Boundaries' sections into a single section to reduce redundancy and save tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but has some redundancy — the 'When to Use' and 'Boundaries' sections repeat generic boilerplate, and the 'Common Patterns' section largely restates what's already shown in the Architecture and Primitives table. The 'Adapting This Pattern' preamble sentence is unnecessary filler. | 2 / 3 |
Actionability | Provides concrete API signatures and a primitives table, but the actual executable code lives entirely in a referenced file. The skill body itself contains no copy-paste-ready code examples — only API call signatures in bullet points and a text-based architecture diagram. A developer would need to navigate to the reference file to do anything. | 2 / 3 |
Workflow Clarity | The architecture diagram shows a clear 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 described in the workflow itself — it's unclear what happens on step failure beyond 'retries exhaust and move to DLQ'. | 2 / 3 |
Progressive Disclosure | Excellent structure with a concise overview, primitives table, and well-signaled one-level-deep references to the full implementation file, config file, and external DLQ documentation. Content is appropriately split between the skill overview and reference materials. | 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.