Skip to content
Skills Library
DevOps & cloud · Planning

queue-design

/queue-design

Design a message queuing or streaming architecture for a workload. Use when asked "should we use Kafka or SQS", "design a queue architecture", or "design event streaming".

Repository
tonone ↗
Licence
MIT
Last repository change
14.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 14.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Design a message queuing or streaming architecture for a workload. Use when asked "should we use Kafka or SQS", "design a queue architecture", or "design event streaming".

Triggers from the description

should we use Kafka or SQSdesign a queue architecturedesign event streaming
Original author description

Design a message queuing or streaming architecture for a workload. Use when asked "should we use Kafka or SQS", "design a queue architecture", or "design event streaming".

How it works

  1. Steps
  2. Key Rules
  3. Delivery
Original SKILL.md headings · 37 lines, 181 words
SKILL.md preview
---
name: queue-design
description: Design a message queuing or streaming architecture for a workload. Use when asked "should we use Kafka or SQS", "design a queue architecture", or "design event streaming".
allowed-tools: Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
version: 1.7.0
author: tonone-ai <hello@tonone.ai>
license: MIT
compatibility: Designed for Claude Code
tags: [infrastructure, messaging, design]
---

# Queue Design

You are Queue — Message Queue & Streaming Engineer on the Infrastructure Specialist Team.

## Steps

### Step 0: Confirm Context

Ask the user for any missing context needed to produce a useful output. If the request is clear, skip questions and proceed.

### Step 1: Gather Context

Gather the use case (task queue/streaming/event log), throughput requirements, ordering requirements, and cloud provider.

### Step 2: Produce Output

Output a queue design: technology selection with rationale, topic/queue structure, consumer group design, DLQ config, and retry strategy.

### Step 3: Summary

Output a brief summary:

- What was produced
- Key risks or tradeoffs
- Recommended next steps

## Key Rules

- Follow the output format defined in docs/output-kit.md
- Always quantify tradeoffs: cost, reliability, and operational complexity
- Flag when recommendation requires production validation or load testing

## Delivery

If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.

Versions

The database has no other skills named queue-design.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 18cfde29dfdd (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100sqs-queue-setup
    Configure sqs queue setup operations. Auto-activating skill for AWS Skills. Triggers on: sqs queue setup, sqs queue setup Part of the AWS Skills skill category. Use when working with sqs queue setup functionality. Trigger with phrases like "sqs queue setup", "sqs setup", "sqs".
  • 100apache-kafka-event-streaming-architecture
    Use this skill when architecting distributed event streaming topologies, topic partitioning, retention policies, and broker clustering.
  • 100messaging-streaming
    This skill should be used when the user designs a "message queue", reaches for "Kafka", "RabbitMQ", "SQS", "Kinesis", "pub/sub", or "event-driven" architecture, asks about "async processing", "background jobs", "stream processing", or wrestles with "exactly-once vs…
  • 100sqs
    Amazon SQS managed message queue service. Covers standard and FIFO queues, dead-letter queues, and integration patterns. Use for AWS-native serverless and microservices architectures. USE WHEN: user mentions "sqs", "aws queues", "fifo queue", "lambda trigger", "sns to sqs", asks…
  • 100architecture
    Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.
  • 100architecture
    Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.