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-stack-releasegit 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-stack-release)<a href="https://agentmods.dev/skills/elastic/elastic-docs-skills/docs-stack-release"><img src="https://agentmods.dev/badge/skills/elastic/elastic-docs-skills/docs-stack-release/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-stack-release"><img src="https://agentmods.dev/badge/skills/elastic/elastic-docs-skills/docs-stack-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium Excessive Agency · line 142 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00110 | $0.06905 |
| Opus 5.5 | $0.00044 | $0.02762 |
| Sonnet 5.5 | $0.00022 | $0.01381 |
| Haiku 4.5 | $0.00011 | $0.00690 |
Grade A, and why
docs-stack-release 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 1mo 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 — 386 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docs release issue ([Docs release] X.Y.Z in elastic/dev) is the source of truth -- not the eng [Release] issue. Create missing docs issues (§1.1) or collect dates from the user. Missing issue URLs: (issue TBD).
Playbooks: v9 -- v8. Templates: minor -- 9.x patch -- 8.x patch.
| Line | Repo | Config files | Deploy watch |
|---|---|---|---|
| 9.x+ | elastic/docs-builder |
config/assembler.yml, config/versions.yml |
docs-internal-workflows bump PRs + prod version-bump (§0.3) |
| 8.x / 7.x | elastic/docs |
shared/versions/stack/*.asciidoc, conf.yaml |
None -- do not use docs-internal-workflows |
Invariants
- IDs, dates, PR URLs, @mentions: from
gh, the docs issue, Slack, or the user. Never invent. Missing →(issue TBD)or[@handle]and ask. - Never mix 8.x and 9.x in one PR. 8.x/7.x:
elastic/docsonly; nodocs-internal-workflows. - Checklist is the step index. Live-fetch only open work. RN merge is not a checkbox -- always
gh pr viewblocking RN URLs. - A PR URL in the RN table is blocking until merged. Skip only
No changes/N/A. Do not exempt Fleet, Agent, or any product by name. - Check boxes this skill just completed. Do not check anyone else's work (including docs-eng). Do not wait to be asked.
- Slack: read slack-templates.md before drafting or sending. Confirm before send; thread follow-ups on the FF announcement.
- Live/released Slack only after the gate (§0.3) and a user eyeball of the site. Do not draft before the gate.
- Empty args / "how's my release": session state → active docs issue. Do not ask which version if one is in flight. After closed-issue cleanup leaves none, stop -- do not rediscover.
- Cleanup = docs issue
CLOSEDonly. 404 = drop that ID and rediscover. No TTL. - RC varies each release -- read from the
#mission-controlcoordination thread or eng issue. Never hardcode a name. - Do not offer a Slack ping or PR whose issue box is already checked, or that the user already said they sent.
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.
- 1mo ago Changed 7887781251b1
- 1mo ago First seen · 386 lines · 110 tokens per session scan A c428b242d725
docs-stack-release is a skill published in the GitHub repository elastic/elastic-docs-skills (72 stars, last pushed yesterday), licensed Apache-2.0. It adds 110 tokens to every session and 6,905 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
skillshare-release
Prepare and review skillshare releases using the Release Please PR, verify the proposed version and changelog, inspect draft assets, and publish through the manual Publish Release workflow when explicitly authorized. Use when the user says "release", "prepare release", "cut a release", or asks to publish a new…
finishing-a-development-branch
A process for finishing a completed development branch. A branch is a separate line of code changes that can later be merged or submitted as a pull request.
skillshare-changelog
Generate CHANGELOG.md entry from recent commits in conventional format. Also syncs the website changelog page. Use this skill whenever the user asks to: generate a changelog, document what changed between tags, or create a new CHANGELOG entry. If you see requests like "write the changelog for v0.17", "what changed…
factory-ship
Experimental workflow for publishing and completing configured software delivery work. Use when the user or an enabled factory policy asks to ship.
prepare-release
Prepare a new release by collecting commits, generating bilingual release notes, updating version files, and creating a release branch. Use when asked to prepare/create a release, bump version, or run /prepare-release.