Skip to content
cccskills
FreePublished on GitHub

resilient-spreadsheet-workflow

Troubleshoot CSV and XLSX processing when execute_code_sandbox fails. The workflow locates input files, saves processing code as a Python script, captures execution errors, checks dependencies and file access, and confirms output exists before reading it.

OriginalShow the original description

Resilient multi-step workflow for spreadsheet processing when execute_code_sandbox fails, using shell_agent exploration, file-based scripts, and verification steps

See how to install

Good for

  • Recovering spreadsheet processing after sandbox errors
  • Locating CSV and XLSX input files
  • Diagnosing dependency, path, and encoding errors
  • Confirming output files exist before reading them

Files included (2)

  • SKILL.md4.0 KB
  • .skill_id44 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Resilient Spreadsheet Workflow

This skill provides a robust workflow for processing spreadsheet files (CSV, XLSX) when execute_code_sandbox encounters failures. It uses a combination of tools to ensure reliable execution and clear error diagnosis.

When to Use

  • Processing spreadsheet files when execute_code_sandbox returns unknown errors
  • Need to debug why spreadsheet operations fail
  • Require reliable file I/O with verification at each step

Step-by-Step Workflow

Step 1: Initial Exploration with shell_agent

Start by using shell_agent to explore the file structure and understand what files exist:

Use shell_agent to:
- List files in the working directory
- Identify spreadsheet files (CSV, XLSX)
- Examine file sizes and basic structure

Example task for shell_agent:

Explore the current directory to find all spreadsheet files (CSV, XLSX). 
List their sizes and identify which files need processing.

Step 2: Write Processing Script with write_file

Create a standalone script file rather than executing inline code:

# Use write_file to create a script like "process_sheet.py"
content = """
import pandas as pd
import sys

try:
    df = pd.read_csv('input.csv')  # or pd.read_excel for XLSX
    # Perform your processing
    result = df.describe()
    result.to_csv('output.csv', index=False)
    print("Processing complete")
except Exception as e:
    print(f"Error: {e}", file=sys.stderr)
    sys.exit(1)
"""

write_file(path="process_sheet.py", content=content)

Step 3: Execute with run_shell and Error Redirection

Execute the script with stderr redirected to stdout for complete error capture:

run_shell command="python process_sheet.py 2>&1"

The 2>&1 redirection ensures both stdout and stderr are captured together, making error messages visible.

Step 4: Isolate Errors with Verification Commands

If Step 3 fails, add targeted verification commands to diagnose the actual problem:

# Check if Python is available
run_shell command="which python 2>&1"

# Check if pandas is installed
run_shell command="python -c 'import pandas' 2>&1"

# Verify input file exists and is readable
run_shell command="ls -la input.csv 2>&1"

# Check file encoding/content
run_shell command="file input.csv 2>&1"
run_shell command="head -5 input.csv 2>&1"

Step 5: Verify Output Before Reading

Before reading results with read_file, verify the output file exists:

list_dir(path=".")
# Confirm output file appears in the listing
# Then proceed to read_file

Complete Example

1. shell_agent(task="Find and describe all CSV/XLSX files in current directory")
2. write_file(path="analyze_data.py", content="<processing script>")
3. run_shell(command="python analyze_data.py 2>&1")
4. If error: run_shell(command="python -c 'import pandas; print(pandas.__version__)' 2>&1")
5. list_dir(path=".")  # Verify output exists
6. read_file(filetype="csv", file_path="output.csv")

Common Error Patterns

SymptomDiagnostic CommandLikely Cause
Module not foundpython -c 'import pandas'Missing dependency
File not foundls -la <filename>Wrong path or name
Permission deniedls -la <filename>File permissions
Encoding errorfile <filename>Wrong file format

Best Practices

  1. Always use 2>&1 with run_shell for shell commands to capture full error output
  2. Verify before reading - use list_dir to confirm file existence before read_file
  3. Break into small steps - separate exploration, script writing, execution, and verification
  4. Use shell_agent for unknowns - when directory structure or file types are unclear
  5. Write scripts to files - more reliable than inline code execution for complex operations

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