python-parallelization
v0.1.0Transform sequential Python code into parallel/concurrent implementations. Use when asked to parallelize Python code, improve code performance through concur...
⭐ 0· 34·0 current·0 all-time
by@lnj22
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description match the SKILL.md and reference document: all recommended tools and patterns (multiprocessing, asyncio, NumPy, Dask, etc.) are relevant to Python parallelization. No unrelated binaries, credentials, or config paths are requested.
Instruction Scope
The runtime instructions are narrowly scoped to analyzing and transforming Python code for concurrency/parallelism. They do not instruct reading arbitrary system files, contacting external endpoints, or exfiltrating data. Examples reference common libraries and typical file operations (e.g., read_csv) which are appropriate for the domain.
Install Mechanism
This is an instruction-only skill with no install spec and no downloads or extracted archives. That minimizes disk-write/remote-code risk.
Credentials
No environment variables, credentials, or config paths are required. The skill mentions a number of third-party Python libraries (aiohttp, numba, dask, cupy, tqdm) but does not request credentials or system-level access; these mentions are proportional to the functionality.
Persistence & Privilege
always:false and no steps that modify other skills or system-wide agent settings. The skill does not request permanent presence or elevated privileges.
Assessment
This skill appears coherent and low-risk: it only provides guidance and code patterns for parallelizing Python. Before using it, review any transformed code the agent produces (don't let it run changes automatically), ensure you have the necessary Python libraries installed in your environment, and test transformed code on sample inputs—parallel code can consume many CPU/ memory resources and introduce race conditions or serialization/pickle issues. If you plan to let an agent run or apply changes automatically, require explicit approval for execution. If you need the skill to actually run code, prefer running it in an isolated environment (container/VM) and keep backups of original code.Like a lobster shell, security has layers — review code before you run it.
latestvk97c5xvw69agavnsg6v7z31s9h84wdav
License
MIT-0
Free to use, modify, and redistribute. No attribution required.