Backend Message Queue
Use when the user asks about Kafka topics and partitions, RabbitMQ exchanges, SQS, consumer groups, consumer lag, dead letter queues, retention or message size limits. Produces broker topology and producer/consumer configuration. Not for event design between services (use backend-event-driven) or stream processing (use data-streaming).
Install
npx skills add j4flmao/agent-skills --skill backend-message-queuegit clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/backend/universal/message-queue ~/.claude/skills/backend-message-queuePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Backend Message Queue ## Purpose Design consistent, production-grade message-driven systems. Every message flow must follow the same conventions for broker selection, topic/queue topology, message schema, delivery guarantees, consumer idempotency, retry, and dead-letter handling. ## Agent Protocol ### Trigger Exact user phrases: "message queue", "Kafka", "RabbitMQ", "SQS", "pub-sub", "event bus", "consumer group", "topic", "queue", "at-least-once", "exactly-once", "idempotent consumer", "event sourcing", "dead letter queue", "DLQ", "message broker", "producer", "consumer", "event-driven", "async processing", "design a message flow". ### Input Context Before activating, verify: - The business event or asynchronous task is known. - The delivery guarantee requirement (at-most-once / at-least-once / exactly-once) is known. If not, ask: "What delivery guarantee do you need?" - The throughput requirement is known. - The broker preference (Kafka / RabbitMQ / SQS) is known. If not, ask: "Which broker? Kafka (high throughput, replay), RabbitMQ (routing, flexibility), or SQS (managed, simple)?" ### Output Artifact No file output unless the user requests it. Produces messaging topology specs as text. ### Response Format For each topic/queue:
Details
- Skill name
backend-message-queue- Repository
- j4flmao/agent-skills
- Path
skills/backend/universal/message-queue/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Backend Message Queue skill do?
Use when the user asks about Kafka topics and partitions, RabbitMQ exchanges, SQS, consumer groups, consumer lag, dead letter queues, retention or message size limits. Produces broker topology and producer/consumer configuration. Not for event design between services (use backend-event-driven) or stream processing (use data-streaming).
How do I install the Backend Message Queue skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill backend-message-queue. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Backend Message Queue popular?
It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.
Related skills
Agent Observability
45j4flmao/agent-skills
Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).
AI Agent Architectures
45j4flmao/agent-skills
Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).
AI Agent Core Loop
45j4flmao/agent-skills
Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).
Backend Multi Tenancy
45j4flmao/agent-skills
Use when the user asks about multi-tenancy, SaaS where each customer must only see their own data, tenant isolation, row-level security, schema or database per tenant, tenant context or tenant provisioning. Produces an isolation model with enforcement code. Not for Supabase RLS specifics (use supabase).
Backend Internationalization
45j4flmao/agent-skills
Use when the user asks about backend i18n, translating API messages, locale negotiation (Accept-Language), ICU MessageFormat, pluralization, BCP 47 tags or locale-aware dates and currency. Produces a server-side localization setup. Not for UI string handling (use frontend-internationalization).
Backend Plugin Architecture
45j4flmao/agent-skills
Use when the user asks about a plugin system, extension points, SPI, plugin loader, hot-plug or dynamic loading, plugin sandboxing or plugin manifests. Produces a plugin host design with lifecycle and isolation. Not for micro-frontends (use microfrontend).
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.