weave-query

Generate validated ES|QL queries and synthetic datasets via Vulcan integration.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Loom projects often struggle to produce production-ready ES|QL queries, synthetic datasets, and integration-grounded data inputs that align with the weave-model. This skill bridges loom's pipeline with elastic/vulcan to generate validated, parameterized ES|QL queries, LLM-produced synthetic datasets, EPR-grounded integration data, and tested RAG pipelines. Vulcan handles the bottom-up data + query layer; loom consumes its outputs in weave-model to replace hand-authored seed data and ES|QL.

Core Features & Use Cases

  • Generates parameterized ES|QL queries and validated data fixtures that feed weave-model.
  • Produces synthetic datasets and integration-grounded artifacts for Fleet/Beats scenarios.
  • Runs before weave-model to ensure data modeling has ready, tested inputs for dashboards and ML configs.

Quick Start

Invoke weave-query before weave-model to generate Vulcan-driven ES|QL queries and synthetic datasets for your current demo script.

Frequently Asked Questions about weave-query

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

FAQPage Schema
How do I generate production-ready ES|QL queries for Elastic search scenarios?

Generating production-ready ES|QL queries requires coordinating with Vulcan and a running Elastic cluster to produce validated, parameterized outputs. This process creates the vulcan-queries contract for downstream data modeling and RAG pipelines.

What is the best way to create synthetic datasets for Fleet and Beats integration scenarios?

Creating synthetic datasets for Fleet and Beats scenarios involves using Vulcan integration to produce EPR-grounded data artifacts. These outputs replace hand-authored seed data to provide tested inputs for dashboards and ML configurations.

Do I need a running Elastic cluster to use Vulcan for ES|QL query generation?

A running Elastic cluster is not strictly required for ES|QL query generation with Vulcan, as you can skip indexing. However, an active cluster is necessary if you want to validate queries and test RAG pipelines against actual data.

How does Vulcan integrate with weave-model to build RAG pipelines?

Vulcan integrates with weave-model by handling the bottom-up data and query layer, producing a vulcan-queries contract. Loom consumes these validated outputs in weave-model to build tested RAG pipelines and replace manually authored ES|QL.

What are the limitations of using Vulcan for ES|QL query generation without an Elastic cluster?

Without a running Elastic cluster, you must skip indexing, meaning you cannot validate the generated ES|QL queries or test RAG pipelines against live data. You also require a local Vulcan installation at the ../vulcan path for the integration to function.