AGENT SKILL

celery-expert

Use when implementing celery functionality with production-grade patterns and safeguards.

License 许可
MIT
最近更新
2026-04-11
Stars
★ 3
Forks
0

01 前言 Front Matter

name
celery-expert
metadata
{ "hermes": { "tags": [ "codex-agent", "general" ], "source": "codex-field-kit/general" } }
description
Use when implementing celery functionality with production-grade patterns and safeguards.

03 SKILL.md 正文

Celery Expert

Focus Areas

  • Configuring Celery for distributed systems
  • Task retry strategies and error handling
  • Optimizing worker performance and resources
  • Managing RabbitMQ or Redis brokers
  • Implementing robust Celery architectures
  • Monitoring task execution and failures
  • Efficient scheduling with Celery Beat
  • Task serialization and message passing
  • Security best practices for Celery setups
  • Troubleshooting and debugging Celery issues

Approach

  • Follow official Celery documentation strictly
  • Use asynchronous execution for non-blocking tasks
  • Leverage built-in task recovery and retry mechanisms
  • Optimize resource usage with concurrency settings
  • Configure task routing for load distribution
  • Ensure idempotent task implementations
  • Implement logging for task lifecycle events
  • Secure broker communication with SSL/TLS
  • Schedule regular worker health checks
  • Keep worker nodes updated with latest patches

Quality Checklist

  • Celery configuration matches project requirements
  • Task idempotency verified and tested
  • Retries configured with exponential backoff
  • Monitoring tools in place for task oversight
  • Scheduled tasks execute at correct intervals
  • Worker nodes have optimal concurrency settings
  • Task queue length regularly reviewed
  • Broker performance meets expected throughput
  • System security protocols adhered to
  • Comprehensive task testing and validation

Output

  • Distributed Celery setup documentation
  • Task implementation with detailed comments
  • Retry, error handling, and logging strategies
  • Performance benchmarks of task execution
  • Monitoring dashboards for task metrics
  • Regular reports on task and worker status
  • Secure broker configuration details
  • Schedule for periodic system audits
  • Idempotency test results and validation
  • Detailed troubleshooting resources and guides

04 同仓库更多 Skills

0xharryriddle
0xharryriddle/codex-field-kit

vercel-react-best-practices

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

前端开发
★ 3
0xharryriddle
0xharryriddle/codex-field-kit

swarm-planner

[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.

★ 3
0xharryriddle
0xharryriddle/codex-field-kit

super-swarm-spark

Only to be triggered by explicit super-swarm-spark commands.

★ 3
0xharryriddle
0xharryriddle/codex-field-kit

role-creator

Create and install Codex custom agent roles in ~/.codex/config.toml, generate role config files, enforce supported keys, and guide users through required role inputs (model, reasoning effort, developer_instructions).

★ 3
0xharryriddle
0xharryriddle/codex-field-kit

read-github

Read and search GitHub repository documentation via gitmcp.io MCP service. **WHEN TO USE:** - User provides a GitHub URL - User mentions a specific repo in owner/repo format - User asks "what does this repo do?", "read the docs for X repo", or similar - User wants to search code or docs within a repo

Skill与智能体开发
★ 3
0xharryriddle
0xharryriddle/codex-field-kit

planner

Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: "make a plan", "create a plan", "plan this out", "plan the implementation", "help me plan", "design a plan", "draft a plan", "write a plan", "outline the steps", "break this down into tasks", "what's the plan for", or any similar planning request. Also triggers on explicit "/planner" or "/plan" commands.

★ 3