davidgeorgehope/elasticsearch-skill
Developer toolsЭта страница переведена автоматически. Технические детали смотрите в оригинале. Открыть оригинал
Claude Code skill for interacting with Elasticsearch REST API — Query DSL, aggregations, cluster ops, ILM, ES|QL, and more
Обзор
A markdown-based skill that teaches Claude Code how to interact with Elasticsearch clusters via REST API. No SDK, no client library, no MCP server — just curl and knowledge. Claude Code loads skills from local directories, not from GitHub URLs. Clone this repo, then copy the files to one of the supported skill locations. From within your project's root directory: Then commit the .claude/skills/elasticsearch/ directory to your repo so your team gets it too. Restart Claude Code, then check the skill is loaded: You should see elasticsearch in the list. Adding a GitHub URL to the skills array in ~/.claude/settings.json does work. Skills must be local files — there is no remote fetching. Set your cluster credentials as environment variables before starting Claude Code:
README
Показан фрагмент оригинального README. Открыть оригинал.
Elasticsearch Skill for Claude Code
A markdown-based skill that teaches Claude Code how to interact with Elasticsearch clusters via REST API. No SDK, no client library, no MCP server — just curl and knowledge.
What’s in it
| File | What it covers |
|---|---|
SKILL.md |
Auth, search, CRUD, bulk ops, index management, cluster health, ILM, ES|QL, ingest pipelines |
references/query-dsl.md |
Full Query DSL — bool, match, term, range, nested, geo, wildcards, runtime fields, search_after |
references/aggregations.md |
Metric, bucket, and pipeline aggregations — plus SRE patterns (error rates, top-N leaderboards) |
Installation
Claude Code loads skills from local directories, not from GitHub URLs. Clone this repo, then copy the files to one of the supported skill locations.
Option A: Personal skill (available in all projects)
git clone https://github.com/davidgeorgehope/elasticsearch-skill.git
mkdir -p ~/.claude/skills/elasticsearch
cp elasticsearch-skill/SKILL.md ~/.claude/skills/elasticsearch/
cp -r elasticsearch-skill/references ~/.claude/skills/elasticsearch/
Option B: Project skill (available in one repo only)
From within your project’s root directory:
git clone https://github.com/davidgeorgehope/elasticsearch-skill.git /tmp/elasticsearch-skill
mkdir -p .claude/skills/elasticsearch
cp /tmp/elasticsearch-skill/SKILL.md .claude/skills/elasticsearch/
cp -r /tmp/elasticsearch-skill/references .claude/skills/elasticsearch/
Then commit the .claude/skills/elasticsearch/ directory to your repo so your team gets it too.
Verify
Restart Claude Code, then check the skill is loaded:
/skills
You should see elasticsearch in the list.
Note: Adding a GitHub URL to the
skillsarray in~/.claude/settings.jsondoes not work. Skills must be local files — there is no remote fetching.
Configuration
Set your cluster credentials as environment variables before starting Claude Code:
export ES_URL="https://your-cluster.es.cloud.elastic.co:443"
export ES_API_KEY="your-base64-api-key"
Optionally, for Kibana API access:
export KIBANA_URL="https://your-cluster.kb.cloud.elastic.co:443"
No server to run, no dependencies to install, no Docker container to spin up.
Why a Skill and Not MCP?
This is a deliberate choice, not a limitation.
The token tax
MCP servers expose tools via JSON schemas that get injected into the LLM’s context window on every request. Anthropic’s own testing found that a modest five-server setup with 58 tools consumed ~55,000 tokens before the conversation even started. That’s your context window being eaten alive by tool definitions you might not even use.
A skill loads its main instructions only when triggered, and deeper reference files only when the LLM actually needs them. Progressive disclosure by design — not by workaround.
The full circle
Рекомендуемые инструменты
Попробуйте другой запрос или уберите фильтр.
Установка
npx skillfish add davidgeorgehope/elasticsearch-skill