Agent Skills
› pydantic/monty
› python-playground
python-playground
GitHub在隔离的 playground 目录中运行和测试 Python 代码,用于执行脚本、测试片段或实验 CPython 行为,确保不影响主代码库。
Trigger Scenarios
需要执行 Python 脚本
测试代码片段
实验 Python 行为
Install
npx skills add pydantic/monty --skill python-playground -g -y
SKILL.md
Frontmatter
{
"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. If the
playgrounddirectory doesn't already exist, runmkdir 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 &&. This allows the pre-approved commands to work without prompting.
Example workflow
Step 1 - Create directory if it doesn't already exist (Bash, already allowed):
mkdir playground
Step 2 - Write code (use Write tool, not cat):
Write to playground/test.py:
def foo():
raise ValueError('test')
foo()
Step 3 - Run script (Bash, already allowed):
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
Version History
- 026b383 Current 2026-08-20 09:39


