Automates Elastic Fleet integration package registration and configuration for loom engagements.
npx skills add https://github.com/ajmeyers42/loom --skill weave-fleet
Please help me install this Agent Skill. Skill: weave-fleet Source: https://github.com/ajmeyers42/loom/tree/main/skills/weave-fleet Command: npx skills add https://github.com/ajmeyers42/loom --skill weave-fleet
Resolves, configures, and registers Elastic Fleet integration packages (EPM) for a loom engagement. Reads discovery and data model to determine which packages to install, performs an asset catalog review to surface use-as-is / clone-and-modify / storyline-enhancement opportunities, generates deploy/{slug}-integrations-manifest.json and demo/{slug}-integration-assets.md, and injects an idempotent install step into bootstrap.py. Supports ECH (full Fleet) and Serverless (asset-only mode).
ALWAYS use this skill when the data model includes any logs-* or metrics-* data streams. This skill decides whether each stream should be backed by a real integration package (Path A) or managed-template fallback naming (Path B). Also trigger when the SA says "install the kubernetes integration", "use Fleet for log collection", "EPM package install", "I want the out-of-the-box dashboards", "set up the integration", or "install integration packages for the demo".
High-intent search queries and answers about installing and using this skill.
Automate Elastic Fleet integration package installation by deriving package selections from discovery data models and generating idempotent deploy manifests. The process registers EPM packages end-to-end, injecting bootstrap steps and creating an asset catalog guide.
Use Fleet integration packages when your data model includes logs-* or metrics-* data streams and you want out-of-the-box dashboards. The process evaluates each stream to decide between real EPM package backing or managed-template fallback naming.
Yes, Elastic Fleet integration supports both ECH full Fleet mode and Serverless asset-only mode. The automation enforces support for both deployments, adapting package registration and configuration logic to fit the specific environment.
An Elastic Fleet integration assets catalog surfaces use-as-is, clone-and-modify, and storyline-enhancement opportunities. It is generated by reviewing resolved EPM packages against discovery data, producing a markdown guide for demo engagements.
Make EPM package bootstrapping idempotent by injecting an automated install step into bootstrap.py. This ensures repeated demo deployments resolve, configure, and register Fleet integration packages consistently without manual reconfiguration.
Yes, you can generate deploy manifests for Elastic Fleet directly from a data model. The automation reads discovery inputs to determine package selections and outputs a deploy integrations manifest JSON file for the engagement.
tbroadleyExtract samples, messages, events, and metrics from Inspect AI .eval logs.
skaile-aiDiscover and deploy AI assets from the ai-assets catalog via the Skaile CLI.
patrykkopycinskiConfigure Elastic Agent to collect logs, metrics, and security data via Fleet or standalone enrollment.
kvm9-devInstall and remove language runtimes, packages, and Nix system dependencies.
