Agent skill

Python Spreadsheet Debug

Systematic Python debugging workflow for spreadsheet tasks to isolate environment issues from script logic

Install Python Spreadsheet Debug

skills CLI

$ npx skills add HKUDS/OpenSpace --skill python-spreadsheet-debug -a claude-code

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

GitHub CLI

$ gh skill install HKUDS/OpenSpace python-spreadsheet-debug --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-spreadsheet-debug .claude/skills/python-spreadsheet-debug && 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-spreadsheet-debug" agent skill from https://github.com/HKUDS/OpenSpace/tree/main/benchmarks/gdpval/skills/python-spreadsheet-debug into .claude/skills/python-spreadsheet-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "python-spreadsheet-debug", 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-spreadsheet-debug

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-spreadsheet-debug -a codex

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

GitHub CLI

$ gh skill install HKUDS/OpenSpace python-spreadsheet-debug --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-spreadsheet-debug .agents/skills/python-spreadsheet-debug && 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-spreadsheet-debug" agent skill from https://github.com/HKUDS/OpenSpace/tree/main/benchmarks/gdpval/skills/python-spreadsheet-debug into .agents/skills/python-spreadsheet-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "python-spreadsheet-debug", 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-spreadsheet-debug -a cursor

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

GitHub CLI

$ gh skill install HKUDS/OpenSpace python-spreadsheet-debug --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-spreadsheet-debug .cursor/skills/python-spreadsheet-debug && 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-spreadsheet-debug" agent skill from https://github.com/HKUDS/OpenSpace/tree/main/benchmarks/gdpval/skills/python-spreadsheet-debug into .cursor/skills/python-spreadsheet-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "python-spreadsheet-debug", 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-spreadsheet-debug

--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-spreadsheet-debug -a gemini-cli

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

GitHub CLI

$ gh skill install HKUDS/OpenSpace python-spreadsheet-debug --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-spreadsheet-debug .gemini/skills/python-spreadsheet-debug && 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-spreadsheet-debug" agent skill from https://github.com/HKUDS/OpenSpace/tree/main/benchmarks/gdpval/skills/python-spreadsheet-debug into .gemini/skills/python-spreadsheet-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "python-spreadsheet-debug", 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-spreadsheet-debug

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-spreadsheet-debug -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-spreadsheet-debug .github/skills/python-spreadsheet-debug && 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-spreadsheet-debug" agent skill from https://github.com/HKUDS/OpenSpace/tree/main/benchmarks/gdpval/skills/python-spreadsheet-debug into .github/skills/python-spreadsheet-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "python-spreadsheet-debug", 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-spreadsheet-debug -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-spreadsheet-debug --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-spreadsheet-debug .opencode/skills/python-spreadsheet-debug && 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-spreadsheet-debug" agent skill from https://github.com/HKUDS/OpenSpace/tree/main/benchmarks/gdpval/skills/python-spreadsheet-debug into .opencode/skills/python-spreadsheet-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "python-spreadsheet-debug", 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-spreadsheet-debug
GitHub stars: 7.7k
Token cost: ~860 tokens
SKILL.md length: 296 words
Files: 2
Skills in repo: 199
Repo updated: Aug 12, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Systematic Python debugging workflow for spreadsheet tasks to isolate environment issues from script logic

Works in 4 steps: Verify Python Environment → Test Library Imports in Isolation → Run Minimal Test Script → …
Tasks that involve Excel spreadsheets
SKILL.md covers Step 1: Verify Python…, Step 2: Test Library Imports…, Step 3: Run Minimal Test Script and Step 4: Execute Full Script, plus 4 more sections
Calls python, pip and python3

What it does

Python Spreadsheet Debug is an agent skill from HKUDS/OpenSpace. Systematic Python debugging workflow for spreadsheet tasks to isolate environment issues from script logic

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

It sits in Documents & Office, covering Excel spreadsheets and Debugging. 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.

When your agent uses it

Tasks that involve Excel spreadsheets
Tasks that involve Debugging

Example prompts

“/python-spreadsheet-debug”

Requirements

Python 3

Workflow steps

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

Verify Python Environment
Test Library Imports in Isolation
Run Minimal Test Script
Execute Full Script

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
- pip
- python3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pip, which can reach the network depending on how they are called.
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 Spreadsheet Debug loads about 860 tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 296 words of instructions outside code blocks.

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

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). 296 words, ~860 tokens.

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

name: python-spreadsheet-debug
description: Systematic Python debugging workflow for spreadsheet tasks to isolate environment issues from script logic

Python Spreadsheet Debugging Workflow

When executing Python scripts for spreadsheet/data processing tasks, use this systematic debugging approach to efficiently isolate environment configuration issues from script logic errors, especially when run_shell returns opaque errors.

Step 1: Verify Python Environment

First, confirm the Python interpreter path and version to ensure you're working in the expected environment:

bash

which python python3
python --version
python3 --version

This identifies whether Python is available and which version is being used.

Step 2: Test Library Imports in Isolation

Before running your full script, verify that required libraries can be imported successfully. Test each critical import individually:

bash

python -c "import pandas; print('pandas:', pandas.__version__)"
python -c "import openpyxl; print('openpyxl:', openpyxl.__version__)"
python -c "import xlrd; print('xlrd:', xlrd.__version__)"

Replace library names based on your script's requirements. This identifies missing dependencies or version conflicts early.

Step 3: Run Minimal Test Script

Create and execute a minimal script that exercises only the core functionality without full business logic:

python

# test_minimal.py
import pandas as pd

# Test 1: Can we read a file?
try:
    df = pd.read_excel('sample.xlsx')
    print(f"✓ File read successful: {len(df)} rows")
except Exception as e:
    print(f"✗ File read failed: {e}")

# Test 2: Can we perform basic operations?
try:
    result = df.groupby('category')['amount'].sum()
    print(f"✓ GroupBy operation successful")
except Exception as e:
    print(f"✗ Operation failed: {e}")

Run this with: python test_minimal.py

Purpose: This isolates whether the issue is with file access, library functionality, or specific script logic.

Step 4: Execute Full Script

Once the minimal test passes, run the complete script:

bash

python your_script.py

If errors occur now, you know the environment is correctly configured and can focus on debugging the specific logic.

Quick Diagnostic Command

For rapid diagnosis, run all checks in sequence:

bash

echo "=== Python Version ===" && python --version && \
echo "=== Key Imports ===" && python -c "import pandas, openpyxl; print('OK')" && \
echo "=== Ready for full script ==="

Common Issues and Resolutions

Symptom	Likely Cause	Resolution
`ModuleNotFoundError`	Missing package	`pip install <package-name>`
`ImportError` with version	Version conflict	Check `pip list`, reinstall specific version
`FileNotFoundError`	Wrong path/context	Verify working directory with `pwd`
`PermissionError`	File access	Check file permissions or path

When to Use This Pattern

run_shell returns cryptic or truncated error messages
Script worked previously but suddenly fails
Deploying to a new environment or container
Debugging spreadsheet processing with pandas, openpyxl, xlrd, etc.

Benefits

Fast isolation: Identifies environment vs. logic issues within seconds
Incremental confidence: Each passing step narrows the problem space
Reusable pattern: Apply consistently across all Python spreadsheet tasks

Files

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

SKILL.md
.skill_id

Open the folder on GitHubat commit 3827781

Compare with similar skills

Python Spreadsheet Debug 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 Spreadsheet Debug compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Python Spreadsheet Debug this skillHKUDS/OpenSpace	7.7k	—	~860	Automated safety check: Pass	MIT	1 mo ago
Instrument Data To Allotropeaws-samples/amazon-bedrock-agents-healthcare-lifesciences	274	2 repos	~2.7k	Automated safety check: Pass	Apache-2.0	5 days ago
Doc Cleanernotoriouslab/doc-cleaner	309	—	~712	Automated safety check: Pass	MIT	1 mo ago
MineruNebutra/MinerU-Skill	122	—	~504	Automated safety check: Pass	MIT	13 days ago
XLSXzzhonglei/GeoCode-Release	186	—	~3.1k	Automated safety check: Pass	MIT	3 days ago
Python Bridgetmustier/pi-for-excel	434	—	~820	Automated safety check: Pass	MIT	today

Similar skills

Instrument Data To Allotrope
aws-samples/amazon-bedrock-agents-healthcare-lifesciences
Official
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV.
274 GitHub starsUsed in 2 repos~2.7k tokens
Documents & OfficeAuto-check passed
Doc Cleaner
notoriouslab/doc-cleaner
Convert PDF, DOCX, XLSX, and text files to clean, structured Markdown.
309 GitHub stars~712 tokensUpdated 1 mo ago
Documents & OfficeAuto-check passed
Mineru
Nebutra/MinerU-Skill
An AI-Native skill for parsing PDF / Office / image files into Markdown with MinerU — a fast, zero-config document parser for AI agents.
122 GitHub stars~504 tokensUpdated 13 days ago
Documents & OfficeAuto-check passed
XLSX
zzhonglei/GeoCode-Release
Create, edit, analyze, or convert Excel spreadsheets (.xlsx, .xlsm) where the workbook file is the primary deliverable.
186 GitHub stars~3.1k tokensUpdated 3 days ago
Documents & OfficeAuto-check passed
Python Bridge
tmustier/pi-for-excel
Native Python execution via the local Python bridge. An agent skill from tmustier/pi-for-excel.
434 GitHub stars~820 tokensUpdated today
Documents & OfficeAuto-check passed
Office To Md
shuyu-labs/WebCode
Convert Office documents (Word, Excel, PowerPoint, PDF) to Markdown format.
278 GitHub stars~1k tokensUpdated 3 mo ago
Documents & OfficeAuto-check: notes

Questions about Python Spreadsheet Debug

What does Python Spreadsheet Debug do?

Systematic Python debugging workflow for spreadsheet tasks to isolate environment issues from script logic. Python Spreadsheet Debug is an agent skill from HKUDS/OpenSpace.

When should I use Python Spreadsheet Debug?

Python Spreadsheet Debug fits situations like: tasks that involve Excel spreadsheets; tasks that involve Debugging.

How do I install Python Spreadsheet Debug in Claude Code?

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

How do I install Python Spreadsheet Debug in Codex?

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

Can I use Python Spreadsheet Debug 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-spreadsheet-debug -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-spreadsheet-debug, .gemini/skills/python-spreadsheet-debug, .github/skills/python-spreadsheet-debug and .opencode/skills/python-spreadsheet-debug in your project.

What does Python Spreadsheet Debug need to run?

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

Does Python Spreadsheet Debug access the network?

SKILL.md contains no URLs. Its commands use pip, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Python Spreadsheet Debug 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 Spreadsheet Debug use?

Python Spreadsheet Debug 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 Spreadsheet Debug use?

About 860 tokens (SKILL.md is roughly 3.4k 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 Spreadsheet Debug?

Skills that share tags, products or a category with Python Spreadsheet Debug: Instrument Data To Allotrope (aws-samples/amazon-bedrock-agents-healthcare-lifesciences, 274 stars), Doc Cleaner (notoriouslab/doc-cleaner, 309 stars), Mineru (Nebutra/MinerU-Skill, 122 stars) and XLSX (zzhonglei/GeoCode-Release, 186 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Python Spreadsheet Debug?

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 Spreadsheet Debug

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Python Spreadsheet Debugging Workflow

Step 1: Verify Python Environment

Step 2: Test Library Imports in Isolation

Step 3: Run Minimal Test Script

Step 4: Execute Full Script

Quick Diagnostic Command

Common Issues and Resolutions

When to Use This Pattern

Benefits

Files

Compare with similar skills

Similar skills

More from HKUDS/OpenSpace

Related

Questions about Python Spreadsheet Debug