wind-pulse

Check Elastic demo environment health via Elasticsearch and Kibana REST APIs.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/ajmeyers42/loom --skill wind-pulse
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wind-pulse
Source: https://github.com/ajmeyers42/loom/tree/main/skills/wind-pulse
Command: npx skills add https://github.com/ajmeyers42/loom --skill wind-pulse

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Checks the live health and readiness of a deployed Elastic demo environment. Reads credentials from the engagement's .env file, queries Elasticsearch and Kibana directly, and produces a compact terminal status report covering cluster health, index doc counts, ML job state, ELSER endpoint responsiveness, every saved object in engagement NDJSON (especially dashboards), tagged SLOs, Agent Builder, optional workflows, and anomaly injection readiness. Runs in under 60 seconds.

Core Features & Use Cases

  • Real-time health pulse for Elastic demo environments, validating end-to-end readiness.
  • Verifies indices and data-model integrity, saved objects, SLO tagging, and optional assets.
  • Produces a concise terminal status report with actionable remediation guidance for failures.

Quick Start

Run the wind_pulse script in the engagement workspace to generate a concise pre-demo health status.

Frequently Asked Questions about wind-pulse

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

FAQPage Schema
How do I check the health and readiness of an Elastic demo environment?

Check Elastic demo environment health by running the wind_pulse script in your engagement workspace. It queries Elasticsearch and Kibana REST APIs to report cluster state, index counts, ML jobs, and saved objects in under 60 seconds.

What does an Elasticsearch cluster health check cover for deployed demo environments?

An Elasticsearch cluster health check covers cluster status, index document counts, ML job states, ELSER endpoint responsiveness, and Kibana saved objects. It validates end-to-end demo readiness and provides remediation guidance for failures.

Do I need a specific configuration file to verify Kibana saved objects and SLO tagging?

Yes, you need a valid engagement .env file containing your credentials. The script reads this file to authenticate with Elasticsearch and Kibana REST APIs and verify saved objects, SLO tagging, and Agent Builder presence.

How do I validate ELSER endpoint responsiveness and ML job state in Elasticsearch?

Validate ELSER endpoint responsiveness and ML job state by executing a health pulse script that directly queries Elasticsearch REST APIs. It reports endpoint status and job states in a compact terminal summary within 60 seconds.

How long does it take to verify Elastic demo environment readiness before a presentation?

Verifying Elastic demo environment readiness takes under 60 seconds. The script produces a concise terminal status report covering cluster health, data-model integrity, dashboards, and anomaly injection readiness for pre-demo validation.

Why is my Elastic demo environment health check failing to detect Kibana dashboards?

A health check may fail to detect Kibana dashboards if the engagement NDJSON file is missing or incomplete. The script relies on this file to verify every saved object and provide actionable remediation guidance for failures.