Skip to content
cccskills
FreePublished on GitHub

pdf-gen-fallback

Generate PDF documents when sandbox execution fails with unclear errors. Check available Python libraries, switch to direct shell execution, and verify the resulting file while collecting error details to help diagnose problems.

OriginalShow the original description

Reliable PDF generation using shell-based Python execution when sandbox fails

See how to install

Good for

  • Generating a PDF after sandbox execution fails
  • Checking PDF libraries and choosing an alternative
  • Verifying generated PDFs and investigating errors

Files included (2)

  • SKILL.md3.2 KB
  • .skill_id30 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

PDF Generation Fallback

This skill provides a reliable workflow for generating PDFs and documents when execute_code_sandbox returns opaque errors. Use direct run_shell with python -c as a fallback, with library availability checks and explicit error handling.

When to Use

  • execute_code_sandbox fails with cryptic error messages during document/PDF generation
  • You need to generate PDFs, reports, or structured documents
  • Standard library execution is unreliable for document creation tasks

Step-by-Step Procedure

Step 1: Check Library Availability

Before attempting generation, verify that required libraries are installed:

run_shell command="python -c \"import reportlab; print('reportlab available')\""
run_shell command="python -c \"import fpdf; print('fpdf available')\""
run_shell command="python -c \"import pypdf; print('pypdf available')\""

Step 2: Attempt execute_code_sandbox First

Try the sandbox approach initially (it's cleaner for iteration):

execute_code_sandbox code="""
from reportlab.lib.pagesizes import letter
from reportlab.pdfgen import canvas

c = canvas.Canvas("output.pdf", pagesize=letter)
c.drawString(100, 750, "Document Content")
c.save()
print("ARTIFACT_PATH:/path/to/output.pdf")
"""

Step 3: Detect Opaque Errors

Watch for these failure indicators:

  • Generic "execution failed" messages
  • Import errors that don't match library availability checks
  • Timeout errors during document rendering
  • Missing artifact paths in output

Step 4: Fall Back to run_shell

If sandbox fails, use direct shell execution:

run_shell command="python -c \"
from reportlab.lib.pagesizes import letter
from reportlab.pdfgen import canvas
c = canvas.Canvas('output.pdf', pagesize=letter)
c.drawString(100, 750, 'Document Content')
c.save()
print('PDF created successfully')
\""

Step 5: Verify Output

After generation, confirm the file exists:

run_shell command="ls -la output.pdf && file output.pdf"

Complete Example Workflow

1. Check libraries: run_shell "python -c \"import reportlab\""
2. Try sandbox: execute_code_sandbox with PDF generation code
3. If error detected: Fall back to run_shell with python -c
4. Verify: run_shell "ls -la *.pdf"
5. Read result: read_file filetype="pdf" file_path="output.pdf"

Error Handling Tips

  • Capture stderr from run_shell to diagnose issues
  • Use absolute paths when possible to avoid working directory issues
  • For complex documents, write the Python script to a file first, then execute
  • Consider installing missing libraries: run_shell command="pip install reportlab"

Library Alternatives

If reportlab is unavailable, try:

  • fpdf - Simpler API, good for basic PDFs
  • weasyprint - HTML/CSS to PDF conversion
  • pypdf - PDF manipulation and merging

Common Pitfalls

  • Don't assume sandbox errors mean the approach is wrong—often it's环境 issues
  • Always verify the PDF was created before proceeding
  • Handle encoding issues explicitly (use utf-8)
  • For images in PDFs, ensure image files are accessible to the execution context

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Prepare audio stems, the separate parts of a track, for mixing by matching their durations with silence, loops, or crossfades. Verify each generated and processed file before moving to the next production step.

  • Match audio parts with different durations
  • Extend drums and melodic parts using suitable methods
  • Check audio specifications before mixing
HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

Produce audio in separate stems, meaning individual instrument tracks, and verify each output as you go. Align track lengths with silence, loops, or crossfades, then apply effects, mix a master, and package the files.

  • Align instrument tracks to a reference audio file
  • Choose how to extend tracks that are too short
  • Verify audio properties after generation and effects
HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

Build serverless endpoints that relay external API requests for a dashboard while keeping API keys on the server. Includes Vercel examples for input checks, caching, cross-origin access, and consistent JSON responses.

  • Connect a dashboard to external APIs without exposing API keys
  • Create endpoints for stock quotes and news
  • Standardize API responses and error handling
HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

Produce a master track and separate audio parts through a structured Python workflow. Apply filters and reverb, export WAV files with consistent settings, package them in a ZIP archive, and check that the deliverables meet the requested specifications.

  • Export a master track with separate audio parts
  • Apply filters and reverb to audio
  • Check duration and format across deliverables
HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

Keep document creation moving when web searches and page retrieval repeatedly fail. The skill preserves the original task, uses the model’s existing knowledge, and clearly identifies information that could not be checked against external sources.

  • Continue drafting after repeated web retrieval failures
  • Preserve task requirements during network errors
  • Mark information that could not be externally verified
HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

When Python execution repeatedly fails in execute_code_sandbox, use a file-based alternative: save the script, run it through the shell, and capture results or errors. The guidance covers paths, imports, timeouts, structured output, and optional cleanup.

  • Retry Python work through the shell after repeated sandbox failures
  • Run longer tasks with an adjusted timeout
  • Execute Python work that needs multiple files or system utilities
HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

See all skills by HKUDS

Report a problem with this skill