Agent skill

Python Execution Fallback

Four-step recovery workflow for code execution failures when inline Python fails

MITAuto-check passed

Install Python Execution Fallback

skills CLI

$ npx skills add HKUDS/OpenSpace --skill python-execution-fallback -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install HKUDS/OpenSpace python-execution-fallback --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/HKUDS/OpenSpace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/benchmarks/gdpval/skills/python-execution-fallback .claude/skills/python-execution-fallback && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "python-execution-fallback" agent skill from https://github.com/HKUDS/OpenSpace/tree/main/benchmarks/gdpval/skills/python-execution-fallback into .claude/skills/python-execution-fallback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "python-execution-fallback", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/HKUDS/OpenSpace/tree/main/benchmarks/gdpval/skills/python-execution-fallback

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add HKUDS/OpenSpace --skill python-execution-fallback -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install HKUDS/OpenSpace python-execution-fallback --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/HKUDS/OpenSpace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/benchmarks/gdpval/skills/python-execution-fallback .agents/skills/python-execution-fallback && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "python-execution-fallback" agent skill from https://github.com/HKUDS/OpenSpace/tree/main/benchmarks/gdpval/skills/python-execution-fallback into .agents/skills/python-execution-fallback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "python-execution-fallback", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add HKUDS/OpenSpace --skill python-execution-fallback -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install HKUDS/OpenSpace python-execution-fallback --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/HKUDS/OpenSpace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/benchmarks/gdpval/skills/python-execution-fallback .cursor/skills/python-execution-fallback && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "python-execution-fallback" agent skill from https://github.com/HKUDS/OpenSpace/tree/main/benchmarks/gdpval/skills/python-execution-fallback into .cursor/skills/python-execution-fallback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "python-execution-fallback", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/HKUDS/OpenSpace.git --path benchmarks/gdpval/skills/python-execution-fallback

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add HKUDS/OpenSpace --skill python-execution-fallback -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install HKUDS/OpenSpace python-execution-fallback --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/HKUDS/OpenSpace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/benchmarks/gdpval/skills/python-execution-fallback .gemini/skills/python-execution-fallback && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "python-execution-fallback" agent skill from https://github.com/HKUDS/OpenSpace/tree/main/benchmarks/gdpval/skills/python-execution-fallback into .gemini/skills/python-execution-fallback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "python-execution-fallback", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install HKUDS/OpenSpace python-execution-fallback

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add HKUDS/OpenSpace --skill python-execution-fallback -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/HKUDS/OpenSpace.git skills-src && mkdir -p .github/skills && cp -r skills-src/benchmarks/gdpval/skills/python-execution-fallback .github/skills/python-execution-fallback && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "python-execution-fallback" agent skill from https://github.com/HKUDS/OpenSpace/tree/main/benchmarks/gdpval/skills/python-execution-fallback into .github/skills/python-execution-fallback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "python-execution-fallback", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add HKUDS/OpenSpace --skill python-execution-fallback -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install HKUDS/OpenSpace python-execution-fallback --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/HKUDS/OpenSpace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/benchmarks/gdpval/skills/python-execution-fallback .opencode/skills/python-execution-fallback && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "python-execution-fallback" agent skill from https://github.com/HKUDS/OpenSpace/tree/main/benchmarks/gdpval/skills/python-execution-fallback into .opencode/skills/python-execution-fallback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "python-execution-fallback", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: python-execution-fallback
GitHub stars: 7.7k
Token cost: ~1.2k tokens
SKILL.md length: 322 words
Files: 2
Skills in repo: 199
Repo updated: Aug 12, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Four-step recovery workflow for code execution failures when inline Python fails

Works in 4 steps: Attempt Inline Execution → Write Script to File (On Failure) → Execute the File → …
SKILL.md covers Pattern Overview, When to Use, Step-by-Step Instructions and Code Example: Complete Workflow, plus 3 more sections
Calls python

What it does

Python Execution Fallback is an agent skill from HKUDS/OpenSpace. Four-step recovery workflow for code execution failures when inline Python fails

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file.

It works with Python. The repository describes itself as: "OpenSpace: The Skill Management Layer for AI Agents" -- https://open-space.cloud/. The licence is MIT.

Example prompts

“/python-execution-fallback”

Requirements

Python 3

Workflow steps

4 steps, taken from the step headings in SKILL.md.

Attempt Inline Execution
Write Script to File (On Failure)
Execute the File
Validate Output

What it can do on your machine

Read from SKILL.md and the folder at commit 3827781. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- python
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Python Execution Fallback loads about 1.2k tokens when it runs. Until then it costs about 27 tokens; SKILL.md has 322 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~27
When it runs · the whole SKILL.md, loaded when a task matches: ~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from HKUDS/OpenSpace at commit 3827781, republished under its MIT licence (© HKUDS). 322 words, ~1,213 tokens.

Download SKILL.mdSave it as .claude/skills/python-execution-fallback/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: python-execution-fallback
description: Four-step recovery workflow for code execution failures when inline Python fails

Python Execution Fallback Workflow

This skill provides a systematic debugging approach when inline Python code execution fails, particularly in heredoc or shell_agent contexts.

Pattern Overview

When Python code execution fails, follow this recovery workflow:

Attempt inline execution first - Try running Python code directly
Write script to file on failure - Persist the code to a .py file
Execute the file - Run the saved script via shell
Validate output - Verify results are correct and complete

When to Use

Apply this pattern when:

Inline Python execution fails with syntax or runtime errors
Heredoc-based code execution encounters parsing issues
Working with complex multi-line scripts that need debugging
Need systematic approach to isolate execution failures
Spreadsheet/data generation tasks fail in inline mode

Step-by-Step Instructions

Step 1: Attempt Inline Execution

Try executing Python code inline first (using execute_code_sandbox or similar):

python

# Example: Attempt inline execution
import pandas as pd
import openpyxl

df = pd.read_excel("input.xlsx")
# Process data...
df.to_excel("output.xlsx", index=False)

If this succeeds, proceed. If it fails, move to Step 2.

Step 2: Write Script to File (On Failure)

When inline execution fails, write the complete script to a persistent file:

python

# Capture the script content
script_content = '''
import pandas as pd
import openpyxl
import sys

try:
    # Your original code here
    df = pd.read_excel("input.xlsx")
    
    # Processing logic
    result_df = df.groupby("category").sum()
    
    # Output
    result_df.to_excel("output.xlsx", index=False)
    print("SUCCESS: File generated")
    
except Exception as e:
    print(f"ERROR: {e}", file=sys.stderr)
    sys.exit(1)
'''

# Write to file
with open("script.py", "w") as f:
    f.write(script_content)

print("Script written to script.py")

Step 3: Execute the File

Run the saved script using shell execution:

bash

python script.py

Or with error capture:

bash

python script.py 2>&1 | tee execution.log

This approach:

Avoids heredoc parsing issues
Provides clearer error messages
Allows script inspection and modification
Enables re-execution without rewriting

Step 4: Validate Output

Verify the results are correct:

python

# Validation script
import pandas as pd
import os

# Check file exists
if os.path.exists("output.xlsx"):
    df = pd.read_excel("output.xlsx")
    print(f"Rows: {len(df)}, Columns: {len(df.columns)}")
    print(df.head())
    print("VALIDATION: PASSED")
else:
    print("VALIDATION: FAILED - Output file missing")

Code Example: Complete Workflow

python

# Full fallback workflow example
def generate_spreadsheet_fallback(data, output_path):
    """Generate spreadsheet with fallback workflow"""
    
    # Step 1: Try inline
    inline_script = f'''
import pandas as pd
data = {data}
df = pd.DataFrame(data)
df.to_excel("{output_path}", index=False)
'''
    
    try:
        # Attempt inline execution
        result = execute_code_sandbox(code=inline_script)
        if "error" not in result.lower():
            return "SUCCESS_INLINE"
    except Exception as e:
        pass
    
    # Step 2: Write to file
    file_script = f'''
import pandas as pd
import sys

try:
    data = {data}
    df = pd.DataFrame(data)
    df.to_excel("{output_path}", index=False)
    print("SUCCESS")
except Exception as e:
    print(f"ERROR: {{e}}", file=sys.stderr)
    sys.exit(1)
'''
    
    with open("generate.py", "w") as f:
        f.write(file_script)
    
    # Step 3: Execute file
    shell_result = run_shell(command="python generate.py")
    
    # Step 4: Validate
    if os.path.exists(output_path):
        return "SUCCESS_FILE"
    else:
        return "FAILED"

Best Practices

Include error handling in file-based scripts (try/except with sys.stderr)
Add success indicators (print statements) to confirm execution
Preserve original logic when converting from inline to file
Check return codes when executing scripts via shell
Clean up temporary files after successful validation
Log both stdout and stderr for debugging

Common Failure Scenarios

This pattern helps resolve:

Heredoc string escaping issues
Multi-line code formatting problems
Import path resolution failures
Environment variable access issues
Complex indentation in inline code

Combine with retry-with-modification for iterative debugging
Use alongside output-validation-check for result verification
Pair with error-log-analysis for root cause identification

Files

SKILL.md and 1 other file in benchmarks/gdpval/skills/python-execution-fallback of HKUDS/OpenSpace.

SKILL.md
.skill_id

Open the folder on GitHubat commit 3827781

Compare with similar skills

Python Execution Fallback next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Python Execution Fallback compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Python Execution Fallback this skillHKUDS/OpenSpace	7.7k	—	~1.2k	Automated safety check: Pass	MIT	1 mo ago
MCP Server Builderanthropics/skills	180k	62 repos	~2.3k	Automated safety check: Pass	Apache-2.0	2 days ago
PDF Processinganthropics/skills	180k	48 repos	~2k	Automated safety check: Pass	Proprietary	2 days ago
NotebookLM Research AssistantPleasePrompto/notebooklm-skill	7.8k	13 repos	~2.4k	Automated safety check: Notes	MIT	27 days ago
Manim Video Productionbrowser-use/video-use	28k	6 repos	~3k	Automated safety check: Pass	MIT	5 days ago
Code Review ChecklistshareAI-lab/learn-claude-code	78k	5 repos	~1.1k	Automated safety check: Pass	MIT	9 days ago

Similar skills

MCP Server Builder
anthropics/skills
Official
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
180k GitHub starsUsed in 62 repos~2.3k tokens
Agent WorkflowsAuto-check passed
PDF Processing
anthropics/skills
Official
Handles everyday PDF jobs in Python and on the command line: extract text and tables, merge, split, rotate, watermark, fill forms, encrypt and OCR.
180k GitHub starsUsed in 48 repos~2k tokens
Documents & OfficeAuto-check passed
NotebookLM Research Assistant
PleasePrompto/notebooklm-skill
Lets Claude Code ask questions of your Google NotebookLM notebooks through browser automation and return answers grounded in your uploaded sources.
7.8k GitHub starsUsed in 13 repos~2.4k tokens
Knowledge ManagementAuto-check: notes
Manim Video Production
browser-use/video-use
Produces math and technical explainer videos with Manim Community Edition: concept animations, equation derivations, algorithm walkthroughs and data stories.
28k GitHub starsUsed in 6 repos~3k tokens
Media & CreativeAuto-check passed
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
78k GitHub starsUsed in 5 repos~1.1k tokens
DevelopmentAuto-check passed
PPT Master
hugohe3/ppt-master
Generates editable PowerPoint decks, rebuilds slides from images, fills .pptx templates and polishes existing presentations through routed workflows.
58k GitHub starsUsed in 1 repo~2.5k tokens
Documents & OfficeAuto-check passed

Questions about Python Execution Fallback

What does Python Execution Fallback do?

Four-step recovery workflow for code execution failures when inline Python fails. Python Execution Fallback is an agent skill from HKUDS/OpenSpace.

How do I install Python Execution Fallback in Claude Code?

Run `npx skills add HKUDS/OpenSpace --skill python-execution-fallback -a claude-code`. Or copy the skill folder (benchmarks/gdpval/skills/python-execution-fallback in HKUDS/OpenSpace) into .claude/skills/python-execution-fallback in your project. Claude Code loads it when a task matches its description.

How do I install Python Execution Fallback in Codex?

Run `npx skills add HKUDS/OpenSpace --skill python-execution-fallback -a codex`. Or copy the skill folder (benchmarks/gdpval/skills/python-execution-fallback in HKUDS/OpenSpace) into .agents/skills/python-execution-fallback in your project. Codex loads it when a task matches its description.

Can I use Python Execution Fallback in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add HKUDS/OpenSpace --skill python-execution-fallback -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/python-execution-fallback, .gemini/skills/python-execution-fallback, .github/skills/python-execution-fallback and .opencode/skills/python-execution-fallback in your project.

What does Python Execution Fallback need to run?

Going by SKILL.md and its folder, Python Execution Fallback needs the command-line tools its instructions call (python). Our summary lists: Python 3.

Does Python Execution Fallback access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Python Execution Fallback safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Python Execution Fallback use?

Python Execution Fallback is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Python Execution Fallback use?

About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Python Execution Fallback?

Skills that share tags, products or a category with Python Execution Fallback: MCP Server Builder (anthropics/skills, 180k stars), PDF Processing (anthropics/skills, 180k stars), NotebookLM Research Assistant (PleasePrompto/notebooklm-skill, 7.8k stars) and Manim Video Production (browser-use/video-use, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Python Execution Fallback?

HKUDS (a GitHub organization) maintains it in HKUDS/OpenSpace, which has 7,743 GitHub stars. The repository holds 199 skills in this directory. The repository was last updated on August 12, 2026.

Source: HKUDS/OpenSpace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Python Execution Fallback

Facts

At a glance

What it does

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Python Execution Fallback Workflow

Pattern Overview

When to Use

Step-by-Step Instructions

Step 1: Attempt Inline Execution

Step 2: Write Script to File (On Failure)

Step 3: Execute the File

Step 4: Validate Output

Code Example: Complete Workflow

Best Practices

Common Failure Scenarios

Related Patterns

Files

Compare with similar skills

Similar skills

More from HKUDS/OpenSpace

Related

Questions about Python Execution Fallback