Skip to content
cccskills
FreePublished on GitHub

sandbox-failure-recovery

Resume Python tasks after execute_code_sandbox errors or timeouts by saving the attempted code as a script and running it through run_shell. The workflow includes dependency checks, execution timeouts, and verification of generated files such as Excel reports.

OriginalShow the original description

Recover from execute_code_sandbox failures by writing code to file and executing via run_shell

Works withExcel
See how to install

Good for

  • Retrying Python code after sandbox errors
  • Resuming Excel or CSV generation after a failure
  • Running saved scripts with a longer timeout
  • Checking generated files after a retry

Files included (2)

  • SKILL.md3.5 KB
  • .skill_id38 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Sandbox Failure Recovery Workflow

When execute_code_sandbox fails (often due to infrastructure issues, timeouts, or complex dependencies), use this recovery pattern to achieve identical results by writing the code to a file and executing it directly.

When to Use This Skill

  • execute_code_sandbox returns an error or times out
  • The task involves spreadsheet generation (Excel, CSV) or file output
  • You have working Python code that needs to be executed
  • The sandbox environment appears unstable

Step-by-Step Instructions

Step 1: Preserve the Failed Code

When execute_code_sandbox fails, capture the Python code that was attempted. If the code was generated but not saved, reconstruct it from the execution attempt.

Step 2: Write Code to File

Use write_file to save the Python script to a .py file:

write_file with:
- path: "script_name.py" (e.g., "generate_report.py", "process_data.py")
- content: <the full Python code>

Example:

# Content for write_file
import pandas as pd
from openpyxl import Workbook

# Your spreadsheet generation logic here
df = pd.DataFrame({'Revenue': [100, 200, 300]})
df.to_excel('output.xlsx', index=False)

Step 3: Execute via run_shell

Run the saved script using run_shell with Python 3:

run_shell with:
- command: "python3 script_name.py"
- timeout: 60 (or higher for complex operations)

Step 4: Verify Output

Check that the expected output files were created:

list_dir with:
- path: "."

Or read the generated file to confirm correctness:

read_file with:
- file_path: "output.xlsx"
- filetype: "xlsx"

Complete Example

Scenario: Generate an Excel P&L report after sandbox failure.

# Step 1: Write the Python script
write_file:
  path: "generate_pnl_report.py"
  content: |
    import pandas as pd
    from openpyxl import Workbook
    
    # Create revenue data
    data = {
        'Tour Stop': ['London', 'Paris', 'Berlin'],
        'Revenue': [50000, 45000, 38000],
        'Withholding Tax': [5000, 4500, 3800],
        'Expenses': [12000, 11000, 9500]
    }
    df = pd.DataFrame(data)
    df['Net Income'] = df['Revenue'] - df['Withholding Tax'] - df['Expenses']
    
    # Export to Excel
    df.to_excel('pnl_report.xlsx', index=False)
    print("Report generated successfully")

# Step 2: Execute the script
run_shell:
  command: "python3 generate_pnl_report.py"
  timeout: 60

# Step 3: Verify
list_dir:
  path: "."

Best Practices

  1. Use descriptive filenames - Name files after their purpose (e.g., generate_report.py, process_spreadsheet.py)

  2. Set appropriate timeouts - Complex operations may need 60+ seconds

  3. Include error handling in your Python code - Add try/except blocks to capture and report issues:

    try:
        # Your code here
    except Exception as e:
        print(f"Error: {e}")
        raise
    
  4. Clean up temporary files - After successful execution, you may remove the .py file if not needed

  5. Check dependencies - Ensure required packages (pandas, openpyxl, etc.) are available in the shell environment

Why This Works

  • run_shell executes in a more stable environment than the sandbox
  • File-based execution avoids sandbox memory/resource constraints
  • The Python interpreter in the shell has full access to installed packages
  • Output files are written directly to the workspace

<THIS_SKILL_EVOLVED>

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