coding/python-async-patterns/SKILL.md
Async Python patterns for building non-blocking I/O with asyncio and async/await: task orchestration, cancellation, timeouts, backpressure, rate limiting, and safe sync/async boundaries. Use when implementing concurrent network/DB workflows or async services.
npx skillsauth add aeondave/malskill python-async-patternsInstall 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.
This skill focuses on practical asyncio patterns for I/O-bound concurrency.
time.sleep(), no sync HTTP/DB in async code).gather() can turn memory into a queue.to_thread() when necessary.Prefer asyncio.TaskGroup (Python 3.11+) for structured concurrency with clear failure propagation.
async with asyncio.TaskGroup() as tg:
tg.create_task(fetch_url(url1))
tg.create_task(fetch_url(url2))
# All tasks joined; exceptions aggregated
For concurrency limits, add a semaphore:
sem = asyncio.Semaphore(10)
async def bounded():
async with sem:
return await fetch_url(url)
asyncio.timeout() (3.11+) for scoped timeouts.asyncio.CancelledError only to clean up, then re-raise.asyncio.to_thread().Load on demand:
references/foundations.md — event loop, coroutines vs tasks, TaskGroup vs gatherreferences/cancellation-timeouts.md — cancellation semantics and timeout patternsreferences/backpressure-rate-limit.md — queues, semaphores, producer/consumer, rate limitingreferences/sync-async-interop.md — to_thread, executors, avoiding hidden blockingreferences/testing.md — testing async code patterns (pytest-asyncio) and flake avoidancedata-ai
Scoped routing: Linux operator; hosts, sessions, users, services, packages, logs, containers, SSH, network paths, privilege evidence.
development
Offensive methodology for ICS/OT/SCADA environments in authorized industrial penetration testing and red team operations. Use when assessing PLCs, RTUs, HMIs, engineering workstations, historians, or field devices running Modbus, DNP3, EtherNet/IP, S7comm/S7+, Profinet, IEC 60870-5-104, BACnet, or OPC-UA. Covers passive OT network enumeration, protocol-level device interrogation, PLC coil/register read-write attacks, HMI session exploitation, historian and engineering workstation compromise, and safe escalation rules for critical infrastructure scope. Does not cover: general IT network exploitation (network-technique), physical hardware interfaces UART/JTAG/SPI (hardware-technique), wireless sensor network attacks (wireless-technique), RF/SDR signal analysis (hardware-ctf or wireless-technique), or CTF-framed ICS lab tasks (ics-ctf).
tools
Offensive methodology for authorized game security assessments, game client security research, and game-adjacent penetration testing in real-world engagements. Use when assessing game clients for cheating vulnerabilities, testing anti-cheat effectiveness, auditing game server protocols for score manipulation or economic fraud, reverse engineering game DRM or license validation, analyzing game save file protection, or assessing game mod/plugin security. Covers: process memory scanning and manipulation (Cheat Engine methodology), game binary reversing for license and DRM bypass, game network protocol analysis and packet replay, anti-cheat mechanism analysis, save file format reversing and tampering, speed hack and value injection techniques. Does NOT cover: CTF game challenges (game-ctf), game engine source code auditing (web-exploit-technique or vuln-search-technique for the backend), or general binary exploitation (pwn-ctf or reversing-technique).
development
Auth assessment: hardware/embedded methodology; UART/JTAG/SWD/SPI/I2C, firmware extraction, boot/debug paths, embedded OS evidence.