content-distribution

Render, merge, zip, upload, and share Declassified Case outputs via Drive.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill coordinates the final phase of Declassified Cases by rendering, merging, packaging, and distributing outputs to designated destinations, automating repetitive distribution tasks and ensuring consistent delivery.

Core Features & Use Cases

  • Render PDFs: verify and render per-document outputs as HTML and PDF.
  • Envelope Merging: merge per-envelope PDFs in sequence.
  • Packaging & Distribution: create final ZIPs, include premium audio if available, upload to Google Drive, and share links.
  • Use Case: When closing a case, run the pipeline to produce a ready-to-distribute package for external recipients.

Quick Start

Run the content-distribution workflow to package the final case outputs from cases/exports/<CASE_SLUG>/ into final/ and ZIP, then upload the ZIP to Drive.

Frequently Asked Questions about content-distribution

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

FAQPage Schema
How do I automate packaging and distributing case files to Google Drive?

Automating case file packaging and distribution to Google Drive requires orchestrating PDF rendering, envelope merging, ZIP creation, and upload processes into a single pipeline. This workflow handles rendering checks, sequences per-envelope PDFs, creates final ZIPs, and uploads them to Drive for link sharing.

What is the process for merging multiple PDF envelopes into a single package?

Merging multiple PDF envelopes into a single package involves sequencing per-envelope PDFs after verifying individual document renders. The workflow validates HTML and PDF outputs, merges documents in exact sequence, and bundles them with premium audio into a final ZIP archive for distribution.

Can I include audio files when zipping case outputs for distribution?

Including audio files when zipping case outputs is supported during the final packaging phase. The workflow detects available premium audio assets and automatically bundles them into the final ZIP file alongside merged PDFs before uploading to Drive and generating share links.

Does this case management distribution workflow require external dependencies?

This case management distribution workflow requires no external dependencies or components to function. It autonomously handles end-to-end manifest-driven case delivery tasks including rendering verification, envelope sequencing, ZIP creation, Drive uploads, and status reporting.

What's the best way to automate final case delivery and status reporting?

Automating final case delivery and status reporting is best achieved through a manifest-driven pipeline that orchestrates rendering, merging, packaging, and uploading. This approach coordinates ZIP creation, Google Drive uploads, link sharing, and automated status updates as part of end-to-end case workflows.

When should I not use automated ZIP packaging for case distribution?

Automated ZIP packaging for case distribution is not suitable for cases lacking final outputs in the cases/exports directory, as the workflow depends on existing rendered assets. It is specifically designed for end-to-end case workflows requiring multiple envelope merges and Drive uploads.