<< All versions
Skill v1.0.1
currentAutomated scan100/100majiayu000/claude-skill-registry/python-playground
3 files
──Details
PublishedJune 24, 2026 at 12:36 AM
Content Hashsha256:2c73c1e181197300...
Git SHA6d0bffa14ce1
Bump Typepatch
──Files
Files (1 file, 1.6 KB)
SKILL.md1.6 KBactive
SKILL.md · 49 lines · 1.6 KB
version: "1.0.1" name: python-playground description: Run and test Python code in a dedicated playground directory. Use when you need to execute Python scripts, test code snippets, investigate CPython behavior, or experiment with Python without affecting the main codebase.
Python Playground
Run Python code in an isolated playground directory for testing and experimentation.
Instructions
- First, ensure the playground directory exists:
mkdir -p playground - Use the Write tool to create the Python file at
playground/test.py - Run with:
uv run playground/test.pyto test cpython behavior orcargo run -- playground/test.pyto test monty behavior
IMPORTANT: Use separate tool calls for each step - do NOT chain commands with && or use heredocs. This allows the pre-approved commands to work without prompting.
Example workflow
Step 1 - Create directory (Bash, already allowed):
bash
mkdir -p playground
Step 2 - Write code (use Write tool, not cat): Write to playground/test.py:
python
def foo():raise ValueError('test')foo()
Step 3 - Run script (Bash, already allowed):
bash
uv run playground/test.py
Guidelines
- The
playground/directory is gitignored - Use a different file name for each test you want to run, give the files recognizable names like
test_value_error.py - Use
uv run ...to run scripts (uses project Python) - Or,
cargo run -- ...to run scripts using Monty - Use Write tool for creating files (avoids permission prompts)
- Run mkdir and uv as separate commands (not chained)
- do NOT delete files from playground after you've finished testing