qwenvoice-vendored-runtime

Coordinate vendored runtime packaging for QwenVoice with Python, ffmpeg, and MLX components.

350|30|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/PowerBeef/QwenVoice --skill qwenvoice-vendored-runtime
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qwenvoice-vendored-runtime
Source: https://github.com/PowerBeef/QwenVoice/tree/main/.agents/skills/qwenvoice-vendored-runtime
Command: npx skills add https://github.com/PowerBeef/QwenVoice --skill qwenvoice-vendored-runtime

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Update and maintain the vendored runtime, patches, and packaging flows for QwenVoice to ensure reliable, reproducible builds.

Core Features & Use Cases

  • Safe edit boundaries: treat vendored assets as generated and only modify sources that drive the flow.
  • Patch and bundle workflow: manage mlx-audio patches, Python wheel rebuilding, and ffmpeg assets.
  • Rebuild, verify, and release: coordinate runtime packaging with backend surfaces and release validation.

Quick Start

Run the vendored-runtime workflow to rebuild and verify the packaged runtime using the project’s standard scripts.

Frequently Asked Questions about qwenvoice-vendored-runtime

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

FAQPage Schema
How do I safely update a vendored runtime without breaking Python wheel builds?

To safely update a vendored runtime, treat vendored assets as generated files and only edit the repo-owned sources that drive the flow. Rebuild and verify Python wheels through standard project scripts to ensure stable packaging.

What is the best way to manage mlx-audio patches in a Python packaging workflow?

Managing mlx-audio patches involves applying changes only to repo-owned sources and validating them through the provided scripts. This ensures consistent runtime packaging and reliable builds across different environments.

How does vendoring a runtime ensure reproducible builds for ffmpeg and Python components?

Vendoring a runtime ensures reproducible builds by coordinating ffmpeg assets, Python wheel rebuilding, and release-bundle verification. Validating changes through standard patches keeps the packaged output stable across environments.

Can I edit vendored ffmpeg assets directly to fix a packaging issue?

You should not edit vendored ffmpeg assets directly. Treat them as generated outputs and modify only the underlying repo-owned sources, then run the provided scripts to rebuild and verify the runtime.

Do I need external dependencies to rebuild and verify a vendored runtime?

No external dependencies are required to run the vendored-runtime workflow. You can rebuild and verify the packaged runtime using the project's standard scripts and patches directly within your environment.

Why does my Python wheel rebuild fail after updating vendored runtime sources?

Python wheel rebuilds fail if you modify vendored assets instead of repo-owned sources. Apply changes strictly through the vendored-runtime workflow and validate using the provided patches to deliver stable builds.