Generate CoQuill v2 manifest.yaml from docx, html, or markdown templates.
npx skills add https://github.com/LegalQuants/lq-skills --skill coquill-analyzer
Please help me install this Agent Skill. Skill: coquill-analyzer Source: https://github.com/LegalQuants/lq-skills/tree/main/skills/coquill/analyzer Command: npx skills add https://github.com/LegalQuants/lq-skills --skill coquill-analyzer
This Skill removes the guesswork from turning CoQuill v2 contract template files into a structured manifest by automatically extracting template variables, control structures, and loop-scoped fields.
{% if %}, {% else %}, {% endif %}, {% for %}, and {{ variable }} tags and classifies variables by scope (top-level, conditional branches, loop sub-variables).config.yaml variable overrides into the extracted manifest while preserving template-derived structure.manifest.yaml consumed by the CoQuill orchestrator, including dependencies and optional meta/groups/validation.Ask the Orchestrator to run the coquill orchestrator analyzer on your template directory so it generates <template_dir>/manifest.yaml.
High-intent search queries and answers about installing and using this skill.
To generate a manifest from template files, the analyzer parses docx, html, and markdown formats to extract variables, conditionals, and loops, writing the structured output into a manifest.yaml file. It validates file selection and infers variable types.
Template variable inference detects tags like `{% if %}` and `{{ variable }}`, classifying variables by scope into top-level, conditional branches, or loop sub-variables. It infers basic types such as boolean, text, date, number, email, and phone from variable names.
Yes, you can override inferred template variables using a config.yaml file. The analyzer merges config.yaml overrides into the extracted manifest while preserving the template-derived structure, ensuring authoritative configurations take precedence over inferred types.
Extracting variables from a docx template involves parsing the document's XML structure with a fallback mechanism to detect control structures like `{% for %}` loops and `{{ variable }}` tags. The analyzer classifies these elements by scope to build a dependency graph.
Yes, manifest generation supports loop-scoped fields and dependency graphs. The analyzer detects `{% for %}` tags to classify loop sub-variables and writes a v2 manifest.yaml that includes dependencies and optional meta, groups, and validation.
You need a v2 manifest.yaml when a downstream renderer requires a machine-readable contract template schema and dependency graph. It provides a structured contract by extracting variables and control structures, enabling orchestrated rendering workflows.
houfuRender DOCX, HTML, and Markdown templates with variable data and validate placeholders.
BellaBeGenerate runnable application artifacts from manifests and targets.
maxvaegaParse and validate JSON data against schemas and JSONPath queries.
pelchersParse academic PDFs, DOCX, Markdown, HTML, and web pages into structured JSON metadata and outlines.