Task routing and queue management patterns for Celery including priority queues, topic exchanges, worker-specific routing, and advanced queue configurations. Use when configuring task routing, managing queues, setting up priority queues, implementing worker routing, configuring topic exchanges, or when user mentions task routing, queue management, Celery routing, worker assignments, or message broker routing.
View on GitHubFebruary 1, 2026
Select agents to install to:
npx add-skill https://github.com/vanman2024/ai-dev-marketplace/blob/main/plugins/celery/skills/routing-strategies/SKILL.md -a claude-code --skill routing-strategiesInstallation paths:
.claude/skills/routing-strategies/# Celery Task Routing Strategies Skill This skill provides comprehensive templates, scripts, and patterns for implementing advanced task routing and queue management in Celery applications, including priority queues, topic-based routing, and worker-specific queue assignments. ## Overview Effective task routing is crucial for: 1. **Performance Optimization** - Route compute-intensive tasks to dedicated workers 2. **Priority Management** - High-priority tasks bypass slower queues 3. **Resource Isolation** - Separate critical operations from background jobs 4. **Scalability** - Independent scaling of different task types This skill covers routing with RabbitMQ, Redis, and custom broker configurations. ## Available Scripts ### 1. Test Routing Configuration **Script**: `scripts/test-routing.sh <config-file>` **Purpose**: Validates routing configuration and tests queue connectivity **Checks**: - Broker connectivity (RabbitMQ/Redis) - Queue declarations - Exchange configurations - Routing key patterns - Worker queue bindings - Priority queue setup **Usage**: ```bash # Test routing configuration ./scripts/test-routing.sh ./celery_config.py # Test with custom broker URL BROKER_URL=amqp://user:password@localhost:5672// ./scripts/test-routing.sh ./celery_config.py # Verbose output VERBOSE=1 ./scripts/test-routing.sh ./celery_config.py ``` **Exit Codes**: - `0`: All routing tests passed - `1`: Configuration errors detected - `2`: Broker connection failed ### 2. Validate Queue Configuration **Script**: `scripts/validate-queues.sh <project-dir>` **Purpose**: Validates queue setup across application code **Checks**: - Task decorators use valid queues - No hardcoded queue names (use config) - All queues defined in routing configuration - Priority settings are valid (0-255) - Exchange types match routing patterns - Worker configurations reference valid queues **Usage**: ```bash # Validate current project ./scripts/validate-queues.sh . # Validate specific director