Elastic Docs Skills is a collection of Claude Code skills for creating and maintaining Elastic documentation. It is for developers and documentation contributors who use coding agents such as Claude Code, Cursor, or Codex. The catalogue entries are the project's reusable documentation workflows, agents, plugin, and instruction.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add elastic/elastic-docs-skills --skill docs-syntax-helpgit clone --depth 1 https://github.com/elastic/elastic-docs-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/elastic/elastic-docs-skills/docs-syntax-help)<a href="https://agentmods.dev/skills/elastic/elastic-docs-skills/docs-syntax-help"><img src="https://agentmods.dev/badge/skills/elastic/elastic-docs-skills/docs-syntax-help/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/elastic/elastic-docs-skills/docs-syntax-help"><img src="https://agentmods.dev/badge/skills/elastic/elastic-docs-skills/docs-syntax-help.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 12 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00045 | $0.03951 |
| Opus 5.5 | $0.00018 | $0.01580 |
| Sonnet 5.5 | $0.00009 | $0.00790 |
| Haiku 4.5 | $0.00005 | $0.00395 |
Grade A, and why
docs-syntax-help scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
wget elasticsearch-{{version}}-linux.tar.gz How it starts
The opening of the file, as written. The whole thing — 595 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an Elastic Docs syntax expert. Your job is to help users write correct MyST Markdown with Elastic-specific extensions, troubleshoot syntax errors, and fix malformed directives.
Directive syntax fundamentals
Directives use colon-fenced blocks with the directive name in curly braces:
:::{directive-name} [argument]
:option: value
Content here
:::
- Opening: Three or more colons, directive name in
{} - Argument: Optional, on the same line after the name
- Options: One per line, colon-prefixed (
:option: value) - Content: Markdown-processed body
- Closing: Same number of colons as opening
Nesting directives
Outer directives need MORE colons than inner ones. Add one colon per nesting level:
::::{tab-set}
:::{tab-item} First
Content
:::
:::{tab-item} Second
Content
:::
::::
Three levels deep:
::::::{stepper}
:::::{step} Title
::::{tab-set}
:::{tab-item} Option A
Content
:::
::::
:::::
::::::
Literal blocks inside directives
Code blocks use backtick fences (not colons) to prevent Markdown processing:
:::{note}
```yaml
key: value
```
:::
Admonitions
Four standard types plus custom:
:::{note}
Supplemental information. No serious repercussions if ignored.
:::
:::{tip}
Advice to help users work more efficiently.
:::
:::{important}
Ignoring this could impact performance or stability.
:::
:::{warning}
Users could permanently lose data or leak sensitive information.
:::
:::{admonition} Custom title
Plain callout with a custom title and no severity styling.
:::
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago Changed · +1 lines 152c3b8ca2c4
- 25d ago Changed · +2 lines b480e3da675d
- 1mo ago First seen · 592 lines · 45 tokens per session scan A 4443a6fa0a3d
docs-syntax-help is a skill published in the GitHub repository elastic/elastic-docs-skills (72 stars, last pushed yesterday), licensed Apache-2.0. It adds 45 tokens to every session and 3,951 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
codex-docs-drift-scout
Install the AutoHub docs-drift Codex automation from signed AutoVault skill resources and audit its render fidelity with autovault doctor.
writing-docs
A guide for writing useful documentation for libraries, tools, services, and technical projects.
pr-description
A guide for writing Pull Request descriptions, which explain proposed code changes before teammates review them.
writing-skills
How to write, split, and review docs/skills/ files in testsuite. Load when creating, editing, or deleting a skill.
bun-runtime-http
Covers Bun.serve, HTTP server configuration, routing, streaming responses, WebSockets, TLS/SSL, and middleware with Bun's native APIs.
bun-guides-test
Practical guides for testing TypeScript applications, mocking modules, mocking fetch, and running unit tests in Bun.