About this skill

Problem

When scripts already depend on rq-wrap, direct calls can scatter parameter assembly, repeated logic, and version-specific handling across multiple files. Rq Wrap is positioned more narrowly: it is not a replacement for rq-wrap, but a wrapper layer that gives code a single entry point and keeps business logic from being tightly coupled to low-level invocation details.

Behavior and boundaries

Based on the available material, its scope stays close to wrapping rq-wrap:

Encapsulation: it centralizes how rq-wrap is invoked behind a wrapper.
Minimal surface: the version is 1.0.0, and the description only states that it is a rq-wrap wrapper, without documenting additional subsystems or complex workflows.
Fit: useful in engineering scripts that already rely on rq-wrap and want to reduce repeated call patterns.

Note that it is not the right choice if the project does not use rq-wrap, or if the need is general-purpose tooling, task orchestration, or dependency management. Because public details are limited, verify the actual local interface and constraints before adoption.

Screenshots

Use Cases

Maintain existing rq-wrap invocation scripts and consolidate scattered parameters behind one entry point
Reuse the same rq-wrap wrapper in engineering scripts to avoid duplicating call assembly logic
Add an rq-wrap adapter layer to an existing service to separate business code from low-level call details

Best For

Backend engineers maintaining rq-wrap call chains who want scattered wrappers consolidated into one entry point
Automation developers writing internal engineering scripts who need to reuse the same rq-wrap wrapper logic
Tech leads refactoring legacy call code who want to separate business logic from low-level tooling details