Terminal
Terminal/Skill
Reviews and fixes an existing Elastic integration package, including pipelines, field mappings, CEL programs, manifests and changelogs.
By Elastic
Works with
npx skills add elastic/integration-skills --skill maintain-integrationUse this skill when the package already exists:
Use create-integration instead when:
create-integration → references/add-datastream-workflow.md)→ Read references/review-workflow.md fully before starting.
Run automated validation, delegate inspection to a subagent (see Dispatch convention in references/review-workflow.md) pointing it at review-integration/references/reviewer-subagent-guidance.md as its operating manual, present findings with no file changes.
→ Read references/improve-workflow.md fully before starting.
Analyze issues (from prior review or fresh reviewer run), prioritize by severity, fix directly or delegate to subagents, re-validate, and report.
For small targeted changes you can handle inline without loading a full workflow:
package-spec skill_dev/build/docs/README.md_dev/build/build.yml creation or ECS reference bumpcelfmt -s -agent -i cel.yml.hbs -o cel.yml.hbs in the stream's agent/stream/ directoryRun elastic-package lint and elastic-package check after any direct edits to confirm no regressions.
elastic-package-cli — validation and test commandspackage-spec — manifest rules, version bumps, and changelog schemaDo not load domain-specific skills (pipelines, CEL, ECS, field mappings) into your own context. Delegate to subagents that already have that knowledge.
All specialised work is delegated to the platform's generic / general-purpose subagent (Cursor: generalPurpose Task agent; Claude Code: general-purpose Task agent; or the equivalent on other platforms). Each task prompt must point the subagent at the relevant *-subagent-guidance.md file by path and instruct it to read that file (plus the skill SKILL.md it lists in "First steps") end-to-end before doing any other work. Do NOT read the guidance file yourself or paste its contents into the task prompt — that doubles its context cost. Pass only the path plus the task-specific context. The subagent will load the manual itself in its own fresh context. Full dispatch rules and per-workflow detail live in references/review-workflow.md and references/improve-workflow.md.
| Subagent guidance file | Use for |
|---|---|
review-integration/references/reviewer-subagent-guidance.md | Thorough read-only quality inspection: classifies files by domain, loads all relevant domain skills and checklists via the review-integration skill, returns severity-ranked, domain-tagged findings |
ingest-pipelines/references/builder-subagent-guidance.md | Pipeline fixes: JSE00001, error handling, processor tags, ECS categorization, field definitions, test fixtures |
cel-programs/references/builder-subagent-guidance.md | CEL fixes: program logic, cursor management, error handling, mito validation, mock API, cel.yml.hbs template, manifest var cleanup |
When delegating, provide the subagent with: package path, data stream path, specific issues to fix (paste findings), sample data if relevant, and any constraints.
All data committed must be fully anonymized — no real IPs, hostnames, emails, tokens, or org identifiers in any committed file. When fixing or adding test fixtures, mock responses, sample events, or documentation examples, verify all values are synthetic. Anonymize any real data found as part of the improvement pass.
references/review-workflow.md — read-only review workflow (phases 1–4, mandatory checklists, output format)references/improve-workflow.md — full improvement workflow (analyze → prioritize → fix → re-validate → report)