File Generator

File Generator Skill

Use this skill when the user wants an answer delivered as a downloadable file artifact. This skill creates new workflow files; it does not edit an existing uploaded file.

Workflow

1. Decide the target file format from the user's request.
2. If the user did not specify a format, choose the most appropriate supported format:
   • Use md for reports, notes, plans, structured prose, and documentation drafts.
   • Use docx only when the user explicitly asks for Word, DOCX, an editable Word document, or Word-specific rich formatting.
   • Use xlsx when the user explicitly asks for Excel or a spreadsheet workbook. Provide valid CSV content.
   • Use pdf when the user explicitly asks for PDF or a simple read-only distribution file.
   • Use pptx when the user explicitly asks for PowerPoint, slides, a deck, or an editable presentation.
   • Use txt for plain text without formatting.
   • Use html for runnable HTML pages or previewable web documents.
   • Use svg when the user explicitly asks for an SVG/vector image file.
   • Use json for machine-readable structured data.
   • Use csv for table-like data.
3. For PDF, DOCX, PPTX, XLSX, and SVG, read the selected format reference before calling a tool. For MD, TXT, JSON, CSV, and HTML, the tool schema and this core skill are sufficient unless advanced format details are needed.
4. Use generate_file for simple exports.
5. Use generate_docx when a Word document needs headings, fonts, font sizes, alignment, spacing, page margins, page breaks, colored/bold/underlined text, or simple tables.
6. Use generate_pdf when a PDF needs richer layout, print CSS, tables, colors, page margins, page breaks, or business-report formatting.
7. Use generate_pptx when the user needs an editable static PowerPoint deck.
8. For PPTX, plan the slide layout before building the structured presentation object. Use non-overlapping boxes for titles, text, and tables. Split dense content into more slides instead of shrinking text or stacking elements.
9. For PPTX with Chinese or other dense text, treat "more text" as more slides, not denser text boxes. Keep body paragraphs short; use bullets, columns, or additional slides before exceeding the readable capacity of a box.
10. Before calling generate_pptx, self-check that each slide's readable content fits within the slide bounds, does not overlap, uses explicit x, y, w, and h when the layout matters, and avoids long unbroken lines.
11. Always create a temporary downloadable artifact. This skill does not write generated output into File Management.
12. If the user explicitly asks to save, create, upload, add, or import the generated result into File Management or the current Files page, first generate the artifact here, then use file-manager/save_file_to_management with the returned tool_file_id/file_id and destination filename.
13. For file-first requests, put the complete body directly in the generation tool call. Do not first emit the same complete body through submit_intermediate_answer. Only show the complete body in chat as well when the user explicitly asks to see both the chat text and the file.
14. After the required format reference is read and the source material is sufficient, call the selected generation tool immediately. On that tool-calling turn, leave ordinary assistant content empty; do not first draft or duplicate the report, analysis, or document body outside the tool arguments.
15. In the final answer, briefly mention the generated filename and format.
16. Do not invent, rewrite, shorten, or manually format download links. The system UI displays generated file download controls from structured artifact events.
17. A generic request for a "file" or "document" does not imply Word. When the content is structured prose and no format is specified, use generate_file with md; use txt only when formatting is unnecessary.
18. If a generation call fails schema validation, correct the selected tool's arguments and retry it at most once. Do not switch to another format-specific tool merely to bypass a missing required argument.

References

Read exactly one reference after choosing a complex target format. References for MD, TXT, JSON, CSV, and HTML are optional and should be read only when the request needs format-specific details:

Constraints

• The skill creates new files only. It does not edit existing uploaded files or preserve an existing template.
• Do not call generate_docx, generate_pdf, generate_pptx, or complex generate_file formats (XLSX or SVG) until the selected format reference has been read. MD, TXT, JSON, CSV, and HTML generation may proceed directly from the core skill and tool schema.
• generate_file accepts only its documented simple parameters. Do not invent format-specific parameters such as sheets, styles, pages, columns, headers, or metadata. XLSX output applies the default table styling documented in format-xlsx.md; the caller cannot customize those styles through generate_file.
• generate_docx accepts a structured document object. Do not stringify it, and do not pass raw Markdown or HTML as document.
• Do not call generate_docx unless the user explicitly requested Word/DOCX, an editable Word document, or Word-specific rich formatting. A generic request to "write this as a file/document" should use generate_file with md (or txt for plain text).
• generate_pdf accepts self-contained HTML and optional inline CSS. Do not pass JSON document specs.
• generate_pptx accepts a structured presentation object. Do not stringify it, and do not pass HTML or Markdown as presentation.
• PPTX readable content should not use negative coordinates. Negative x or y is only appropriate for decorative shapes that intentionally bleed off an edge.
• Generated file content must fit within the backend file size limit.
• Do not include filesystem paths in filenames.
• Do not claim a file was generated unless the tool call succeeded.
• Treat the generated tool result as authoritative. A generated file is successful only when the result includes a file identity such as file_id or tool_file_id, plus a filename/format or an equivalent artifact record.
• If the generation tool fails or returns no artifact identity, do not say the file was generated. Explain the actual failure or missing confirmation.
• Retry at most once with corrected content or arguments when the tool error is recoverable. Do not repeat the same generation call with identical arguments after a failure.
• If the user asks for advanced document features that the selected reference says are unsupported, generate the closest supported file only when that still satisfies the request.

Tool Usage

generate_file accepts:

• content: text content to write into the file.
• format: txt, md, html, json, csv, svg, docx, xlsx, or pdf.
• filename: optional display filename. The extension is added automatically.
• title: optional title used by generated HTML, XLSX, and PDF files. For XLSX, this becomes a merged title row above the table.
• lifecycle: optional temporary artifact lifecycle, persistent or temporary. Defaults to temporary.

generate_docx accepts:

• document: structured object describing the styled DOCX document.
• filename: optional display filename. The .docx extension is added automatically.
• lifecycle: optional temporary artifact lifecycle, persistent or temporary. Defaults to temporary.

generate_pdf accepts:

• html: self-contained HTML body or full HTML document.
• css: optional inline CSS appended to the document.
• filename: optional display filename. The .pdf extension is added automatically.
• title: optional title used when wrapping an HTML fragment. Visible content must be in html.
• lifecycle: optional temporary artifact lifecycle, persistent or temporary. Defaults to temporary.

generate_pptx accepts:

• presentation: structured object describing the editable static PPTX deck.
• filename: optional display filename. The .pptx extension is added automatically.
• lifecycle: optional temporary artifact lifecycle, persistent or temporary. Defaults to temporary.