Document Skills

# 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 interpretat...

# 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 Daytona 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 ...