Cypress To Scout Migration
elastic/kibana
Migrate Kibana Cypress E2E tests (.cy.ts) to Scout (Playwright).
Analyzes an OpenSpec requirements spec for internal consistency, implementation compliance, and test opportunities; when a shell is available, run openspec validate first for structural checks.
OfficialApache-2.0Auto-check passed
Install Requirements Verification
$ npx skills add elastic/terraform-provider-elasticstack --skill requirements-verification -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install elastic/terraform-provider-elasticstack requirements-verification --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/terraform-provider-elasticstack.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/requirements-verification .claude/skills/requirements-verification && 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 "requirements-verification" agent skill from https://github.com/elastic/terraform-provider-elasticstack/tree/main/.agents/skills/requirements-verification into .claude/skills/requirements-verification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "requirements-verification", 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/terraform-provider-elasticstack/tree/main/.agents/skills/requirements-verificationType 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/terraform-provider-elasticstack --skill requirements-verification -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install elastic/terraform-provider-elasticstack requirements-verification --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/elastic/terraform-provider-elasticstack.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/requirements-verification .agents/skills/requirements-verification && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "requirements-verification" agent skill from https://github.com/elastic/terraform-provider-elasticstack/tree/main/.agents/skills/requirements-verification into .agents/skills/requirements-verification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "requirements-verification", 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/terraform-provider-elasticstack --skill requirements-verification -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install elastic/terraform-provider-elasticstack requirements-verification --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/elastic/terraform-provider-elasticstack.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/requirements-verification .cursor/skills/requirements-verification && 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 "requirements-verification" agent skill from https://github.com/elastic/terraform-provider-elasticstack/tree/main/.agents/skills/requirements-verification into .cursor/skills/requirements-verification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "requirements-verification", 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/terraform-provider-elasticstack.git --path .agents/skills/requirements-verification--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/terraform-provider-elasticstack --skill requirements-verification -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install elastic/terraform-provider-elasticstack requirements-verification --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/elastic/terraform-provider-elasticstack.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/requirements-verification .gemini/skills/requirements-verification && 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 "requirements-verification" agent skill from https://github.com/elastic/terraform-provider-elasticstack/tree/main/.agents/skills/requirements-verification into .gemini/skills/requirements-verification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "requirements-verification", 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/terraform-provider-elasticstack requirements-verificationInstalls 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/terraform-provider-elasticstack --skill requirements-verification -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/elastic/terraform-provider-elasticstack.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/requirements-verification .github/skills/requirements-verification && 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 "requirements-verification" agent skill from https://github.com/elastic/terraform-provider-elasticstack/tree/main/.agents/skills/requirements-verification into .github/skills/requirements-verification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "requirements-verification", 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/terraform-provider-elasticstack --skill requirements-verification -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/terraform-provider-elasticstack requirements-verification --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/elastic/terraform-provider-elasticstack.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/requirements-verification .opencode/skills/requirements-verification && 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 "requirements-verification" agent skill from https://github.com/elastic/terraform-provider-elasticstack/tree/main/.agents/skills/requirements-verification into .opencode/skills/requirements-verification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "requirements-verification", 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
requirements-verification- GitHub stars
- 210
- Token cost
- ~1.8k tokens
- SKILL.md length
- 681 words
- Files
- 2
- Skills in repo
- 21
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Analyzes an OpenSpec requirements spec for internal consistency, implementation compliance, and test opportunities; when a shell is available, run openspec validate first for structural checks.
- Works in 6 steps: OpenSpec structural validation… → Parse the requirements document → Internal consistency → …
- Reviewing specs
- SKILL.md covers Input, Workflow, Output format and Reference
- Calls make and npm
What it does
Requirements Verification is an agent skill from elastic/terraform-provider-elasticstack, published by the product's own GitHub organization. Analyzes an OpenSpec requirements spec for internal consistency, implementation compliance, and test opportunities; when a shell is available, run openspec validate first for structural checks. Use when reviewing specs, verifying implementation against requirements, or identifying test gaps.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `reference.md`).
It works with Elasticsearch. The repository describes itself as: Terraform provider for Elastic Stack. The licence is Apache-2.0.
When your agent uses it
- Reviewing specs
- Verifying implementation against requirements
- Identifying test gaps
Example prompts
- “Use the requirements-verification skill to analyz an OpenSpec requirements spec for internal consistency, implementation compliance, and test…”
- “/requirements-verification”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit ab9d355. 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:
makenpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.
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
Requirements Verification loads about 1.8k tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 681 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
The full file from elastic/terraform-provider-elasticstack at commit ab9d355, republished under its Apache-2.0 licence (© elastic). 681 words, ~1,796 tokens.
Download SKILL.mdSave it as
.claude/skills/requirements-verification/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- requirements-verification
- description
- Analyzes an OpenSpec requirements spec for internal consistency, implementation compliance, and test opportunities; when a shell is available, run openspec validate first for structural checks. Use when reviewing specs, verifying implementation against requirements, or identifying test gaps.
Requirements Document Analysis
Analyze an OpenSpec requirements spec (from openspec/specs/<capability>/spec.md, or a delta spec under openspec/changes/**/specs/) and produce three outputs:
- Internal consistency — whether requirements contradict each other or the schema.
- Implementation compliance — whether the implementation meets each requirement.
- Test opportunities — concrete unit or acceptance tests that would verify requirements programmatically.
Input
- Requirements document: User specifies the path (e.g.
openspec/specs/elasticsearch-security-role/spec.md) or the entity name/implementation path. Resolve to thespec.mdunderopenspec/specs/<capability>/(or the relevant delta spec path). - Implementation: From the doc’s “Resource implementation” or “Data source implementation” line (e.g.
internal/elasticsearch/security/role). Use that package for compliance and test analysis.
Workflow
0. OpenSpec structural validation (recommended when a shell is available)
Before deep analysis, run the OpenSpec CLI so the spec matches what CI enforces. This checks structure (e.g. ### Requirement: / #### Scenario: shape, SHALL / MUST in requirement bodies)—not semantic consistency or implementation compliance.
- Repo root, after
make setup(ormake setup-openspec/npm ci):make check-openspec
or:OPENSPEC_TELEMETRY=0 ./node_modules/.bin/openspec validate --specs - Single spec (optional):
OPENSPEC_TELEMETRY=0 ./node_modules/.bin/openspec validate <capability> --type spec(e.g.elasticsearch-security-role) - Active change deltas (optional):
openspec validate --allto includeopenspec/changes/**
If validation fails, report the CLI errors first and fix the markdown before spending effort on sections 1–3. If no terminal is available, proceed with manual review and note that openspec validate was not run.
1. Parse the requirements document
- Read the doc and extract: title/type name, implementation path (from
Resource implementation:/Data source implementation:/Workflow implementation:/Script implementation:), Purpose, Schema (HCL/YAML block if present). - List every
### Requirement:section: id (use(REQ-NNN)or(REQ-001–REQ-003)from the heading if present; otherwise derive a short id from the heading), category (infer from content: API, Identity, Import, etc.), and text (full SHALL/MUST statements in that section). Normalize references (e.g. “id format”, “cluster_uuid/name”) for consistency checks.
2. Internal consistency
Apply the checks in reference.md (Consistency checks):
- Identity/Import: Same id format in Identity and Import requirements; no conflicting formats.
- Schema vs requirements: Required/optional/computed in schema matches what requirements imply (e.g. “when X is configured” implies X is optional or optional+computed).
- Lifecycle: No requirement that X triggers replace and another that X is updated in place.
- Compatibility: Version numbers and feature names aligned across requirements; no conflicting minimum versions for the same feature.
- State/Plan: No requirement that the resource “preserve null” and another that it “store empty list” for the same field.
- StateUpgrade: Referenced prior schema version exists; upgrade steps are ordered and non-conflicting.
Output: Consistent or list Inconsistencies with requirement ids and short explanation.
Show full SKILL.md (272 more words)Show less
3. Implementation compliance
- Resolve implementation package from the doc (e.g.
internal/elasticsearch/security/role). Locateresource.go,schema.go,create.go,read.go,update.go,delete.go,models.go, state upgrade code, and any validators/plan modifiers. - For each requirement, determine where the behavior would be implemented (see reference.md “Requirement → implementation mapping”). Search or read that code and verify the behavior.
- Classify each requirement: Met (code clearly implements it), Not met (code contradicts or omits it), Unclear (cannot determine from code or tests).
- Output: Table or list: REQ-ID, Category, Status (Met / Not met / Unclear), Evidence (file/function or “not found”).
4. Test opportunities
- Locate unit tests:
*_test.goin the implementation package (e.g.resource_test.go,state_upgrade_test.go) and acceptance tests:acc_test.go(or*_acc_test.go) for the resource. - For each requirement, decide whether it is verifiable by unit test (e.g. state upgrade logic, id parsing, validation) or verifiable by acceptance test (e.g. create/read/update/delete, import, error diagnostics). See reference.md “Test opportunity patterns”.
- Identify requirements that are not covered by existing tests (or only weakly covered). Suggest concrete test cases: unit test name + scenario, or acceptance test step (config + checks) that would assert the requirement.
- Output: List of Suggested tests, each with: requirement id(s), type (unit / acceptance), description, and how it would verify the requirement.
5. Report
Produce a single report with three sections:
- Internal consistency: Result + any inconsistencies.
- Implementation compliance: Summary (e.g. X/Y met, Z unclear) + per-requirement status table.
- Test opportunities: List of suggested tests with requirement ids and verification approach.
Output format
# Requirements analysis: <entity name>
**Document**: `openspec/specs/.../spec.md`
**Implementation**: `internal/...` (or workflow/script path from the spec)
## 1. Internal consistency
- **Result**: Consistent | Inconsistent
- **Inconsistencies** (if any): [REQ-xxx] vs [REQ-yyy]: ...
## 2. Implementation compliance
| REQ-ID | Category | Status | Evidence |
|--------|------------|----------|----------|
| REQ-001| API | Met | create.go, update.go call PutRole |
...
**Summary**: X met, Y not met, Z unclear.
## 3. Test opportunities
| REQ-ID(s) | Type | Suggested test | Verifies |
|-----------|------------|----------------|----------|
| REQ-008 | Acceptance | Import with invalid id; expect error diagnostic | Import validation |
...Reference
- OpenSpec authoring and CLI overview:
dev-docs/high-level/openspec-requirements.md - Requirement categories and implementation mapping: reference.md
- Existing entity code-path checklist (for locating implementation):
.agents/skills/existing-entity-requirements/reference.md - Schema/acceptance test coverage (for test patterns):
.cursor/skills/schema-coverage/if analyzing attribute-level coverage alongside requirements.
© elastic, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in .agents/skills/requirements-verification of elastic/terraform-provider-elasticstack.
- SKILL.md
- reference.md
Open the folder on GitHubat commit ab9d355
Compare with similar skills
Requirements Verification 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 |
|---|---|---|---|---|---|---|
| Requirements Verification this skillelastic/terraform-provider-elasticstack | 210 | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Cypress To Scout Migrationelastic/kibana | 21k | — | ~3.8k | Automated safety check: Pass | Custom licence | |
| Activate Connectorelastic/kibana | 21k | — | ~1.9k | Automated safety check: Notes | Custom licence | |
| Codeqlelastic/kibana | 21k | — | ~1.7k | Automated safety check: Pass | Custom licence | |
| Debug Oaselastic/kibana | 21k | — | ~1.4k | Automated safety check: Pass | Custom licence | |
| Security Case Managementelastic/agent-skills | 592 | 1 repos | ~2.6k | Automated safety check: Notes | Apache-2.0 |
Similar skills
- Official
- 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
Security Case Management
elastic/agent-skills
Create, search, update, and manage SOC cases via the Kibana Cases API.
- Official
Ecs Rfc Guide
elastic/ecs
Guides contributors through the Elastic Common Schema (ECS) RFC (Proposal) process: template sections, target maturity (alpha/beta), rfcs/text artifacts, and optional OTel mapping.
More from elastic/terraform-provider-elasticstack
All 21 skills in this repo- Official
Openspec Explore
elastic/terraform-provider-elasticstack
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements.
- Official
Openspec Apply Change
elastic/terraform-provider-elasticstack
Implement tasks from an OpenSpec change. An agent skill from elastic/terraform-provider-elasticstack.
- Official
Openspec Archive Change
elastic/terraform-provider-elasticstack
Archive a completed change in the experimental workflow. An agent skill from elastic/terraform-provider-elasticstack.
- Official
PR Monitoring Loop
elastic/terraform-provider-elasticstack
Monitor GitHub pull requests through a subagent-based loop that watches CI checks, review comments, PR comments, review state, merge conflicts, and branch freshness.
- Official
Openspec Plus Proposal
elastic/terraform-provider-elasticstack
MANDATORY skill that activates whenever the OpenSpec proposal phase begins.
- Official
Openspec Propose
elastic/terraform-provider-elasticstack
Propose a new change with all artifacts generated in one step.
Related
Works with
Questions about Requirements Verification
What does Requirements Verification do?
Analyzes an OpenSpec requirements spec for internal consistency, implementation compliance, and test opportunities; when a shell is available, run openspec validate first for structural checks. Requirements Verification is an agent skill from elastic/terraform-provider-elasticstack, published by the product's own GitHub organization. Analyzes an OpenSpec requirements spec for internal consistency, implementation compliance, and test opportunities; when a shell is available, run openspec validate first for structural checks.
When should I use Requirements Verification?
Requirements Verification fits situations like: reviewing specs; verifying implementation against requirements; identifying test gaps.
How do I install Requirements Verification in Claude Code?
Run `npx skills add elastic/terraform-provider-elasticstack --skill requirements-verification -a claude-code`. Or copy the skill folder (.agents/skills/requirements-verification in elastic/terraform-provider-elasticstack) into .claude/skills/requirements-verification in your project. Claude Code loads it when a task matches its description.
How do I install Requirements Verification in Codex?
Run `npx skills add elastic/terraform-provider-elasticstack --skill requirements-verification -a codex`. Or copy the skill folder (.agents/skills/requirements-verification in elastic/terraform-provider-elasticstack) into .agents/skills/requirements-verification in your project. Codex loads it when a task matches its description.
Can I use Requirements Verification 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/terraform-provider-elasticstack --skill requirements-verification -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/requirements-verification, .gemini/skills/requirements-verification, .github/skills/requirements-verification and .opencode/skills/requirements-verification in your project.
What does Requirements Verification need to run?
Going by SKILL.md and its folder, Requirements Verification needs the command-line tools its instructions call (make and npm).
Does Requirements Verification access the network?
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Requirements Verification 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 Requirements Verification use?
Requirements Verification is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Requirements Verification use?
About 1.8k tokens (SKILL.md is roughly 7.2k 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 Requirements Verification?
Skills that share tags, products or a category with Requirements Verification: Cypress To Scout Migration (elastic/kibana, 21k stars), Activate Connector (elastic/kibana, 21k stars), Codeql (elastic/kibana, 21k stars) and Debug Oas (elastic/kibana, 21k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Requirements Verification?
elastic (a GitHub organization, an official publisher) maintains it in elastic/terraform-provider-elasticstack, which has 210 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 9, 2026.
Source: elastic/terraform-provider-elasticstack on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.