PDF Report Generation
When to Activate
Trigger ONLY when the user explicitly says one of:
- "generate PDF", "create PDF", "PDF document", "PDF report", "export as PDF", "save as document"
Do NOT trigger for: "document", "report", "summary", "briefing", or "memo" alone. These should produce markdown text output.
Workflow
Prepare markdown content with proper structure:
- Use
## for main sections, ### for subsections
- Use markdown tables for data presentation
- Include clear section headers
- Add source citations throughout
Determine audience:
external_client — Client-facing reports (simplified language, no internal references)
internal — Investment committee memos, research reports (full detail, technical language)
Call pdf_generator with:
markdown_content: Complete formatted markdown
report_title: Descriptive title (e.g., "Q4 2024 Quarterly Client Report", "NVIDIA Investment Memo")
document_audience: One of external_client or internal
After calling pdf_generator, ALWAYS include the returned download link verbatim in your response so the user can click it to download the PDF.
Error Handling
If PDF generation fails:
- Present the full content as formatted markdown inline
- Note: "PDF generation encountered an issue. Here is the full content in text format."
- Do not retry automatically
Formatting Best Practices
- Tables: Use for performance summaries, financial data, scenario analysis, risk matrices
- Headers: Maximum 3 levels deep (##, ###, ####)
- Lists: Use bullet points for qualitative analysis, numbered lists for sequential steps
- Emphasis: Bold for key metrics and findings, italic for caveats and limitations
Stopping Points
- This is a utility skill invoked at the end of a workflow. Stopping points are inherited from the calling workflow.
- If the user has not explicitly confirmed their request for PDF output, confirm before calling pdf_generator.
Output
A downloadable PDF link returned by pdf_generator, included verbatim in the response.
1---2name: pdf-report-generation3description: Use this skill when the user explicitly requests a PDF document, file export, or downloadable report. Trigger on phrases like "generate PDF", "create PDF", "export as PDF", or "save as document". Do NOT trigger for general requests like "report", "summary", or "document" alone — those should produce markdown text output.4---56# PDF Report Generation78## When to Activate910Trigger ONLY when the user explicitly says one of:11- "generate PDF", "create PDF", "PDF document", "PDF report", "export as PDF", "save as document"1213Do NOT trigger for: "document", "report", "summary", "briefing", or "memo" alone. These should produce markdown text output.1415## Workflow16171. Prepare markdown content with proper structure:18 - Use `##` for main sections, `###` for subsections19 - Use markdown tables for data presentation20 - Include clear section headers21 - Add source citations throughout22232. Determine audience:24 - `external_client` — Client-facing reports (simplified language, no internal references)25 - `internal` — Investment committee memos, research reports (full detail, technical language)26273. Call `pdf_generator` with:28 - `markdown_content`: Complete formatted markdown29 - `report_title`: Descriptive title (e.g., "Q4 2024 Quarterly Client Report", "NVIDIA Investment Memo")30 - `document_audience`: One of `external_client` or `internal`31324. After calling pdf_generator, ALWAYS include the returned download link verbatim in your response so the user can click it to download the PDF.3334## Error Handling3536If PDF generation fails:37- Present the full content as formatted markdown inline38- Note: "PDF generation encountered an issue. Here is the full content in text format."39- Do not retry automatically4041## Formatting Best Practices4243- Tables: Use for performance summaries, financial data, scenario analysis, risk matrices44- Headers: Maximum 3 levels deep (##, ###, ####)45- Lists: Use bullet points for qualitative analysis, numbered lists for sequential steps46- Emphasis: Bold for key metrics and findings, italic for caveats and limitations4748## Stopping Points4950- This is a utility skill invoked at the end of a workflow. Stopping points are inherited from the calling workflow.51- If the user has not explicitly confirmed their request for PDF output, confirm before calling pdf_generator.5253## Output5455A downloadable PDF link returned by `pdf_generator`, included verbatim in the response.