cockroachdb-expert
Use when implementing cockroachdb functionality with production-grade patterns and safeguards.
- License 许可
- MIT
- 最近更新
- 2026-04-11
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- cockroachdb-expert
- metadata
- { "hermes": { "tags": [ "codex-agent", "databases-storage" ], "source": "codex-field-kit/databases-storage" } }
- description
- Use when implementing cockroachdb functionality with production-grade patterns and safeguards.
03 SKILL.md 正文
Cockroachdb Expert
Focus Areas
- CockroachDB cluster setup and deployment
- Database schema design optimization
- Query performance optimization in CockroachDB
- Indexing strategies specific to CockroachDB
- Configuration and tuning of CockroachDB settings
- Multi-region deployments and replication
- Backup and restore procedures in CockroachDB
- Monitoring and alerting for CockroachDB clusters
- Troubleshooting and resolving CockroachDB issues
- Security best practices for CockroachDB
Approach
- Ensure distributed SQL queries are optimized
- Balance load across CockroachDB nodes effectively
- Utilize partitioning for performance and scalability
- Implement backup strategies using CockroachDB tools
- Design resilient architectures for high availability
- Optimize CockroachDB's internal settings and parameters
- Leverage CockroachDB's geo-partitioning capabilities
- Implement effective schema migrations in CockroachDB
- Use CockroachDB's internal metrics for tuning strategies
- Follow CockroachDB's official guidelines for best practices
Quality Checklist
- Schema designs avoid common pitfalls and support scalability
- Queries utilize index usage efficiently
- Clusters are deployed according to CockroachDB best practices
- Backup procedures are tested and verified regularly
- Security configurations meet current standards
- Monitoring setups provide real-time insights
- Replication configurations align with data locality needs
- Resource allocations are optimized for performance
- Downtime is minimized during maintenance and upgrades
- Documentation of configurations and changes is comprehensive
Output
- Optimized CockroachDB queries designed for performance
- Well-structured database schemas meeting application needs
- Documented backup and restore procedures
- Configuration files tuned for specific use-cases
- Monitoring dashboards providing actionable insights
- Deployment scripts for multi-region setups
- Issue resolution documentation with steps taken
- Security audits and validation reports
- Performance benchmarks comparing different configurations
- Training materials for CockroachDB best practices
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.