.claude/skills/python-playground/SKILL.md
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.
npx skillsauth add pydantic/monty python-playgroundInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Run Python code in an isolated playground directory for testing and experimentation.
playground directory doesn't already exist, run mkdir playground.playground/test.pyuv run playground/test.py to test cpython behavior or cargo run -- playground/test.py to test monty behaviorIMPORTANT: Use separate tool calls for each step - do NOT chain commands with &&. This allows the pre-approved commands to work without prompting.
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
playground/ directory is gitignoredtest_value_error.pyuv run ... to run scripts (uses project Python)cargo run -- ... to run scripts using Montydevelopment
Use fastmod to make mass code updates to avoid many repetitive changes.
development
Fetch coverage diff from Codecov for the current branch or a specific PR. Shows uncovered lines, patch coverage, and overall coverage change.
development
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
development
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.