package-spec

Validate Elastic integration package manifest.yml and changelog.yml against the official package-spec.

15|5|Updated May 11, 2026
One-click install
npx skills add https://github.com/elastic/integration-skills --skill package-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: package-spec
Source: https://github.com/elastic/integration-skills/tree/main/skills/package-spec
Command: npx skills add https://github.com/elastic/integration-skills --skill package-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Package-spec validation ensures Elastic integration packages conform to the official spec by enforcing manifest structures, changelog schemas, and alignment with upstream guidance.

Core Features & Use Cases

  • Validate manifest.yml fields (format_version, conditions, variables, routing rules)
  • Validate changelog.yml schema and semantic version bumps
  • Align package metadata with the upstream elastic/package-spec to prevent drift
  • Provide guidance for lint/check failures and format-version decisions

Quick Start

Review the package's manifest.yml and changelog.yml to ensure conformance with the latest package-spec.

Frequently Asked Questions about package-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate an Elastic integration package manifest against the package-spec?

To validate an Elastic integration package manifest, review fields like format_version, conditions, variables, and routing rules to ensure they align with the official package-spec. This prevents metadata drift and ensures compliance with upstream requirements.

Why does elastic-package lint fail on my changelog.yml?

elastic-package lint failures on changelog.yml often occur when the schema or semantic version bumps do not match the official package-spec. Validate your changelog structure to ensure it aligns with the expected format and upstream guidance.

What is the correct format_version to use in my Elastic package manifest?

The correct format_version for an Elastic package manifest depends on the specific package-spec version you are targeting. Check the upstream elastic-package-spec guidance to determine the appropriate version and ensure your metadata conforms.

How do I fix elastic-package check errors for routing rules and variables?

To fix elastic-package check errors for routing rules and variables, validate your manifest.yml against the official package-spec. Ensure all conditions, variables, and routing configurations strictly follow the upstream structural requirements.

Can I use this to prevent metadata drift in Elastic integration packages?

Yes, you can prevent metadata drift in Elastic integration packages by validating manifest and changelog schemas against the upstream package-spec. This ensures your package metadata remains aligned with official requirements during building or reviewing.