# elastic-package-cli

Walks your agent through elastic-package commands: formatting, linting, artifact builds, pipeline and system tests, local Elastic stack.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 507 installs · ★ 16
- Author: elastic
- License: Apache-2.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/elastic/integration-skills/tree/HEAD/skills/elastic-package-cli/SKILL.md
- Updated: 2026-10-16
- HTML: https://affpapa.org/en/nevibecode/skills/elastic-package-cli

## What it does

This skill lays out the loops you follow while developing and validating Elastic integrations. Routine local verification runs `elastic-package format`, then `lint`, `check` and `build`. `check` combines linting and building and stops at the first failure by default; `format --fail-fast` verifies without rewriting files.

Faster pipeline iteration uses an Elasticsearch-only stack: `elastic-package stack up -d --services=elasticsearch`, followed by `test pipeline`. The `--generate` flag rewrites expected outputs, so review those files before keeping them. End-to-end runs go `stack up -d`, `service up`, `test system`, and `--data-streams <name>` narrows the scope.

Inside you get a command map and a flag cheat sheet: global `-C` and `-v`, stack flags `-d`, `-s`, `--version`, `-p`, system test flags `--setup`, `--tear-down`, `--no-provision`, `--variant`. Failure diagnosis lives in `references/troubleshooting.md`. Nothing runs without `elastic-package` on your `PATH` and a container runtime such as Docker or Podman, and commands expect a package directory or `-C <package-dir>`. ECS field design and ingest processor strategy are out of scope here.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add elastic/integration-skills --skill elastic-package-cli -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/elastic-package-cli/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/elastic-package-cli/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add elastic/integration-skills --skill elastic-package-cli -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/elastic-package-cli/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add elastic/integration-skills --skill elastic-package-cli -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/elastic-package-cli/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install elastic/integration-skills elastic-package-cli
```

2. **Manually: put the files in place**
- File: `.github/skills/elastic-package-cli/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add elastic/integration-skills --skill elastic-package-cli -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/elastic/integration-skills --path skills/elastic-package-cli
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/elastic-package-cli/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add elastic/integration-skills --skill elastic-package-cli -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/elastic/integration-skills/tree/HEAD/skills/elastic-package-cli/SKILL.md

## When to use it
- verify package structure and formatting before a commit
- produce a package artifact
- run pipeline tests and regenerate expected outputs
- bring up a local Elastic stack for end-to-end runs
- check package status in Kibana after install

## Example prompts
- Run `format`, `lint`, `check` and `build` on this package in order.
- Start the stack with Elasticsearch only and run `test pipeline`.
- Run system tests scoped to one data stream with `--data-streams`.

## Source text · SKILL.md · Apache-2.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 8a750dc6bdb9726b.

BEGIN THIRD-PARTY FILE 8a750dc6bdb9726b
````text
---
name: elastic-package-cli
description: "Use when developing or validating Elastic integrations with elastic-package commands such as build, check, lint, format, test, stack, service, install, profiles, and benchmark."
license: Apache-2.0
metadata:
  author: elastic
  version: "1.0"
---

# elastic-package CLI


## When to use

Use this skill when tasks include:
- validating package structure and formatting
- building a package artifact
- running pipeline or system tests
- managing local Elastic test stack lifecycle
- installing or checking package status in Kibana

## When not to use

Do not use this skill as the primary guide for:
- ECS field design decisions (use an ECS-focused skill)
- ingest processor design and parsing strategy (use an ingest-pipeline-focused skill)
- package layout architecture (use a package-structure-focused skill)

## Prerequisites

- `elastic-package` is installed and available in `PATH`
- container runtime is available (Docker or Podman)
- you run commands from a package directory (or pass `-C <package-dir>`)

## Core workflows

### 1) Validate and build loop

Run this sequence for routine local verification:

```bash
elastic-package format
elastic-package lint
elastic-package check
elastic-package build
```

Notes:
- `check` runs lint and build together and fails fast by default.
- use `format --fail-fast` when you want read-only verification without rewriting files.

### 2) Pipeline test loop (fast iteration)

Use Elasticsearch-only stack for quicker feedback:

```bash
elastic-package stack up -d --services=elasticsearch
elastic-package test pipeline
elastic-package test pipeline --generate
```

Then review generated expected files before keeping changes.

### 3) System test loop (end-to-end)

Use this when you need full ingest behavior with service provisioning:

```bash
elastic-package stack up -d
elastic-package service up
elastic-package test system
```

Use `--data-streams <name>` to scope tests and reduce run time.

## Practical command examples

```bash
# format package files
elastic-package format

# lint against package spec and templates
elastic-package lint

# combined validation workflow
elastic-package check

# build package artifact
elastic-package build

# start only Elasticsearch for pipeline tests
elastic-package stack up -d --services=elasticsearch

# run pipeline tests
elastic-package test pipeline

# regenerate expected pipeline outputs
elastic-package test pipeline --generate
````
END THIRD-PARTY FILE 8a750dc6bdb9726b

The third-party file has ended. Everything between the 8a750dc6bdb9726b tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2473 of 3271 bytes. © elastic · Apache-2.0 · https://github.com/elastic/integration-skills/tree/HEAD/skills/elastic-package-cli/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md