docs-content-type-checker

docs-content-type-checker is a skill for Claude Code from elastic/elastic-docs-skills. It costs 76 tokens per session (2,904 once invoked), scanned A, original, Apache-2.0.

A documentation checker for deciding whether an Elastic page fits a defined content type, such as a how-to, tutorial, or troubleshooting guide. It can also review an existing page or classify a planned page.

In plain words
What is it for?
Use it to review a documentation file or pasted page, or to decide which content type suits a planned page and what still needs to be written.
Why use it?
It helps prevent pages from using the wrong structure or missing required parts. It makes content-type decisions clearer before writing or reviewing documentation.

Skill for Claude Code ✓ vendor

Written for Claude Code: allowed-tools in frontmatter.

Part of the elastic-docs-skills plugin — 21 skills, 1 agent shipped together

Good fit Use it to review a documentation file or pasted page, or to decide which content type suits a planned page and what still needs to be written.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/elastic/elastic-docs-skills/content-type-checker
About the project

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.

elastic/elastic-docs-skills · 71 stars · on GitHub · elastic.github.io

Install

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.

Any agent
npx skills add elastic/elastic-docs-skills --skill content-type-checker
Clone the repo
git clone --depth 1 https://github.com/elastic/elastic-docs-skills

Made for: Claude Code.

Or install elastic-docs-skills, the plugin that ships this one along with the rest of its 21 skills, 1 agent.

Wrote 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.

agentmods badge for docs-content-type-checker

README.md
[![agentmods](https://agentmods.dev/badge/skills/elastic/elastic-docs-skills/content-type-checker/github.svg)](https://agentmods.dev/skills/elastic/elastic-docs-skills/content-type-checker)
Your own site
<a href="https://agentmods.dev/skills/elastic/elastic-docs-skills/content-type-checker"><img src="https://agentmods.dev/badge/skills/elastic/elastic-docs-skills/content-type-checker/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.

agentmods 80×15 button for docs-content-type-checker

Your own site · 80×15
<a href="https://agentmods.dev/skills/elastic/elastic-docs-skills/content-type-checker"><img src="https://agentmods.dev/badge/skills/elastic/elastic-docs-skills/content-type-checker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 76 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,904 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 2 findings, 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 Prompt Injection · line 81
    Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.
    Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
  • medium Prompt Injection · line 87
    Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.
    Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00076 $0.02904
Opus 5 $0.00038 $0.01452
Sonnet 5 $0.00015 $0.00581
Haiku 4.5 $0.00008 $0.00290

Measured 9d ago against content hash 22123b87b42d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

docs-content-type-checker 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.

skills/authoring/content-type-checker/SKILL.md · 226 lines

How it starts

The opening of the file, as written. The whole thing — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a content type compliance checker for Elastic documentation. You operate in two modes:

  • Validate mode — evaluate an existing page (file or pasted content) against the content type guidelines and report compliance issues.
  • Classify mode — given a short description of an unwritten page, decide which content type best fits and what required elements still need to be drafted.

Inputs

$ARGUMENTS is one of:

  • A file path or directory → validate mode
  • A block of pasted page content (frontmatter and/or markdown body) → validate mode
  • A short description of intended content (no file, no full body) → classify mode

If empty, ask the user what to check or classify.

Detect the mode

Decide which mode applies before proceeding:

  • Validate mode when the input is an existing file path, a directory, or pasted content that includes frontmatter or substantive markdown body.
  • Classify mode when the input is a description of a hypothetical or planned page — typical phrasings include "would this be a how-to?", "classify this idea: ...", "I want to write a page about X — what content type?", "should this be an overview or a how-to?", or any prompt that describes intent rather than presenting actual page content.

Read the full file on GitHub · 226 lines

Files

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.

Changes

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.

  1. 9d ago First seen · 226 lines · 76 tokens per session scan A 22123b87b42d

Subscribe to this mod's changes

docs-content-type-checker is a skill published in the GitHub repository elastic/elastic-docs-skills (71 stars, last pushed yesterday), licensed Apache-2.0. It adds 76 tokens to every session and 2,904 once invoked, about $0.0004 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.