New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Existing Entity Requirements

by elastic in elastic/terraform-provider-elasticstack

Examines an existing Terraform resource or data source implementation and produces an OpenSpec requirements document under openspec/specs/.

OfficialApache-2.0Auto-check passedDevOps & Cloud

Install Existing Entity Requirements

skills CLI
$ npx skills add elastic/terraform-provider-elasticstack --skill existing-entity-requirements -a claude-code

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

GitHub CLI
$ gh skill install elastic/terraform-provider-elasticstack existing-entity-requirements --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/terraform-provider-elasticstack.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/existing-entity-requirements .claude/skills/existing-entity-requirements && 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
existing-entity-requirements
GitHub stars
210
Token cost
~1.1k tokens
SKILL.md length
376 words
Files
2
Skills in repo
21
Repo updated
First seen
Licence
Apache-2.0

At a glance

Examines an existing Terraform resource or data source implementation and produces an OpenSpec requirements document under openspec/specs/.

  • Works in 4 steps: Locate implementation → Examine code path → Write the spec → …
  • The user asks to document requirements for a Terraform entity
  • SKILL.md covers Input, Workflow, Output format and Reference
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Existing Entity Requirements is an agent skill from elastic/terraform-provider-elasticstack, published by the product's own GitHub organization. Examines an existing Terraform resource or data source implementation and produces an OpenSpec requirements document under openspec/specs/. Use when the user asks to document requirements for a Terraform entity, capture behavior from code, or write a requirements doc for a resource/data source.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `reference.md`).

It sits in DevOps & Cloud, covering Infrastructure as code and PRD writing. It works with Terraform and Elasticsearch. The repository describes itself as: Terraform provider for Elastic Stack. The licence is Apache-2.0.

When your agent uses it

  • The user asks to document requirements for a Terraform entity
  • Capture behavior from code
  • Write a requirements doc for a resource/data source

Example prompts

  • “Use the existing-entity-requirements skill to examine an existing Terraform resource or data source implementation and produces an OpenSpec…”
  • “/existing-entity-requirements”

Workflow steps

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

  1. Locate implementation
  2. Examine code path
  3. Write the spec
  4. Quality

What it can do on your machine

Read from SKILL.md and the folder at commit b6bbc21. 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

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    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

Existing Entity Requirements loads about 1.1k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 376 words of instructions outside code blocks.

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

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 b6bbc21, republished under its Apache-2.0 licence (© elastic). 376 words, ~1,089 tokens.

Download SKILL.mdSave it as .claude/skills/existing-entity-requirements/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
existing-entity-requirements
description
Examines an existing Terraform resource or data source implementation and produces an OpenSpec requirements document under openspec/specs/. Use when the user asks to document requirements for a Terraform entity, capture behavior from code, or write a requirements doc for a resource/data source.

Entity Requirements Documentation

Produce an OpenSpec spec (spec.md) for an existing Terraform resource or data source by examining its code path and capturing behavior. Follow dev-docs/high-level/openspec-requirements.md and the OpenSpec shape: ## Purpose, optional ## Schema, ## Requirements with ### Requirement: and #### Scenario: blocks; use SHALL / MUST in requirement text.

Input

  • Entity: User specifies the Terraform entity (e.g. elasticstack_elasticsearch_security_role) or the implementation path (e.g. internal/elasticsearch/security/role).
  • Resolve the implementation package:
  • For Plugin Framework based entities, search for req.ProviderTypeName + "_...".
  • For SDK based entities, this is defined in internal/provider/provider.go.

Workflow

  1. Locate implementation

    • Resource: Package under internal/ containing resource.Resource and Schema, Create, Read, Update, Delete (and optionally ImportState, UpgradeState).
    • Data source: Package or file (e.g. *_data_source.go) containing a data source Schema and Read.

  2. Examine code path
    Use the checklist in reference.md so nothing is missed:

    • Schema (attributes, blocks, required/optional/computed, plan modifiers, validators).
    • Metadata: type name, import, state upgrade.
    • CRUD: which APIs are called, how id is set, how errors and “not found” are handled.
    • Connection: default client vs resource-level override (e.g. elasticsearch_connection).
    • Compatibility: version checks and “Unsupported Feature” behavior.
    • Mapping: config/API/state (JSON parsing, empty vs null, preserve-unknown behavior).
    • Lifecycle: replacement vs in-place update (e.g. RequiresReplace).

  3. Write the spec

    • Path: openspec/specs/<capability>/spec.md (e.g. openspec/specs/elasticsearch-security-role/spec.md). Use a stable capability id: <backend>-<area>-<resource> (see authoring guide).
    • Title and implementation: H1 title and a line Resource implementation: or Data source implementation: with the Go package path (as in legacy docs).
    • Purpose: Short ## Purpose paragraph.
    • Schema: Optional ## Schema with HCL-style block listing each attribute/block with <required|optional|optional+computed|computed>, types, and notes. Example reference: openspec/specs/elasticsearch-security-role/spec.md.
    • Requirements: ### Requirement: … sections (group related behaviors; reference legacy REQ ids in titles like (REQ-001–REQ-003) when useful). Each requirement body MUST contain SHALL or MUST. Add #### Scenario: blocks (Given/When/Then) for verifiable behavior. Derive everything from the code; do not invent behavior. Categories: API, Identity, Import, Lifecycle, Connection, Compatibility, Create/Update, Read, Delete, Mapping, Plan/State, State, StateUpgrade. See reference.md.

  4. Quality

    • Every requirement must be traceable to the implementation (file/function or logic).
    • Schema and requirements must be consistent (e.g. if schema has description optional with a version note, there must be a Compatibility requirement for that version).
    • For resources with state upgrade, include StateUpgrade requirements describing each version transition and error behavior.
Show full SKILL.md (18 more words)Show less

Output format

Use this OpenSpec-oriented structure:

markdown
# `<name>` — Schema and Functional Requirements

Resource implementation: `<GO_PACKAGE_OR_DIR>`

## Purpose
...

## Schema
\`\`\`hcl
...
\`\`\`

## Requirements

### Requirement: Short name (REQ-xxx)

The resource SHALL ...

#### Scenario: ...
- GIVEN ...
- WHEN ...
- THEN ...

Reference

  • Authoring: dev-docs/high-level/openspec-requirements.md
  • Example: openspec/specs/elasticsearch-security-role/spec.md
  • Full code-path checklist and requirement categories: reference.md

© 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/existing-entity-requirements of elastic/terraform-provider-elasticstack.

  • SKILL.md
  • reference.md

Open the folder on GitHubat commit b6bbc21

Compare with similar skills

Existing Entity Requirements 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.

Existing Entity Requirements compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Existing Entity Requirements this skillelastic/terraform-provider-elasticstack210—~1.1kAutomated safety check: PassApache-2.0
Kibana Alerting Rulesaspectrr/deer405—~1.8kAutomated safety check: PassMIT
Kibana Connectorsaspectrr/deer405—~2kAutomated safety check: PassMIT
Review Docshashicorp/terraform-provider-aws11k—~1.3kAutomated safety check: PassMPL-2.0
Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit2606 repos~1.1kAutomated safety check: NotesCustom licence
Cloudflarehodgef/apiker1277 repos~2.2kAutomated safety check: PassMIT

Similar skills

  • Kibana Alerting Rules

    aspectrr/deer

    Create and manage Kibana alerting rules via REST API or Terraform.

    405 GitHub stars~1.8k tokensUpdated 5 mo ago
    DevOps & CloudAuto-check passed

  • Kibana Connectors

    aspectrr/deer

    Create and manage Kibana connectors for Slack, PagerDuty, Jira, webhooks, and more via REST API or Terraform.

    405 GitHub stars~2k tokensUpdated 5 mo ago
    Backend & APIsAuto-check passed

  • Review Docs

    hashicorp/terraform-provider-aws

    Official

    Review a Terraform AWS Provider PR's end-user documentation (website/docs//.markdown): whether docs are needed, description openings, argument/attribute style, section structure, tags wording, code…

    11k GitHub stars~1.3k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Senior DevOps Toolkit

    maslennikov-ig/claude-code-orchestrator-kit

    Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…

    260 GitHub starsUsed in 6 repos~1.1k tokens
    DevOps & CloudAuto-check: notes

  • Cloudflare

    hodgef/apiker

    Comprehensive Cloudflare platform skill covering Workers, Pages, storage (KV, D1, R2), AI (Workers AI, Vectorize, Agents SDK), feature flags (Flagship), networking (Tunnel, Spectrum), security (WAF…

    127 GitHub starsUsed in 7 repos~2.2k tokens
    DevOps & CloudAuto-check passed

  • Terravision Cloud Diagrams

    patrickchugh/terravision

    Draw cloud architecture diagrams for AWS, Azure or GCP with the official provider icon sets, using TerraVision.

    1.6k GitHub stars~5.6k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes

More from elastic/terraform-provider-elasticstack

All 21 skills in this repo

  • Openspec Explore

    elastic/terraform-provider-elasticstack

    Official

    Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements.

    210 GitHub starsUsed in 87 repos~4.6k tokens
    Auto-check passed

  • Openspec Apply Change

    elastic/terraform-provider-elasticstack

    Official

    Implement tasks from an OpenSpec change. An agent skill from elastic/terraform-provider-elasticstack.

    210 GitHub starsUsed in 92 repos~2.1k tokens
    Auto-check passed

  • Openspec Archive Change

    elastic/terraform-provider-elasticstack

    Official

    Archive a completed change in the experimental workflow. An agent skill from elastic/terraform-provider-elasticstack.

    210 GitHub starsUsed in 86 repos~2.7k tokens
    Auto-check passed

  • PR Monitoring Loop

    elastic/terraform-provider-elasticstack

    Official

    Monitor GitHub pull requests through a subagent-based loop that watches CI checks, review comments, PR comments, review state, merge conflicts, and branch freshness.

    210 GitHub stars~4.1k tokensUpdated today
    Auto-check passed

  • Openspec Plus Proposal

    elastic/terraform-provider-elasticstack

    Official

    MANDATORY skill that activates whenever the OpenSpec proposal phase begins.

    210 GitHub starsUsed in 1 repo~3.2k tokens
    Auto-check passed

  • Openspec Continue Change

    elastic/terraform-provider-elasticstack

    Official

    Continue working on an OpenSpec change by creating the next artifact.

    210 GitHub starsUsed in 31 repos~1.7k tokens
    Auto-check passed

Works with

Categories

Questions about Existing Entity Requirements

What does Existing Entity Requirements do?

Examines an existing Terraform resource or data source implementation and produces an OpenSpec requirements document under openspec/specs/. Existing Entity Requirements is an agent skill from elastic/terraform-provider-elasticstack, published by the product's own GitHub organization. Examines an existing Terraform resource or data source implementation and produces an OpenSpec requirements document under openspec/specs/.

When should I use Existing Entity Requirements?

Existing Entity Requirements fits situations like: the user asks to document requirements for a Terraform entity; capture behavior from code; write a requirements doc for a resource/data source.

How do I install Existing Entity Requirements in Claude Code?

Run `npx skills add elastic/terraform-provider-elasticstack --skill existing-entity-requirements -a claude-code`. Or copy the skill folder (.agents/skills/existing-entity-requirements in elastic/terraform-provider-elasticstack) into .claude/skills/existing-entity-requirements in your project. Claude Code loads it when a task matches its description.

How do I install Existing Entity Requirements in Codex?

Run `npx skills add elastic/terraform-provider-elasticstack --skill existing-entity-requirements -a codex`. Or copy the skill folder (.agents/skills/existing-entity-requirements in elastic/terraform-provider-elasticstack) into .agents/skills/existing-entity-requirements in your project. Codex loads it when a task matches its description.

Can I use Existing Entity Requirements 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 existing-entity-requirements -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/existing-entity-requirements, .gemini/skills/existing-entity-requirements, .github/skills/existing-entity-requirements and .opencode/skills/existing-entity-requirements in your project.

What does Existing Entity Requirements need to run?

SKILL.md names no scripts, command-line tools or credentials: Existing Entity Requirements is instructions for the agent only.

Does Existing Entity Requirements 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 Existing Entity Requirements 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 Existing Entity Requirements use?

Existing Entity Requirements 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 Existing Entity Requirements use?

About 1.1k tokens (SKILL.md is roughly 4.4k 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 Existing Entity Requirements?

Skills that share tags, products or a category with Existing Entity Requirements: Kibana Alerting Rules (aspectrr/deer, 405 stars), Kibana Connectors (aspectrr/deer, 405 stars), Review Docs (hashicorp/terraform-provider-aws, 11k stars) and Senior DevOps Toolkit (maslennikov-ig/claude-code-orchestrator-kit, 260 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Existing Entity Requirements?

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 8, 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.