8.3
/ 10
1 evaluations
2.6k Downloads
Overview
Provide structured, opinionated guidance and code patterns for generating professional PDFs from Markdown, HTML/CSS, and data (JSON/code) using common tooling like WeasyPrint, pandoc, reportlab, and fpdf2.
Key Advantages
1.Clear decision rules for selecting the right PDF generation tool based on content source (Markdown, HTML, JSON, plain text).
2.Emphasis on best practices: semantic HTML structure, print-optimized CSS, explicit page-break control, and metadata configuration.
3.Concrete, ready-to-adapt code patterns rather than vague advice, including examples for WeasyPrint and other libraries.
4.Focus on common real-world document types (reports, invoices, contracts) and how to structure them for reliable PDF output.
5.Attention to typical PDF pitfalls (fonts, image paths, page size, large images) with explicit fixes and validation steps after generation.
","Purely local, reference-only skill: no code execution, no
Use Cases
- Designing and implementing HTML/CSS templates that reliably render to PDF for reports, invoices, or contracts using WeasyPrint.
- Converting Markdown documents into styled PDFs with tables of contents and templates via pandoc.
- Building programmatic PDF generation pipelines from JSON or other structured data using reportlab or similar libraries.
- Refactoring ad-hoc HTML into semantically structured, print-optimized layouts with controlled page breaks and headers/footers.
- Creating internal documentation on PDF generation best practices for a team, including CSS for print and validation checklists.
Evaluation Scores
8.3
/ 10
Reliability
8.0
Functionality
7.5
Usability
8.8
Safety
9.5
Performance
7.0
Compatibility
8.5
Based on 1 evaluation · Latest: 3/19/2026
Download Trend
Loading...
Evaluation History (1)
8.3/103/19/2026▼
OS: linux-arm64LLM: anthropic/claude-opus-4.6
**Quick judgement:** A strong *reference* skill for PDF generation patterns and best practices, not an execution or automation tool. Best suited for agents that need to advise on how to implement PDF workflows (tool choice, HTML/CSS structure, templates) rather than generate PDFs directly.
**Strengths**
- Well-scoped: guidance only, with explicit limits (no code execution, no file or network access).
- Practical coverage of common document types and real-world issues (page breaks, fonts, images, metadata, print CSS).
- Tool-agnostic decision matrix (pandoc vs WeasyPrint vs reportlab vs fpdf2) that an agent can leverage to recommend implementation paths.
**Risks / Limitations**
- Cannot itself produce or manipulate PDFs; an external runtime or tools are always required.
- Effectiveness depends on the user (or another tool-calling agent) correctly implementing the suggested code patterns.
- Library ecosystem may evolve; some recommendations could become outdated without maintenance.
**Recommended scenarios**
- An advisory or coding-assistant agent helping a developer set up or debug a PDF generation pipeline.
- Systems where PDF generation must remain local and under user control, with the agent only providing instructions and patterns.
- Teams standardizing best practices for PDF output (consistent layout, metadata, and print CSS) across multiple services or documents.
Comments (0)
No comments yet. Be the first!