Phoenix Pxi Playwright
Arize-ai/phoenix
Write, extend, and debug PXI Playwright E2E tests for Phoenix.
Write LLM evaluation spec files with datasets, tasks, and evaluators using the @kbn/evals Playwright fixture.
Install Evals Write Spec
$ npx skills add elastic/kibana --skill evals-write-spec -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install elastic/kibana evals-write-spec --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/elastic/kibana.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/evals-write-spec .claude/skills/evals-write-spec && rm -rf skills-srcUse ~/.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/
Install the "evals-write-spec" agent skill from https://github.com/elastic/kibana/tree/main/.agents/skills/evals-write-spec into .claude/skills/evals-write-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "evals-write-spec", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/elastic/kibana/tree/main/.agents/skills/evals-write-specType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add elastic/kibana --skill evals-write-spec -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install elastic/kibana evals-write-spec --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/elastic/kibana.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/evals-write-spec .agents/skills/evals-write-spec && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "evals-write-spec" agent skill from https://github.com/elastic/kibana/tree/main/.agents/skills/evals-write-spec into .agents/skills/evals-write-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "evals-write-spec", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add elastic/kibana --skill evals-write-spec -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install elastic/kibana evals-write-spec --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/elastic/kibana.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/evals-write-spec .cursor/skills/evals-write-spec && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "evals-write-spec" agent skill from https://github.com/elastic/kibana/tree/main/.agents/skills/evals-write-spec into .cursor/skills/evals-write-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "evals-write-spec", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/elastic/kibana.git --path .agents/skills/evals-write-spec--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add elastic/kibana --skill evals-write-spec -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install elastic/kibana evals-write-spec --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/elastic/kibana.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/evals-write-spec .gemini/skills/evals-write-spec && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "evals-write-spec" agent skill from https://github.com/elastic/kibana/tree/main/.agents/skills/evals-write-spec into .gemini/skills/evals-write-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "evals-write-spec", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install elastic/kibana evals-write-specInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add elastic/kibana --skill evals-write-spec -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/elastic/kibana.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/evals-write-spec .github/skills/evals-write-spec && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "evals-write-spec" agent skill from https://github.com/elastic/kibana/tree/main/.agents/skills/evals-write-spec into .github/skills/evals-write-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "evals-write-spec", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add elastic/kibana --skill evals-write-spec -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install elastic/kibana evals-write-spec --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/elastic/kibana.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/evals-write-spec .opencode/skills/evals-write-spec && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "evals-write-spec" agent skill from https://github.com/elastic/kibana/tree/main/.agents/skills/evals-write-spec into .opencode/skills/evals-write-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "evals-write-spec", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
evals-write-spec- GitHub stars
- 21k
- Token cost
- ~2.3k tokens
- SKILL.md length
- 575 words
- Files
- 3 (incl. references)
- Skills in repo
- 40
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Write LLM evaluation spec files with datasets, tasks, and evaluators using the @kbn/evals Playwright fixture.
- Works in 2 steps: Inline array -- pass evaluator objects… → selectEvaluators -- typed wrapper that…
- Authoring new eval specs
- SKILL.md covers Spec File Anatomy, Tags, Datasets and Tasks, plus 7 more sections
- Calls node
What it does
Evals Write Spec is an agent skill from elastic/kibana, published by the product's own GitHub organization. Write LLM evaluation spec files with datasets, tasks, and evaluators using the @kbn/evals Playwright fixture. Use when authoring new eval specs, adding datasets or evaluators, or debugging evaluation test failures.
Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `agents/openai.yaml` and `references/evaluator-patterns.md`).
It sits in AI & LLM Engineering, covering LLM evaluation. It works with Playwright. The repository describes itself as: Your window into all of your data.
When your agent uses it
- Authoring new eval specs
- Adding datasets
- Debugging evaluation test failures
Example prompts
- “/evals-write-spec”
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- Inline array -- pass evaluator objects directly (simple suites)
- selectEvaluators -- typed wrapper that enforces Example/TaskOutput generics
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
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
Evals Write Spec loads about 2.3k tokens when it runs, and up to ~4.4k if it reads all its reference files. Until then it costs about 58 tokens; SKILL.md has 575 words of instructions outside code blocks.
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); files beside SKILL.md 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 575 words (~2,342 tokens).
“Eval specs use the evaluate Playwright fixture (not test). A spec file follows this structure:”
- name
- evals-write-spec
- disable-model-invocation
- true
Files
SKILL.md and 2 other files (references) in .agents/skills/evals-write-spec of elastic/kibana.
- SKILL.md
- agents/openai.yaml
- references/evaluator-patterns.md
Open the folder on GitHubat commit ee7c86b
Compare with similar skills
Evals Write Spec 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Evals Write Spec this skillelastic/kibana | 21k | — | ~2.3k | Automated safety check: Pass | Custom licence | |
| Phoenix Pxi PlaywrightArize-ai/phoenix | 12k | — | ~2.6k | Automated safety check: Pass | Custom licence | |
| Eval Loopjacob-dietle/context-os | 111 | — | ~5.2k | Automated safety check: Pass | MIT | |
| LLM Benchmarking with lm-evaluation-harnessOrchestra-Research/AI-Research-SKILLs | 13k | 8 repos | ~3k | Automated safety check: Pass | MIT | |
| Azure AI Projects Python SDKmicrosoft/skills | 3.1k | 6 repos | ~2.8k | Automated safety check: Pass | MIT | |
| Fine-Tuning ExpertJeffallan/claude-skills | 12k | 1 repos | ~1.7k | Automated safety check: Pass | MIT |
Similar skills
Eval Loop
jacob-dietle/context-os
This skill should be used when a specific quality problem (UX, data, architecture, feature) needs systematic diagnosis and iterative fixing toward a defined target.
LLM Benchmarking with lm-evaluation-harness
Orchestra-Research/AI-Research-SKILLs
Runs lm-evaluation-harness to benchmark language models on academic suites such as MMLU, GSM8K and HumanEval, compare models and track training checkpoints.
- Official
Azure AI Projects Python SDK
microsoft/skills
Reference for building on Microsoft Foundry with the azure-ai-projects Python SDK: project clients, versioned agents, evaluations, connections, datasets and indexes.
Fine-Tuning Expert
Jeffallan/claude-skills
Guides LLM fine-tuning with LoRA and QLoRA through Hugging Face PEFT, from dataset validation and training checks to adapter merging, quantization and deployment.
Looper
ksimback/looper
Scaffold a well-designed agent loop with best-practice coaching and a cross-model review council.
More from elastic/kibana
All 40 skills in this repo- Official
Cypress To Scout Migration
elastic/kibana
Migrate Kibana Cypress E2E tests (.cy.ts) to Scout (Playwright).
- Official
Activate Connector
elastic/kibana
Creates a connector instance in a running Kibana. An agent skill from elastic/kibana.
- Official
Codeql
elastic/kibana
Work with CodeQL in Kibana — write, test, and debug custom queries locally, fetch scan results from GitHub, and validate inline suppression comments.
- Official
Debug Oas
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…
- Official
Kbn GitHub
elastic/kibana
GitHub interactions via gh CLI for the Kibana repo. An agent skill from elastic/kibana.
- Official
Kibana Privilege Deprecation
elastic/kibana
Implement and review Kibana feature privilege deprecations. An agent skill from elastic/kibana.
Related
Works with
Categories
Questions about Evals Write Spec
What does Evals Write Spec do?
Write LLM evaluation spec files with datasets, tasks, and evaluators using the @kbn/evals Playwright fixture. Evals Write Spec is an agent skill from elastic/kibana, published by the product's own GitHub organization. Write LLM evaluation spec files with datasets, tasks, and evaluators using the @kbn/evals Playwright fixture.
When should I use Evals Write Spec?
Evals Write Spec fits situations like: authoring new eval specs; adding datasets; debugging evaluation test failures.
How do I install Evals Write Spec in Claude Code?
Run `npx skills add elastic/kibana --skill evals-write-spec -a claude-code`. Or copy the skill folder (.agents/skills/evals-write-spec in elastic/kibana) into .claude/skills/evals-write-spec in your project. Claude Code loads it when a task matches its description.
How do I install Evals Write Spec in Codex?
Run `npx skills add elastic/kibana --skill evals-write-spec -a codex`. Or copy the skill folder (.agents/skills/evals-write-spec in elastic/kibana) into .agents/skills/evals-write-spec in your project. Codex loads it when a task matches its description.
Can I use Evals Write Spec 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 evals-write-spec -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/evals-write-spec, .gemini/skills/evals-write-spec, .github/skills/evals-write-spec and .opencode/skills/evals-write-spec in your project.
What does Evals Write Spec need to run?
Going by SKILL.md and its folder, Evals Write Spec needs the command-line tools its instructions call (node).
Does Evals Write Spec 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 Evals Write Spec 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. Review the folder before installing.
What licence does Evals Write Spec use?
Evals Write Spec 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 Evals Write Spec use?
About 2.3k tokens (SKILL.md is roughly 9.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2k tokens, read only when the agent opens those files.
What are the alternatives to Evals Write Spec?
Skills that share tags, products or a category with Evals Write Spec: Phoenix Pxi Playwright (Arize-ai/phoenix, 12k stars), Eval Loop (jacob-dietle/context-os, 111 stars), LLM Benchmarking with lm-evaluation-harness (Orchestra-Research/AI-Research-SKILLs, 13k stars) and Azure AI Projects Python SDK (microsoft/skills, 3.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Evals Write Spec?
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.