batch-observing

Parallelize multi-user DM ingestion by spawning per-user workers running the /ingest-dm pipeline.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/0xHoneyJar/construct-observer --skill batch-observing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: batch-observing
Source: https://github.com/0xHoneyJar/construct-observer/tree/main/skills/batch-observing
Command: npx skills add https://github.com/0xHoneyJar/construct-observer --skill batch-observing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Batch observing solves the bottleneck of sequential multi-user DM processing by parallelizing ingestion and canvas creation, dramatically speeding up the formation of cross-user insights.

Core Features & Use Cases

  • Leader spawns one worker per input DM export, each running the /ingest-dm pipeline for its user
  • Workers generate per-user canvases and store them under grimoires/observer/canvas
  • Leader monitors progress, handles partial failures, and runs cross-canvas pattern detection after completion
  • Supports error handling, rate-limiting awareness, and optional append-only updates for existing canvases

Quick Start

Use the /batch-observe command with a list of DM export paths to start parallel canvas ingestion.

Frequently Asked Questions about batch-observing

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

FAQPage Schema
How do I process multi-user DM exports in parallel to speed up canvas creation?▼

Parallel multi-user DM processing accelerates canvas creation by spawning per-user workers that run the ingest-dm pipeline simultaneously. A leader agent monitors progress, handles partial failures, and generates cross-canvas insights after ingestion.

What is cross-canvas pattern detection and when do I need it for DM ingestion?▼

Cross-canvas pattern detection analyzes multiple per-user canvases to identify shared insights across user bases. You need it after batch processing sizable DM exports or onboarding large groups, ensuring cross-user patterns are synthesized post-ingestion.

How do I handle partial failures during batch DM ingestion for multiple users?▼

Handling partial failures during batch DM ingestion involves a leader agent that monitors worker progress and manages errors. It supports rate-limiting awareness and optional append-only updates for existing canvases, ensuring ingestion completes despite individual worker issues.

Does batch DM ingestion work for onboarding large groups of new users?▼

Batch DM ingestion is applicable when onboarding five or more new users. The leader agent spawns dedicated workers for each user, generating per-user canvases stored under grimoires/observer/canvas to streamline the onboarding workflow.

What is the best way to orchestrate parallel workers for DM canvas generation?▼

Orchestrating parallel workers for DM canvas generation requires a leader agent to spawn one worker per input DM export. Each worker independently runs the ingest-dm pipeline to process user data and generate individual canvases concurrently.