weave-model

Generate Elasticsearch data artifacts from a demo script and discovery profile.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reads a demo script and discovery profile to generate all Elasticsearch data artifacts required to build a fully deployable Elastic demo, including index mappings, data stream templates, component templates, ILM policies, ingest pipelines, enrich policies, and sample data specifications. It produces a master build manifest and individual artifact files in the correct build order.

Core Features & Use Cases

  • Reads a demo script and discovery JSON to emit a complete Elasticsearch data model ready for bootstrapping.
  • Generates all required artifacts in the correct build sequence and validates prerequisites (e.g., ELSER endpoints for semantic_text when applicable).
  • Produces both machine-readable data-model JSON and a human-readable data-model Markdown document to guide engineers and SEs.
  • Applies baseline version checks (9.4+), and supports Vulcan outputs when present to accelerate artifact generation.

Quick Start

Supply a demo script and discovery JSON; weave-model will generate mappings, templates, pipelines, and a master data-model manifest in the correct build order.

Frequently Asked Questions about weave-model

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

FAQPage Schema
How do I generate Elasticsearch index mappings and ingest pipelines from a discovery profile?

To generate Elasticsearch index mappings and ingest pipelines from a discovery profile, supply the profile and a demo script to produce a complete data model. This process outputs component templates, ILM policies, and enrich policies ready for deployment.

What Elasticsearch artifacts do I need to build a deployable demo environment?

Building a deployable Elasticsearch demo environment requires index mappings, data stream templates, component templates, ILM policies, ingest pipelines, and enrich policies. A master build manifest organizes these artifacts in the correct build sequence for bootstrapping.

Can I use semantic_text with ELSER endpoints in Elasticsearch data models?

Yes, you can use semantic_text with ELSER endpoints in Elasticsearch data models. The artifact generation process validates prerequisite ELSER endpoints to ensure Elasticsearch-native configurations align correctly when semantic_text is applicable.

Does Elasticsearch data model generation require a specific baseline version?

Elasticsearch data model generation requires a baseline version of 9.4 or higher. The generation process applies baseline version checks to ensure compatibility and supports Vulcan outputs when present to accelerate artifact creation.

How do I create a master build manifest for Elasticsearch data artifacts?

To create a master build manifest for Elasticsearch data artifacts, input a demo script and discovery JSON. The process emits machine-readable data-model JSON and human-readable Markdown, detailing mappings and pipelines in the correct build order.

What is the best way to bootstrap Elasticsearch data streams and component templates?

The best way to bootstrap Elasticsearch data streams and component templates is by using a discovery profile and demo script to auto-generate the required artifacts. This approach ensures all configurations align with Elasticsearch-native settings and ELSER where applicable.