Document Skills

# Custom PDF Templates Use this skill when the user wants to **customize the look of PDF exports** — branding, colors, fonts, header/footer layout, title page design, or logo replacement. The `render_markdown` tool accepts `template_path` and `logo_path` parameters that let you supply a custom LaTeX template and logo stored as artifacts. --- ## 1. Quick Start 1. Write the template as an artifact. `name` is a filename, not a path — the `files/` prefix comes from `type: "file"`: ```json { "name": "my-template.latex", "type": "file", "content": "<modified template>" } ``` 2. Optionally supply a logo. `write_artifact` takes inline text only, so a binary logo has to arrive another way: point at a logo artifact you already have, or fetch it in the sandbox with `execute_shell` (anything written to `~/out` syncs back as `out/*`). This skill does not unlock `execute_shell`; learn `learn_code_execution` first if the sandbox is not already available. 3. Render, naming both...

# Default PDF LaTeX Template This is the complete default Vertesia LaTeX template that `render_markdown` uses when no `template_path` is given. Learn `learn_custom_pdf_templates` first: it explains what is safe to change, what to keep, and how to render and inspect the result. Copy the template below, modify the sections you need, and save it as an artifact. ```latex %% Vertesia Professional Report Template %% Modern, clean design for reports with charts, images, and tables %% Compatible with pandoc + xelatex/lualatex — works on macOS and Linux \documentclass[11pt,letterpaper]{article} %% ============================================================================ %% PACKAGES %% ============================================================================ \usepackage{fontspec} \usepackage{geometry} \usepackage{xcolor} \usepackage{graphicx} \usepackage{fancyhdr} \usepackage{titlesec} \PassOptionsToPackage{hyphens}{url} \usepackage{hyperref} \usepackage{enumitem} \usepackage{longtabl...

# Content Summarization Skill When summarizing content, follow these structured approaches: ## Summarization Strategies ### 1. Executive Summary (For Business Documents) - **Length**: 1-2 paragraphs - **Structure**: Key decision/recommendation → Supporting points → Action items - **Focus**: What matters to decision-makers ### 2. Abstract Style (For Technical/Academic) - **Length**: 150-300 words - **Structure**: Purpose → Methods → Key Findings → Conclusion - **Focus**: Reproducibility and scientific accuracy ### 3. TL;DR Style (For Casual/Quick Reference) - **Length**: 2-4 sentences - **Structure**: Main point → Why it matters - **Focus**: The single most important takeaway ### 4. Bullet Point Summary - **Length**: 5-10 bullet points - **Structure**: Key points in order of importance - **Focus**: Scannable, actionable items ## Best Practices 1. **Preserve key information**: Names, dates, numbers, and specific claims 2. **Maintain original meaning**: Don't introduce interp...

# Document Translation Skill Use this skill when translating documents between languages. It covers strategies for maintaining quality and consistency, especially for long documents where section-by-section translation is required. > For general document composition workflows, call `learn_content_authoring`. --- ## 1. Before You Start ### Clarify with the user 1. **Target language** — confirm the exact language and regional variant (e.g., French (France) vs. French (Canada), Brazilian Portuguese vs. European Portuguese) 2. **Tone and register** — formal (vous/usted), informal (tu/tú), technical, legal, marketing? 3. **Terminology preferences** — does the user have preferred translations for domain-specific terms? Are some terms left untranslated (brand names, product names, technical acronyms)? 4. **What to preserve** — code blocks, URLs, proper nouns, formulas typically stay untranslated 5. **Existing translation** — does a translated version of this document already exist? If ...

# Zip Archive Handling Skill Use this skill whenever you need to work with **zipfiles** stored in Vertesia (for example, zipped collections of CSVs, logs, or documents). Key behaviors: - A Vertesia **object** whose source is a `.zip` file has a **text rendition** that lists the files inside the archive (an index), not their full contents. - To actually read files from the archive, you must download the zip into the sandbox and unzip it there. --- ## 1. Understand the Text Rendition When you fetch or inspect a zip object’s text rendition (for example via `fetch_document` in analyze mode), it typically contains: - A list of file paths and names inside the archive. - Sometimes sizes and timestamps, depending on how the index was generated. Use this index to: - Identify which internal files matter (e.g. `data/metrics.csv`, `reports/summary.md`). - Decide which ones you want to extract and analyze. Do **not** treat the text rendition as the full content of each file—it is just a ...