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.
39
Quality
11%
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
22%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 essentially a placeholder that provides minimal information beyond the skill name. It lacks concrete actions, meaningful trigger terms, and explicit guidance on when Claude should select this skill. The repeated trigger term 'rabbitmq queue setup' suggests auto-generated content without human refinement.
Suggestions
Add specific concrete actions like 'Creates RabbitMQ queues, configures exchanges and bindings, sets up dead letter queues, defines routing keys and consumer configurations'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user mentions RabbitMQ, message queues, AMQP, queue consumers, message brokers, or pub/sub messaging patterns'
Add file type or technology markers that distinguish this from other queue technologies: 'Works with RabbitMQ/AMQP configurations, connection strings, and queue topology definitions'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only mentions 'rabbitmq queue setup' without describing any concrete actions. It doesn't explain what specific tasks are performed (e.g., creating queues, configuring exchanges, setting up bindings, defining routing keys). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and has no explicit 'Use when...' clause or equivalent trigger guidance. The triggers listed are just the skill name repeated. | 1 / 3 |
Trigger Term Quality | Contains 'rabbitmq queue setup' which is a relevant keyword, but lacks common variations users might say like 'message queue', 'AMQP', 'RabbitMQ configuration', 'queue consumer', 'producer setup', or 'message broker'. | 2 / 3 |
Distinctiveness Conflict Risk | While 'RabbitMQ' is specific technology, the vague 'queue setup' could overlap with other message queue skills (Kafka, Redis queues, SQS). The lack of specific capabilities makes it harder to distinguish from general backend or messaging skills. | 2 / 3 |
Total | 6 / 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 content is entirely template boilerplate with zero actual RabbitMQ queue setup guidance. It describes what the skill should do rather than providing any actionable instructions, code examples, or configuration patterns. The content fails to teach Claude anything about RabbitMQ and would be completely useless for the stated purpose.
Suggestions
Add executable code examples for RabbitMQ queue setup in at least one language (e.g., Python with pika or Node.js with amqplib)
Include specific queue configuration options (durability, TTL, dead-letter exchanges) with concrete parameter examples
Provide a clear workflow: 1) Connect to RabbitMQ, 2) Declare exchange, 3) Declare queue, 4) Bind queue, with validation steps
Remove all meta-description content ('This skill provides...', 'When to Use...') and replace with actual technical guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely boilerplate with no actual RabbitMQ-specific information. It explains what the skill does in abstract terms without providing any concrete guidance, wasting tokens on meta-description rather than actionable content. | 1 / 3 |
Actionability | No concrete code, commands, or specific instructions for RabbitMQ queue setup are provided. Phrases like 'provides step-by-step guidance' and 'generates production-ready code' describe capabilities without demonstrating them. | 1 / 3 |
Workflow Clarity | No actual workflow or steps for setting up RabbitMQ queues are present. The content only describes that it 'provides step-by-step guidance' without including any actual steps, validation checkpoints, or process flow. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of placeholder text with no structure pointing to detailed materials, no code examples, and no references to additional resources for RabbitMQ configuration or advanced patterns. | 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
994edc4
- 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.