Official agent skill

Debug Oas

by elastic in elastic/kibana

A skill your agent uses when debugging OpenAPI (OAS) issues for a specific API area in Kibana by scoping validation output with one or more --path filters, then separating structural invalid-OAS…

OfficialCustom licenceAuto-check passedBackend & APIs

Install Debug Oas

skills CLI
$ npx skills add elastic/kibana --skill debug-oas -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install elastic/kibana debug-oas --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/elastic/kibana.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/debug-oas .claude/skills/debug-oas && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
debug-oas
GitHub stars
21k
Token cost
~1.4k tokens
SKILL.md length
632 words
Files
3 (incl. scripts)
Skills in repo
40
Repo updated
First seen
Licence
Custom licence

At a glance

A skill your agent uses when debugging OpenAPI (OAS) issues for a specific API area in Kibana by scoping validation output with one or more --path filters, then separating structural invalid-OAS…

  • Works in 6 steps: Ask what APIs the developer is working on. → Ask for one or more HTTP API paths (for… → Refresh generated OAS first when needed… → …
  • Debugging OpenAPI (OAS) issues for a specific API area in Kibana by scoping validation output with one
  • SKILL.md covers Overview, Required interaction flow, Path format guidance and Commands, plus 4 more sections
  • Runs JavaScript scripts from its folder; calls node

What it does

Debug Oas is an agent skill from elastic/kibana, published by the product's own GitHub organization. Use when debugging OpenAPI (OAS) issues for a specific API area in Kibana by scoping validation output with one or more --path filters, then separating structural invalid-OAS failures from quality or documentation gaps such as missing descriptions.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts (for example `agents/openai.yaml` and `scripts/extract_structural_oas_issues.js`).

It sits in Backend & APIs, covering Debugging and OpenAPI specifications. It works with Elasticsearch and OpenAPI. The repository describes itself as: Your window into all of your data.

When your agent uses it

  • Debugging OpenAPI (OAS) issues for a specific API area in Kibana by scoping validation output with one
  • More --path filters
  • Then separating structural invalid-OAS failures from quality
  • Documentation gaps such as missing descriptions

Example prompts

  • “/debug-oas”

Requirements

  • Node.js

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Ask what APIs the developer is working on.
  2. Ask for one or more HTTP API paths (for example /api/fleet/agent_policies).
  3. Refresh generated OAS first when needed by following the environment setup flow in validate-oas.
  4. Run validation with those route-style --path filters.
  5. Classify the resulting issues into structural vs quality.
  6. Display the command output directly so the developer can see current issues.

What it can do on your machine

Read from SKILL.md and the folder at commit ee7c86b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (JavaScript), which the agent can run.

    Shell commands in SKILL.md call:

    • node

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Debug Oas loads about 1.4k tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 632 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~65
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 632 words (~1,447 tokens).

“Use node ./scripts/validate_oas_docs.js to validate Kibana OAS, but always scope output with --path so developers can focus on the API area they are actively changing.”

— opening of SKILL.md by elastic, Custom licence
name
debug-oas
user-invocable
true
disable-model-invocation
true

Read the full SKILL.md on GitHub

Files

SKILL.md and 2 other files (scripts) in .agents/skills/debug-oas of elastic/kibana.

  • SKILL.md
  • agents/openai.yaml
  • scripts/extract_structural_oas_issues.js

Open the folder on GitHubat commit ee7c86b

Compare with similar skills

Debug Oas next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Debug Oas compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Debug Oas this skillelastic/kibana21k—~1.4kAutomated safety check: PassCustom licence
Detecting Debug Endpointsjeremylongshore/tons-of-skills-marketplace2.8k—~2kAutomated safety check: PassMIT
Agents Connectaws/agent-toolkit-for-aws2.8k—~7.4kAutomated safety check: NotesApache-2.0
ToolJet Marketplace Plugin BuilderToolJet/ToolJet41k—~2.1kAutomated safety check: PassAGPL-3.0
CLI Creatorhuangruiteng/CS-Notes4k2 repos~2.7kAutomated safety check: PassApache-2.0
Api2clialexknowshtml/api2cli455—~2.9kAutomated safety check: PassMIT

Similar skills

  • Detecting Debug Endpoints

    jeremylongshore/tons-of-skills-marketplace

    Probe a target for accidentally-public admin / debug / introspection endpoints — Spring Boot Actuator, Apache server-status, Prometheus metrics, GraphQL playground, Swagger UI, phpMyAdmin…

    2.8k GitHub stars~2k tokensUpdated today
    Backend & APIsAuto-check passed
  • Agents Connect

    aws/agent-toolkit-for-aws

    Official

    A skill your agent uses when connecting your agent to external APIs, tools, or services via Gateway, or restricting tool access with Cedar policies.

    2.8k GitHub stars~7.4k tokensUpdated today
    Backend & APIsAuto-check: notes
  • Turns an API description, such as an OpenAPI file or a Postman collection, into a connector plugin for ToolJet's marketplace and checks it with the repo's validator.

    41k GitHub stars~2.1k tokensUpdated today
    Backend & APIsAuto-check passed
  • CLI Creator

    huangruiteng/CS-Notes

    Build a composable CLI for Codex from API docs, an OpenAPI spec, existing curl examples, an SDK, a web app, an admin tool, or a local script.

    4k GitHub starsUsed in 2 repos~2.7k tokens
    Backend & APIsAuto-check passed
  • Api2cli

    alexknowshtml/api2cli

    Generate a working CLI from any API, then wrap it in a Claude Code skill.

    455 GitHub stars~2.9k tokensUpdated 7 mo ago
    Backend & APIsAuto-check passed
  • Vibex

    Raja0sama/vibex

    Diagrams and checkable docs from a codebase. An agent skill from Raja0sama/vibex.

    388 GitHub stars~7.8k tokensUpdated yesterday
    Backend & APIsAuto-check passed

More from elastic/kibana

All 40 skills in this repo
  • Official

    Migrate Kibana Cypress E2E tests (.cy.ts) to Scout (Playwright).

    21k GitHub stars~3.8k tokensUpdated today
    Auto-check passed
  • Activate Connector

    elastic/kibana

    Official

    Creates a connector instance in a running Kibana. An agent skill from elastic/kibana.

    21k GitHub stars~1.9k tokensUpdated today
    Auto-check: notes
  • Codeql

    elastic/kibana

    Official

    Work with CodeQL in Kibana — write, test, and debug custom queries locally, fetch scan results from GitHub, and validate inline suppression comments.

    21k GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • Evals Write Spec

    elastic/kibana

    Official

    Write LLM evaluation spec files with datasets, tasks, and evaluators using the @kbn/evals Playwright fixture.

    21k GitHub stars~2.3k tokensUpdated today
    Auto-check passed
  • Kbn GitHub

    elastic/kibana

    Official

    GitHub interactions via gh CLI for the Kibana repo. An agent skill from elastic/kibana.

    21k GitHub stars~1.3k tokensUpdated today
    Auto-check passed
  • Official

    Implement and review Kibana feature privilege deprecations. An agent skill from elastic/kibana.

    21k GitHub stars~2k tokensUpdated today
    Auto-check passed

Questions about Debug Oas

What does Debug Oas do?

A skill your agent uses when debugging OpenAPI (OAS) issues for a specific API area in Kibana by scoping validation output with one or more --path filters, then separating structural invalid-OAS…. Debug Oas is an agent skill from elastic/kibana, published by the product's own GitHub organization. Use when debugging OpenAPI (OAS) issues for a specific API area in Kibana by scoping validation output with one or more --path filters, then separating structural invalid-OAS failures from quality or documentation gaps such as missing descriptions.

When should I use Debug Oas?

Debug Oas fits situations like: debugging OpenAPI (OAS) issues for a specific API area in Kibana by scoping validation output with one; more --path filters; then separating structural invalid-OAS failures from quality; documentation gaps such as missing descriptions.

How do I install Debug Oas in Claude Code?

Run `npx skills add elastic/kibana --skill debug-oas -a claude-code`. Or copy the skill folder (.agents/skills/debug-oas in elastic/kibana) into .claude/skills/debug-oas in your project. Claude Code loads it when a task matches its description.

How do I install Debug Oas in Codex?

Run `npx skills add elastic/kibana --skill debug-oas -a codex`. Or copy the skill folder (.agents/skills/debug-oas in elastic/kibana) into .agents/skills/debug-oas in your project. Codex loads it when a task matches its description.

Can I use Debug Oas in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add elastic/kibana --skill debug-oas -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/debug-oas, .gemini/skills/debug-oas, .github/skills/debug-oas and .opencode/skills/debug-oas in your project.

What does Debug Oas need to run?

Going by SKILL.md and its folder, Debug Oas needs JavaScript for the scripts in its folder and the command-line tools its instructions call (node). Our summary lists: Node.js.

Does Debug Oas access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Debug Oas safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Debug Oas use?

Debug Oas has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Debug Oas use?

About 1.4k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Debug Oas?

Skills that share tags, products or a category with Debug Oas: Detecting Debug Endpoints (jeremylongshore/tons-of-skills-marketplace, 2.8k stars), Agents Connect (aws/agent-toolkit-for-aws, 2.8k stars), ToolJet Marketplace Plugin Builder (ToolJet/ToolJet, 41k stars) and CLI Creator (huangruiteng/CS-Notes, 4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Debug Oas?

elastic (a GitHub organization, an official publisher) maintains it in elastic/kibana, which has 21,310 GitHub stars. The repository holds 40 skills in this directory. The repository was last updated on October 8, 2026.

Source: elastic/kibana on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.