loom

Orchestrate Elastic loom demo builds from discovery notes and diagnostic exports.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Loom orchestrates the end-to-end assembly of Elastic loom demos by coordinating multiple specialist skills (warp-spark, warp-listen, warp-scan, weave-script, thread-qualify, thread-audit, etc.) into a cohesive pipeline that outputs ready-to-deliver artifacts from discovery notes and diagnostics.

Core Features & Use Cases

  • End-to-end orchestration across discovery, diagnostic analysis, platform audit, script generation, data modeling, deployment readiness, and post-deploy checks.
  • Leverages sub-skills as specialists to load expertise, execute stages in dependency order, and produce organized handoff artifacts.
  • Supports reference repositories and external skill integration to ensure repeatable, enterprise-grade demos across different customer contexts.

Quick Start

Provide discovery notes and optional diagnostic exports; loom will determine which stages to run and orchestrate the full pipeline to produce demo-ready artifacts.

Frequently Asked Questions about loom

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

FAQPage Schema
How do I orchestrate end-to-end Elastic demo pipelines from discovery notes?

Orchestrating Elastic demo pipelines involves coordinating multiple specialist sub-skills in dependency order to process discovery notes and diagnostic exports, producing organized, ready-to-deliver artifacts.

What is dependency-aware pipeline orchestration for staged demos?

Dependency-aware pipeline orchestration is a staged execution mechanism that determines which sub-skills to run in order, tracking inventory and producing explicit handoff artifacts at each stage.

Do I need diagnostic exports to run a full discovery-to-deployment demo build?

Diagnostic exports are optional inputs for the full discovery-to-deployment build, but providing them enables the pipeline to perform deeper diagnostic analysis and platform audit stages.

Can I use reference repositories to ensure repeatable enterprise-grade Elastic demos?

Reference repositories can be used with this orchestration pipeline to ensure repeatable, enterprise-grade demos across different customer contexts by loading external skill integrations.

What's the best way to coordinate multiple specialist skills for a cohesive demo pipeline?

The best way to coordinate specialist skills is using an orchestration pipeline that executes sub-skills in dependency order, ensuring stage-by-stage outputs, inventory tracking, and controlled deployment readiness.

Why does my staged demo pipeline require explicit handoff artifacts between stages?

Staged demo pipelines require explicit handoff artifacts to ensure controlled deployment readiness, maintain inventory tracking, and provide organized inputs for subsequent dependency-aware sub-skill execution.