production-engine

Generate per-document _content.md narratives from envelope data.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/pr3t3l/openclaw-config --skill production-engine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: production-engine
Source: https://github.com/pr3t3l/openclaw-config/tree/main/workspace/skills/production-engine
Command: npx skills add https://github.com/pr3t3l/openclaw-config --skill production-engine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Production Engine generates case document narratives for Declassified Cases and outputs a _content.md file for each document in an envelope, enabling rapid, consistent publication-ready narratives without duplicative manual writing.

Core Features & Use Cases

  • Automatically draft narrative content per document in an envelope
  • Produces _content.md files for each document to feed downstream assembly
  • Spawned once per envelope by the orchestrator to ensure consistency across documents

Quick Start

Ingest an envelope and let the engine produce the _content.md for every document in the batch.

Frequently Asked Questions about production-engine

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

FAQPage Schema
How do I automate narrative generation for case document envelopes?

Automating narrative generation for case document envelopes involves transforming envelope data into per-document narrative content files, producing one _content.md file for each document to ensure consistent publication-ready text.

What is the best way to generate publication-ready content from envelope data?

The best way to generate publication-ready content from envelope data is using an engine that processes all document types within an envelope, automatically drafting a _content.md file for each document without requiring manual writing.

How does content assembly work for declassified case documents?

Content assembly for declassified case documents works by coordinating with an orchestrator that spawns the engine once per envelope, ensuring strict adherence to case data sources and formatting rules to produce accurate _content.md files.

Can I generate narrative content without creating placeholder text or direct JSON template variables?

Generating narrative content without placeholder text or direct JSON template variables requires strict adherence to case data sources and formatting rules, ensuring only data-driven narrative output is produced for each document.

Are there limitations when processing multiple document types within a single envelope?

A limitation when processing multiple document types within a single envelope is that the engine must be spawned once per envelope by the orchestrator to maintain consistency and ensure exactly one _content.md file is generated per document.

Do I need an orchestrator to produce content files for envelope processing?

An orchestrator is required to produce content files for envelope processing because it spawns the engine once per envelope, coordinating the creation of individual _content.md files to ensure consistency across all document types.