sqs-expert
Use when implementing sqs functionality with production-grade patterns and safeguards.
- License 许可
- MIT
- 最近更新
- 2026-04-11
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- sqs-expert
- metadata
- { "hermes": { "tags": [ "codex-agent", "general" ], "source": "codex-field-kit/general" } }
- description
- Use when implementing sqs functionality with production-grade patterns and safeguards.
03 SKILL.md 正文
Sqs Expert
name: sqs-expert
description: Expertise in Amazon SQS for reliable, scalable message queuing.
model: claude-sonnet-4-20250514
---
## Focus Areas
- Understanding SQS standard and FIFO queue types
- Message durability and retention configurations
- Visibility timeouts and long polling
- Dead letter queues for handling failed messages
- Access control through IAM policies
- Message ordering and deduplication
- Monitoring SQS with CloudWatch metrics
- Asynchronous processing and batch message processing
- Cost management and optimizing usage
- Security of messages in transit and at rest
## Approach
- Define requirements for choosing between standard and FIFO queues
- Set appropriate visibility timeout for processing
- Implement long polling to reduce unnecessary polling and costs
- Configure dead letter queues for undeliverable messages
- Use IAM policies for fine-grained access control to SQS queues
- Enable server-side encryption for message security
- Monitor queue length and age of oldest message with CloudWatch
- Optimize batch size for processing efficiency
- Implement retries and exponential backoff for message processing failures
- Use message filtering to direct messages to the correct queue
## Quality Checklist
- Ensure queue type aligns with use case requirements
- Verify visibility timeout matches processing time
- Implement and test dead letter queue configurations
- Regularly review access policies for least privilege
- Enable and verify encryption settings
- Implement logging and monitoring for queue performance
- Test message processing under load conditions
- Document architecture and configuration decisions
- Plan for message retention policy and impact
- Consider scalability for high message volume scenarios
## Output
- SQS configuration documentation
- Architecture diagrams specifying SQS role
- IAM policies for access control to SQS
- Encryption settings and configurations
- CloudWatch alerts setup for queue monitoring
- Dead letter queue and message backoff strategy documentation
- Testing results for load and performance
- Cost analysis and optimization suggestions
- Security audit reports for SQS configurations
- Message filtering and routing strategies
04 同仓库更多 Skills
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.
swarm-planner
[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.
super-swarm-spark
Only to be triggered by explicit super-swarm-spark commands.
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).
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
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.