rabbitmq-expert
Expert RabbitMQ administrator and developer specializing in message broker architecture, exchange patterns, clustering, high availability, and production monitoring. Use when designing message queue systems, implementing pub/sub patterns, troubleshooting RabbitMQ clusters, or optimizing message throughput and reliability.
76
76%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/rabbitmq-expert/SKILL.mdQuality
Discovery
89%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 solid skill description with excellent trigger terms and completeness, including an explicit 'Use when...' clause with multiple specific scenarios. The main weakness is the use of role-based language ('Expert administrator and developer') rather than action-oriented verbs describing concrete capabilities. The description would be stronger if it listed specific actions rather than areas of expertise.
Suggestions
Replace role-based language ('Expert administrator and developer specializing in...') with action verbs describing concrete capabilities (e.g., 'Configures exchanges, sets up clustering, monitors queue health, troubleshoots connection issues').
Add specific file types or tools that might trigger selection (e.g., 'rabbitmq.conf', 'AMQP', 'Erlang cookie configuration').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (RabbitMQ) and lists several areas of expertise (exchange patterns, clustering, high availability, monitoring), but uses role-based language ('Expert administrator and developer') rather than concrete actions. Does not list specific actions like 'configure exchanges', 'set up mirrored queues', or 'diagnose connection issues'. | 2 / 3 |
Completeness | Clearly answers both what (RabbitMQ administration covering architecture, exchange patterns, clustering, HA, monitoring) and when with explicit 'Use when...' clause listing four specific trigger scenarios (designing message queue systems, implementing pub/sub, troubleshooting clusters, optimizing throughput). | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'message queue', 'pub/sub patterns', 'RabbitMQ clusters', 'message throughput', 'reliability'. These are terms users would naturally use when seeking help with message broker systems. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on RabbitMQ with distinct triggers. Unlikely to conflict with general coding skills or other message broker skills due to explicit RabbitMQ naming and specific terminology like 'exchange patterns' and 'clustering'. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides highly actionable, production-ready RabbitMQ guidance with excellent code examples and clear workflows. However, it suffers from severe verbosity with duplicated content (overview appears twice), excessive explanation of concepts Claude already knows, and a monolithic structure that should be split across multiple files for better progressive disclosure.
Suggestions
Remove the duplicated 'Overview' section (appears in both Section 1 and after Section 4) and consolidate expertise descriptions
Extract detailed patterns (Sections 4, 6, 7) into separate reference files (e.g., PATTERNS.md, SECURITY.md) and link from a concise SKILL.md overview
Remove explanatory text about what RabbitMQ concepts are (exchanges, queues, AMQP protocol) - Claude knows these; focus only on project-specific conventions and gotchas
Condense the 'Common Mistakes' section by removing the BAD examples and keeping only the DO patterns with brief context
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~1000+ lines with significant redundancy. The 'Overview' section appears twice with identical content. Explains concepts Claude already knows (what AMQP is, what exchanges do, basic Python patterns). Many sections could be condensed by 50-70%. | 1 / 3 |
Actionability | Excellent executable code examples throughout - complete Python implementations with pika, proper error handling, test fixtures, and configuration files. All code is copy-paste ready with clear context for when to use each pattern. | 3 / 3 |
Workflow Clarity | Clear TDD workflow with explicit steps (write failing test → implement → refactor → verify). Includes validation checkpoints, pre-implementation checklists with phases, and explicit feedback loops for error recovery with DLX patterns. | 3 / 3 |
Progressive Disclosure | Content is organized into numbered sections with clear headers, but everything is in one massive file. No references to external files for detailed content like API references or advanced patterns. The monolithic structure makes navigation difficult despite good internal organization. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (1556 lines); consider splitting into references/ and linking | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 12 / 16 Passed | |
- Repository
- martinholovsky/claude-skills-generator
- Commit
1086ef2
- 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.