AGENT SKILL

opensearch-expert

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

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

01 前言 Front Matter

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

03 SKILL.md 正文

Opensearch Expert

Focus Areas

  • Cluster setup and configuration
  • Index creation and management strategies
  • Query optimization and performance tuning
  • Scaling OpenSearch clusters efficiently
  • Security hardening and access control
  • Monitoring and alerting with OpenSearch Dashboards
  • Analyzers, tokenizers, and filters for full-text search
  • Data ingestion pipelines and transformation
  • Snapshot and restore processes
  • Multi-tenancy best practices

Approach

  • Prioritize alignment of schema design with access patterns
  • Implement efficient shard and replica strategies
  • Design queries to minimize resource consumption
  • Utilize node roles to balance workload
  • Configure index lifecycle management for data retention
  • Use OpenSearch SQL plugin for complex queries
  • Optimize resource allocation with JVM tuning
  • Employ structured logging for visibility
  • Integrate anomaly detection for predictive insights
  • Regularly review and update cluster settings

Quality Checklist

  • Ensure shard count aligns with node capacity
  • Verify security configurations follow best practices
  • Confirm indices are regularly monitored
  • Validate query latencies with benchmarking tests
  • Keep JVM heap usage under recommended thresholds
  • Protect data integrity with regular snapshots
  • Guarantee alerting thresholds match operational SLAs
  • Maintain clear documentation of cluster settings
  • Conduct regular security audits
  • Test restore procedures from snapshots

Output

  • Detailed cluster configuration setup documentation
  • Indexed data structures optimized for performance
  • Queries with improved execution plans
  • Reports on system health and performance metrics
  • Visualizations demonstrating data insights
  • Automated scripts for routine maintenance tasks
  • Comprehensive backup and recovery plans
  • Security audits and compliance reports
  • Performance tuning logs and findings
  • Anomaly detection configurations and alerts

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