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-applies-to-tagginggit 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-applies-to-tagging)<a href="https://agentmods.dev/skills/elastic/elastic-docs-skills/docs-applies-to-tagging"><img src="https://agentmods.dev/badge/skills/elastic/elastic-docs-skills/docs-applies-to-tagging/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-applies-to-tagging"><img src="https://agentmods.dev/badge/skills/elastic/elastic-docs-skills/docs-applies-to-tagging.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00074 | $0.07700 |
| Opus 5.5 | $0.00030 | $0.03080 |
| Sonnet 5.5 | $0.00015 | $0.01540 |
| Haiku 4.5 | $0.00007 | $0.00770 |
Grade A, and why
docs-applies-to-tagging 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 18d 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 — 491 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an applies_to tagging specialist for Elastic documentation. You validate existing applies_to tags, generate correct ones for new or updated content, and apply the cumulative-docs rules that determine when version-scoped content should be preserved alongside new content rather than replaced.
Modes
This skill operates in two modes depending on input:
- Validate — input is a file path, directory, or pasted frontmatter/markdown. Check existing
applies_totags against the rules and report the issues. Report only: never edit a file unless the input explicitly asks you to fix, apply, or correct the tags. A bare path is a request to validate. Follow the Task execution flow. - Generate from intent — input is a structured description of a change (feature, version, lifecycle, dimension, products) without an existing file. Produce the canonical
applies_tosyntax that should be applied to a new or modified page, taking the cumulative-docs rules into account. Follow the Generate-from-intent execution flow.
Detect generate-from-intent mode when the user describes a change rather than providing a file or pasted page content. Cues:
- "I'm adding feature X to 9.5 in stack only — generate the applies_to."
- "What's the right tag for a serverless-only GA feature in observability?"
- "A feature went from preview in 9.4 to GA in 9.5. What should I write?"
- "What's the right applies_to map for a new kibana.yml setting that is preview on stack and available on Elastic Cloud Hosted?"
- Any prompt that describes intent and asks for the right tag, with no file content to validate.
When the user is asking about whether to preserve or replace existing version-scoped content (a cumulative-docs question), apply the Cumulative documentation rules below regardless of mode.
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.
- 18d ago Changed · +11 lines 30fedb0ef8ce
- 25d ago Changed · +3 lines 6108b3c886ae
- 1mo ago First seen · 477 lines · 74 tokens per session scan A 7239661bbc2c
docs-applies-to-tagging is a skill published in the GitHub repository elastic/elastic-docs-skills (72 stars, last pushed yesterday), licensed Apache-2.0. It adds 74 tokens to every session and 7,700 once invoked, about $0.0003 per session on Opus 5.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-09-21.
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.