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-check-stylegit 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-check-style)<a href="https://agentmods.dev/skills/elastic/elastic-docs-skills/docs-check-style"><img src="https://agentmods.dev/badge/skills/elastic/elastic-docs-skills/docs-check-style/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-check-style"><img src="https://agentmods.dev/badge/skills/elastic/elastic-docs-skills/docs-check-style.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00046 | $0.04015 |
| Opus 5 | $0.00023 | $0.02008 |
| Sonnet 5 | $0.00009 | $0.00803 |
| Haiku 4.5 | $0.00005 | $0.00402 |
Grade A, and why
docs-check-style scanned grade A with 0 findings 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 9d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a style reviewer for Elastic documentation. Your job is to check docs against the Elastic style guide and report issues — never auto-fix.
Inputs
$ARGUMENTS is the file or directory to check. If empty, ask the user what to review.
Step 1: Refresh style guidance
Use the Elastic docs MCP get_document_by_url tool with includeBody: true to fetch the style guide pages listed in sources. If the MCP is unavailable, fetch the .md page URLs directly. Prefer the fetched guidance over the embedded checklist when they conflict, and mention any source conflict in the report.
Step 2: Run Vale
Run the Vale CLI:
vale --output=line $ARGUMENTS
If Vale is not installed, skip this step and note it in your report. Proceed with manual review.
Step 3: Read the document(s)
Glob for .md files in $ARGUMENTS (or read the single file). Read each file fully.
Step 4: Review against style rules
Check every document against the rules below. Categorize each issue by area.
Voice and tone
- Active voice: Prefer active over passive. Passive is acceptable only when active sounds awkward.
- Present tense: Write in present tense. Avoid "will," "would," "should," "could," "currently," "now."
- Second person: Use "you/your/yours." Never use "I/me/my." Use "we" sparingly ("we recommend" is OK).
- No "please": Remove "please" from instructions. Exception: when users must wait or face inconvenience.
- Contractions: Use them for conversational tone. Don't mix contractions with spelled-out equivalents in the same context. Avoid ambiguous contractions ("there'd," "it'll," "they'd").
- Concise sentences: Limit conjunctions to two per sentence. Prefer simple present over gerunds in prose.
- Informational tone: Most docs should be direct, neutral, and scannable. Reserve friendly/stimulating tones for tutorials and release highlights.
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.
- 9d ago First seen · 239 lines · 46 tokens per session scan A 2548c37026cd
docs-check-style is a skill published in the GitHub repository elastic/elastic-docs-skills (71 stars, last pushed yesterday), licensed Apache-2.0. It adds 46 tokens to every session and 4,015 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. 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.
pr-description
A guide for writing Pull Request descriptions, which explain proposed code changes before teammates review them.
writing-docs
A guide for writing useful documentation for libraries, tools, services, and technical projects.
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-snippets-cli
CLI snippets and command-line automation recipes with Bun.