rabbitmq-queue-setup
Rabbitmq Queue Setup - Auto-activating skill for Backend Development. Triggers on: rabbitmq queue setup, rabbitmq queue setup Part of the Backend Development skill category.
34
3%
Does it follow best practices?
Impact
87%
1.06xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/06-backend-dev/rabbitmq-queue-setup/SKILL.mdQuality
Discovery
7%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 description is extremely minimal, essentially just a title and category label with no substantive content. It lacks concrete actions, natural trigger terms, and any 'Use when...' guidance, making it nearly useless for skill selection among multiple options.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates RabbitMQ queues, configures exchanges and bindings, sets up dead-letter queues, and defines consumer/producer patterns.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about RabbitMQ, message queues, AMQP, exchanges, bindings, pub/sub messaging, or message broker configuration.'
Remove the duplicate trigger term ('rabbitmq queue setup' is listed twice) and expand with varied natural language terms users might use such as 'message broker', 'queue consumer', 'AMQP setup'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the domain ('RabbitMQ Queue Setup') but lists no concrete actions like creating queues, configuring exchanges, setting up bindings, or defining consumers. It is essentially a title repeated with no elaboration. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the title and completely lacks a 'when should Claude use it' clause. There is no explicit trigger guidance or explanation of capabilities. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'rabbitmq queue setup' repeated twice. It misses natural variations users would say such as 'message queue', 'AMQP', 'consumer', 'producer', 'exchange', 'binding', 'pub/sub', or 'message broker'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'RabbitMQ' specifically does narrow the domain somewhat, making it unlikely to conflict with unrelated skills. However, the lack of detail about what aspects of RabbitMQ it covers could cause overlap with other messaging or backend skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty shell with no actual content about RabbitMQ queue setup. It consists entirely of auto-generated boilerplate that describes what the skill would do without providing any actionable guidance, code examples, configuration snippets, or workflow steps. It adds no value beyond what Claude already knows.
Suggestions
Add concrete, executable code examples for setting up RabbitMQ queues in at least one language (e.g., Python with pika or Node.js with amqplib), including connection, channel creation, queue declaration, and message publishing/consuming.
Include a clear multi-step workflow with validation checkpoints, such as: 1) Install dependencies, 2) Configure connection, 3) Declare queue with specific options, 4) Verify queue exists via management API or CLI, 5) Test with a publish/consume cycle.
Add RabbitMQ-specific configuration guidance covering durability, acknowledgments, prefetch count, dead-letter exchanges, and TTL—things that represent best practices and common pitfalls.
Remove all meta-description sections ('Purpose', 'When to Use', 'Capabilities', 'Example Triggers') and replace them with actual technical content that Claude doesn't already know.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content about RabbitMQ queue setup. Every section restates the same vague information. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no configuration examples, no specific RabbitMQ concepts. It only describes what it could do rather than actually instructing how to set up a RabbitMQ queue. | 1 / 3 |
Workflow Clarity | No workflow steps are provided at all. There is no sequence, no validation checkpoints, and no actual process for setting up a RabbitMQ queue. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-descriptions with no meaningful structure, no references to detailed materials, and no navigation to deeper content. The sections are all boilerplate with no real information. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3076d78
- 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.