Automated summary
Runs and tests Python snippets in an isolated playground directory without affecting the main codebase.
Strengths
- Keeps experiments clearly separated from project code through a gitignored directory
- Provides concrete commands for creating, writing, and running scripts with uv or Monty via cargo
- Favors separate tool calls to avoid permission prompts
- Leaves test files in place for later reference
Limitations
- Assumes uv and optionally cargo/Monty are installed and configured
- Does not address Python dependency management beyond the project environment
- Focused on simple script execution rather than structured test suites
When you need to quickly verify Python snippet behavior or reproduce an error without changing the main repository.
When running the project's official test suite or code that must interact with the production environment.
Security analysis
CautionThe skill is transparent and non-malicious: it creates a local playground directory, writes Python files, and runs them with standard tooling (uv/cargo). There is no exfiltration, no destructive command, no obfuscation, and no attempt to disable safety. The only real residual risk is arbitrary local code execution, which is inherent to the stated purpose, so it merits 'caution' rather than 'safe' or 'risky'. The inaccurate 'already allowed' claims are a minor permissions-hygiene issue.
- •Instructs the agent to execute arbitrary Python files via `uv run` and `cargo run`, which is local code execution with the user's privileges
- •Claims `mkdir -p playground` and `uv run` are 'already allowed' despite no allowed-tools being declared, which is inaccurate and may mislead the agent about its permissions
- •Encourages writing scripts into the repo working tree (mitigated by the gitignore note)
Examples
Create a Python playground script that raises a ValueError and run it with uv to confirm the traceback.In the playground, test how CPython handles a mutable default argument and show the output.Write a small Python script in playground/test.py and run it with cargo run to see how Monty executes it.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):
mkdir -p 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
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/python-playground-mm5t8caj/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/python-playground-mm5t8caj' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/python-playground-mm5t8caj/download' --output '.skill-downloads/python-playground-mm5t8caj/SKILL.md.part' && mv '.skill-downloads/python-playground-mm5t8caj/SKILL.md.part' '.skill-downloads/python-playground-mm5t8caj/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/python-playground-mm5t8caj/SKILL.md' && test -s '.skill-downloads/python-playground-mm5t8caj/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/python-playground' && cp -R '.skill-downloads/python-playground-mm5t8caj' '.claude/skills/python-playground'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/python-playground-mm5t8caj'openskills read 'python-playground-mm5t8caj'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/python-playground-mm5t8caj/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.