coquill-renderer

Render CoQuill document templates into docx, html, or markdown outputs.

46|25|Updated May 7, 2026
One-click install
npx skills add https://github.com/LegalQuants/lq-skills --skill coquill-renderer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coquill-renderer
Source: https://github.com/LegalQuants/lq-skills/tree/main/skills/coquill/renderer
Command: npx skills add https://github.com/LegalQuants/lq-skills --skill coquill-renderer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill fills document templates with provided variables and produces a complete, render-ready document, while validating that no placeholders or template control tags remain.

Core Features & Use Cases

  • Template rendering to multiple formats: Render DOCX templates (via docxtpl), HTML templates, or Markdown templates (via Jinja2).
  • Structural completion validation: Detects unfilled {{ variables }} and any unprocessed {% ... %} control tags and reports validation status.
  • Optional PDF generation with fallbacks: For DOCX, attempts PDF conversion via docx2pdf or headless LibreOffice; for HTML/Markdown, uses WeasyPrint; PDF failures are soft-fail.

Quick Start

Ask the CoQuill orchestrator to render a template by sending the template path, variable dictionary, output directory, requested format, and draft_notice, then return the produced files and validation results.

Frequently Asked Questions about coquill-renderer

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

FAQPage Schema
How do I render Jinja2 templates into DOCX or HTML documents with variable validation?

To render Jinja2 templates into DOCX or HTML, use a variable dictionary to fill placeholders and generate completed outputs. The process validates that no unfilled variables or unprocessed control tags remain, ensuring structural completion for deterministic document-generation workflows.

What is the best way to convert DOCX templates to PDF when using docxtpl?

To convert DOCX templates to PDF, the rendering process attempts conversion via docx2pdf or headless LibreOffice after filling the template. PDF generation operates as a soft-fail, meaning rendering still succeeds and returns validation results even if the PDF conversion fails.

Can I generate PDFs from DOCX or HTML templates using Jinja2 variables?

Yes, you can generate PDFs from DOCX or HTML templates using Jinja2 variables. For DOCX, it attempts PDF conversion via docx2pdf or headless LibreOffice; for HTML and Markdown, it uses WeasyPrint. PDF generation is a soft-fail process, so rendering still succeeds even if PDF conversion fails.

How do I validate that no Jinja2 control tags or placeholders remain unfilled in document templates?

To validate that no Jinja2 control tags or placeholders remain unfilled, the template rendering process detects any leftover variables or unprocessed tags after applying the variable dictionary. It reports a validation status to guarantee the structural completion of the bounded job.

Does template rendering support Markdown and HTML outputs alongside DOCX?

Template rendering supports Markdown, HTML, and DOCX outputs. It processes Jinja2-style placeholders and control tags for Markdown and HTML, while using docxtpl for DOCX files, ensuring deterministic structural completion across all supported document formats.

What happens when PDF generation fails during document rendering?

When PDF generation fails during document rendering, the process executes a soft-fail. The primary DOCX, HTML, or Markdown output is still produced and returned alongside validation results, allowing the orchestrated workflow to continue despite the PDF conversion error.