elastic-package-cli
/elastic-package-cli
Use when developing or validating Elastic integrations with elastic-package commands such as build, check, lint, format, test, stack, service, install, profiles, and benchmark.
- Author
- elastic ↗
- Repository
- integration-skills ↗
- Licence
- Apache-2.0
- Last repository change
- 24.09.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 24.09.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Use when developing or validating Elastic integrations with elastic-package commands such as build, check, lint, format, test, stack, service, install, profiles, and benchmark.
Original author 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.
How it works
- When to use
- When not to use
- Prerequisites
- Core workflows
- Practical command examples
- Key flags cheat sheet
- Quick command map
- References
SKILL.md preview
--- 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 # run end-to-end system tests elastic-package test system ``` ## Key flags cheat sheet - global: `-C, --change-directory`, `-v, --verbose` - stack: `-d, --daemon`, `-s, --services`, `--version`, `-p, --profile` - pipeline tests: `-d, --data-streams`, `-g, --generate`, `-m, --fail-on-missing` - system tests: `--setup`, `--tear-down`, `--no-provision`, `--variant` ## Quick command map - validate/build: `format`, `lint`, `check`, `build` - stack lifecycle: `stack up`, `stack status`, `stack down` - testing: `test pipeline`, `test system`, `test static`, `test asset`, `test policy`, `test script` - package lifecycle: `create`, `install`, `status`, `uninstall` - support: `service up`, `profiles`, `benchmark` ## References - Failure diagnosis and fixes: `references/troubleshooting.md`
Files in this package (2)
- SKILL.md 3 KB
- references/troubleshooting.md 5 KB
Versions
The database has no other skills named elastic-package-cli.
Database snapshot: 13.11.2026 · package version b349754c5761 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100package-spec
Package specification compliance for Elastic integration packages. Covers manifest structure (format_version, conditions, variables, var_groups, provider_permissions, routing rules), changelog schema and semantic version bumps, and alignment with the upstream… - 100create-integration
Use when creating a new Elastic integration package, scaffolding data streams, answering package layout or structure questions, or running the end-to-end integration build workflow. Covers package topology, scaffold commands, post-scaffold edits, and full orchestration of… - 100elastic-beanstalk-deployment
Use when deploying Node.js applications to AWS Elastic Beanstalk or troubleshooting deployment issues - provides dependency installation strategies, monorepo handling, and deployment best practices - 95observability-onboarding
Onboard an application into Elastic Observability with the Elastic Distribution of OpenTelemetry (EDOT): route on language and runtime, detect and replace a classic Elastic APM agent, apply the required OTLP configuration, and then verify with ES|QL that traces, metrics, and… - 100elk
Covers the Elastic Stack (ELK) 8.x/9.x for observability use cases: Elasticsearch cluster management, Elastic Agent/Fleet, Kibana, ingest pipelines, KQL/ES|QL, Index Lifecycle Management, APM agents, distributed tracing, log management, data streams, and diagnostics. Use for… - 95cloud-onboarding
Onboard an Elastic Cloud organization: configure the `elastic` CLI's Cloud context and API key, establish a default region, then invite users, assign predefined or custom Serverless project roles, and create or revoke Cloud API keys. Use when setting up Cloud authentication or…