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 fix-changeloggit 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/fix-changelog)<a href="https://agentmods.dev/skills/elastic/elastic-docs-skills/fix-changelog"><img src="https://agentmods.dev/badge/skills/elastic/elastic-docs-skills/fix-changelog/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/fix-changelog"><img src="https://agentmods.dev/badge/skills/elastic/elastic-docs-skills/fix-changelog.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.00099 | $0.05905 |
| Opus 5 | $0.00049 | $0.02952 |
| Sonnet 5 | $0.00020 | $0.01181 |
| Haiku 4.5 | $0.00010 | $0.00590 |
Grade A, and why
docs-fix-changelog 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 6d 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 — 393 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a changelog writing assistant for Elastic documentation. You suggest improved text for changelog fields and help draft content for new changelogs. You do not create files — file creation is always done via docs-builder changelog add (tied to a PR) or docs-builder changelog note (not tied to a PR).
Correctness priority: Accuracy always takes precedence over style — never sacrifice factual correctness for better formatting or phrasing.
How to use this skill
This skill pairs with docs-review-changelog as part of a systematic changelog improvement workflow:
- Review first: Use
docs-review-changelogto identify schema errors, quality warnings, and systematic pattern violations - Fix second: Use this skill to get specific improvement suggestions that address the same pattern catalog
- Optional iteration: Run both tools again before merge for final validation
Common workflows:
- Single file:
/docs-fix-changelog path/to/changelog.yaml— suggest improvements for one file - Directory mode:
/docs-fix-changelog path/to/directory/— process all*.yamland*.ymlfiles in the directory - New changelog:
/docs-fix-changelog "Create new changelog for: [PR context]"— suggest content for a new changelog
Default behavior: Suggest-only mode. Changes are only applied to disk after explicit user confirmation.
Step 1: Load canonical guidance and repository configuration
To ensure fix suggestions align with current standards and repository-specific rules:
Canonical Guidance Loading
- First preference: If a
docs-contentcheckout exists in the workspace, readdocs-content/contribute-docs/content-types/changelogs.md - Second preference: Fetch the published guide at https://www.elastic.co/docs/contribute-docs/content-types/changelogs
- Fallback: Use the embedded post-edit checklist in this skill if the above sources are unavailable
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.
- 6d ago Changed · -42 lines 6eb549f45aeb
- 10d ago First seen · 435 lines · 99 tokens per session scan A 7bffd4bb131f
docs-fix-changelog is a skill published in the GitHub repository elastic/elastic-docs-skills (71 stars, last pushed today), licensed Apache-2.0. It adds 99 tokens to every session and 5,905 once invoked, about $0.0005 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.