runtime-exec

Detect Python and Node runtimes and package managers to execute scripts.

8|2|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/mikeparcewski/wicked-garden --skill runtime-exec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: runtime-exec
Source: https://github.com/mikeparcewski/wicked-garden/tree/main/skills/runtime-exec
Command: npx skills add https://github.com/mikeparcewski/wicked-garden --skill runtime-exec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides seamless runtime execution for Python and Node scripts by automatically detecting the right runtime and package manager, reducing manual setup and avoiding runtime errors.

Core Features & Use Cases

  • Automatic runtime detection: uses uv for Python when possible, with poetry and virtual environments as fallbacks, and pnpm/npm/yarn/npx for Node scripts.
  • Cross-platform execution: works on Windows, macOS, and Linux with consistent behavior.
  • Safe, auditable execution: runs from the scripts directory with diagnostics and clear fallbacks to prevent silent failures.

Quick Start

Use the runtime-exec skill to run a Python or Node script located in the scripts directory; it will automatically detect and apply the appropriate runtime.

Frequently Asked Questions about runtime-exec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically detect the right Python or Node runtime to run a script?

Automatic runtime detection identifies whether a script requires Python or Node by checking for pyproject.toml, poetry.lock, package.json, and lockfiles. It then selects the appropriate package manager, such as uv, poetry, pnpm, npm, or yarn, to execute the script without manual configuration.

Can I run Python and Node scripts consistently across Windows, macOS, and Linux?

Yes, cross-platform execution ensures Python and Node scripts run consistently across Windows, macOS, and Linux. The runtime detection logic applies the appropriate package manager and provides a safe default execution fallback to maintain reliable behavior in diverse development environments.

What's the best way to execute scripts from a dedicated directory while handling package manager fallbacks?

Executing scripts from the scripts directory is handled automatically by detecting project lockfiles and applying package manager fallbacks. For Node, it falls back from pnpm to npm to yarn to npx, and for Python, it uses uv, poetry, and .venv to ensure reliable execution.

Does this runtime detection approach work with both Poetry and uv for Python environments?

Yes, runtime detection supports both Poetry and uv for Python environments. It prioritizes uv when possible and uses poetry.lock and pyproject.toml files to identify the correct environment, falling back to local .venv directories if those package managers are unavailable.

Why do my Node scripts fail to execute when switching between different package managers?

Node scripts may fail if the correct package manager is not detected from lockfiles. This approach automatically identifies the proper manager by checking for package.json and lockfiles, applying pnpm, npm, yarn, or npx fallbacks to prevent silent execution failures.

How do I prevent silent failures when running Python and Node automation scripts?

To prevent silent failures, runtime execution provides safe, auditable execution with diagnostics and clear fallbacks. It directs scripts from the scripts directory and applies a safe default execution fallback if the primary package managers or runtimes are not found.