iii-queue-processing
Enqueues jobs, configures retry policies, sets concurrency limits, and orders messages via named standard or FIFO queues. Use when building background job workers, task queues, message queues, async pipelines, or any pattern needing guaranteed delivery with exponential backoff and dead-letter handling.
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-queue-processing/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 an excellent skill description that clearly articulates specific capabilities (enqueuing, retry configuration, concurrency, message ordering), provides a comprehensive 'Use when' clause with multiple natural trigger terms, and occupies a distinct niche around job/message queue patterns. It uses proper third-person voice throughout and balances conciseness with thoroughness.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: enqueues jobs, configures retry policies, sets concurrency limits, orders messages via named standard or FIFO queues. These are precise, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (enqueues jobs, configures retry policies, sets concurrency limits, orders messages) and 'when' with an explicit 'Use when...' clause listing five distinct trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'background job workers', 'task queues', 'message queues', 'async pipelines', 'guaranteed delivery', 'exponential backoff', 'dead-letter handling', 'FIFO queues', 'retry policies', 'concurrency limits'. These span both high-level concepts and specific technical terms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche around job/message queuing with specific technical concepts like FIFO queues, dead-letter handling, and exponential backoff. Unlikely to conflict with other skills due to the specificity of the domain. | 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 reasonable overview of queue processing with clear conceptual framing, architecture visualization, and pattern boundaries. Its main weaknesses are the lack of inline executable code (relying entirely on external references that cannot be verified), missing explicit validation/error-recovery workflows, and some redundancy in the boilerplate sections. The content would benefit significantly from at least one complete inline code example and a concrete config snippet.
Suggestions
Add at least one complete, inline executable code example showing a minimal producer + consumer setup rather than relying entirely on external reference files.
Include an inline snippet of the iii-config.yaml queue_configs section showing the actual YAML structure with max_retries, concurrency, type, and backoff_ms fields.
Add explicit validation/verification steps — e.g., how to confirm a job was enqueued, how to inspect the dead letter queue, or how to verify queue config is correct.
Remove or consolidate the generic 'When to Use' and 'Boundaries' boilerplate sections, which add little value and consume tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some redundancy — the 'When to Use' and 'Boundaries' sections at the bottom repeat generic boilerplate that doesn't add value. The 'Key Concepts' and 'Common Patterns' sections overlap somewhat. The ASCII architecture diagram is a nice touch but the overall content could be tightened. | 2 / 3 |
Actionability | The skill provides API signatures and pattern descriptions but no inline executable code examples. It relies entirely on external reference files for working code. The 'Common Patterns' section lists function calls but without complete, copy-paste-ready snippets showing how they fit together. The iii-config.yaml structure is described but never shown inline. | 2 / 3 |
Workflow Clarity | The architecture diagram shows the flow from producer to consumer to DLQ, and the 'Adapting This Pattern' section mentions chaining queues and idempotency checks. However, there are no explicit validation checkpoints or feedback loops for error recovery — the retry/DLQ behavior is described conceptually but there's no step-by-step workflow with verification steps. | 2 / 3 |
Progressive Disclosure | References to external files (queue-processing.js, .py, .rs, iii-config.yaml) are clearly signaled and one level deep, which is good. However, no bundle files were provided, so we cannot verify these references exist. The SKILL.md itself contains a fair amount of content that could be better organized — the 'Common Patterns' section essentially duplicates what should be in the reference files, while the actual config format that would be most useful inline is deferred to an external file. | 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.