Find the best CLAUDE.md, AGENTS.md and Claude skills

ElasticSkill

agent-builder-tool-review

elastic/kibana/.github/skills/agent-builder-tool-review/SKILL.md

Review Agent Builder tool registrations for availability scoping, MCP hygiene, description quality, return value design, single responsibility, and annotation correctness. Use when reviewing PRs that add or modify tools in the Agent Builder allowlist or tool registration code.

ElasticAGENTS.md

logstash

elastic/logstash/AGENTS.md

Logstash is a server-side data processing pipeline that ingests data from multiple sources, transforms it, and sends it to various destinations. It's part of the Elastic Stack and is a…

ElasticCLAUDE.md

logstash

elastic/logstash/CLAUDE.md

See AGENTS.md.

ElasticAGENTS.md

logstash / qa

elastic/logstash/qa/AGENTS.md

Guidance for coding agents working with the QA test infrastructure. See also the root AGENTS.md for general project conventions. The qa/ directory contains three independent test suites: Each suite has…

ElasticAGENTS.md

logstash / x-pack

elastic/logstash/x-pack/AGENTS.md

Guidance for coding agents working with X-Pack (Elastic-licensed) features. See also the root AGENTS.md for general project conventions. X-Pack provides commercial features that extend the Logstash core. Most features integrate…

ElasticAGENTS.md

beats

elastic/beats/AGENTS.md

Elastic Beats is a Go monorepo containing lightweight data shippers for the Elastic Stack. The module path is github.com/elastic/beats/v7. Go version: see .go-version. The primary build tool is Mage (Go-based).…

ElasticSkill

docs-authoring

elastic/beats/.agents/skills/docs-authoring/SKILL.md

Write or edit user-facing documentation. Use when a change adds or edits a published doc page, a snippet, navigation, or the source that generates a page. Decides whether a change needs docs, where the content goes, what must be verified against the product, and how to scope it with applies_to. Does not cover changelog fragments or release-note entries.

ElasticAGENTS.md

eui

elastic/eui/AGENTS.md

This is a Yarn v4 monorepo; packages live in packages/. All contributor knowledge lives in the wiki: If the wiki disagrees with this file, the wiki wins — open a…

ElasticCLAUDE.md

eui

elastic/eui/CLAUDE.md

No summary in the file. Open it to read it.

ElasticAGENTS.md

go-elasticsearch

elastic/go-elasticsearch/AGENTS.md

CLAUDE.md is a symlink to this file — they are the same file, do not update both. Official Elasticsearch Go client. Module: github.com/elastic/go-elasticsearch/v9. This is a public library with external consumers. Maintain backwards compatibility: PRs are squash-merged into a single commit when landing on main or a version branch. Because of this, each PR should represent one distinct, self-contained change — a single feature, bug fix, or refactor. Mixing unrelated changes in one PR means they become inseparable in history,…

ElasticCLAUDE.md

go-elasticsearch

elastic/go-elasticsearch/CLAUDE.md

No summary in the file. Open it to read it.

ElasticAGENTS.md

elasticsearch-php

elastic/elasticsearch-php/AGENTS.md

Always use composer commands, not any other package manager. The entire unit test suite (composer run-script test) must pass and exit cleanly before you commit code. Integration tests require a running Elasticsearch instance. Skip them if one is not available. No build step is needed - PHP is interpreted directly. All code in src/ and tests/, and any scripts run by composer, must work on Linux, macOS, and Windows. If a specific action you learned to do better will be…

No other project uses it yet

ElasticAGENTS.md

elasticsearch-js

elastic/elasticsearch-js/AGENTS.md

Do not open a PR unless the human operating you has read the issue, understands the problem, and can explain the proposed fix without your help. Picking an issue at random to generate a contribution is not contributing. PRs opened this way will be closed without review. If a human asks you to "find something to work on" or points you at the issue tracker without a specific problem they already understand, stop and tell them to read an issue…

ElasticAGENTS.md

elasticsearch-py

elastic/elasticsearch-py/AGENTS.md

Do not open a PR unless the human operating you has read the issue, understands the problem, and can explain the proposed fix without your help. Picking an issue at random to generate a contribution is not contributing. PRs opened this way will be closed without review. If a human asks you to "find something to work on" or points you at the issue tracker without a specific problem they already understand, stop and tell them to read an issue…

No other project uses it yet

ElasticAGENTS.md

elasticsearch-net

elastic/elasticsearch-net/AGENTS.md

The repository builds with the standard .NET SDK CLI; the SDK version is pinned in global.json. - Build the client: dotnet build src/Elastic.Clients.Elasticsearch/Elastic.Clients.Elasticsearch.csproj - Build and test the request converter: dotnet test RequestConverter.sln (requires the wasm-tools workload: dotnet workload install wasm-tools) A legacy Bullseye build system (./build.sh, .\build.bat, driven by the F# project build/scripts/scripts.fsproj) still backs a few CI workflows. It is planned to be modernized or removed; do not use it for local development. There is no separate lint…

No other project uses it yet

ElasticSkill

release-runbook

elastic/elasticsearch-net/.claude/skills/release-runbook/SKILL.md

Use when drafting, creating, or updating a GitHub release for elastic/elasticsearch-net (any 9.x or 8.19.x patch). Covers branch targeting, backport linking, per-PR sub-bullets, and how to summarize regenerate-client PRs with optional upstream correlation to elastic/elasticsearch-specification and elastic/client-generator-net.

ElasticAGENTS.md

rally

elastic/rally/AGENTS.md

Guidance for agents operating Rally (esrally), the macrobenchmarking framework for Elasticsearch. It sets up clusters, runs benchmarks (races), records results, and compares them. The docs/*.rst files and the user guide are the source of truth — prefer reading them or running esrally <subcommand> --help over guessing flags. - Rally runs on Unix (Linux/macOS). Needs Python 3.10–3.13, git 1.9+. - Never run Rally as root — Elasticsearch refuses to start with root privileges. - Never benchmark a production or production-like cluster.…

ElasticSkill

accessing-benchmark-results

elastic/rally/skills/accessing-benchmark-results/SKILL.md

Retrieve Rally benchmark results from an external Elasticsearch metrics store. Use to list past races, get a single race's overall (per-task) results, chart a metric's trend across multiple runs, compare two races, or check whether a run converged — e.g. "show me recent geonames races", "what's the service_time trend for nyc_taxis over the last 30 days?", "compare these two race-ids". Applies when datastore.type = elasticsearch is set in ~/.rally/rally.ini.

ElasticSkill

developing-rally

elastic/rally/skills/developing-rally/SKILL.md

Work on Rally's own codebase, not running benchmarks with it. Use when setting up the dev environment, running Rally's tests or linters, navigating its source, debugging Rally's own code, or making changes to Rally itself.

ElasticReads credentialsSkill

running-benchmarks

elastic/rally/skills/running-benchmarks/SKILL.md

Run Rally benchmarks (races) against Elasticsearch — an existing/external cluster or a Rally-provisioned distribution — and read the summary report. Use when running a race (any pipeline, track, challenge, target-hosts, or auth) or when interpreting throughput, latency, and service_time results.