dsr

Builds and releases cross-platform binaries locally when GitHub Actions is throttled.

3|1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/burningportra/agent-flywheel-plugin --skill dsr-burningportra
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dsr
Source: https://github.com/burningportra/agent-flywheel-plugin/tree/main/skills/dsr
Command: npx skills add https://github.com/burningportra/agent-flywheel-plugin --skill dsr-burningportra

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When GitHub Actions queue times exceed 10 minutes or CI is down, releases stall. This Skill provides fallback release infrastructure that builds tools locally across Linux, macOS, and Windows hosts and uploads artifacts to GitHub without waiting on cloud runners. ## Core Features & Use Cases - Throttling Detection and Fallback Pipeline: Run dsr check to detect GitHub Actions queue delays, then dsr fallback to execute the full check-build-release pipeline locally. - Cross-Platform Build Hosts: Coordinate builds across a local Linux host, a macOS machine over Tailscale SSH, and a Windows machine for native artifacts. - Supply Chain Security: Sign releases with minisign, generate SBOMs (SPDX/CycloneDX), and produce SLSA provenance for every artifact. - Use Case: A maintainer needs to ship ntm v1.5.2 but GitHub Actions is backed up. They run dsr fallback ntm 1.5.2 to build on all three hosts, sign the artifacts, and upload them to the GitHub release. ## Quick Start Use the dsr skill to check whether GitHub Actions is throttled for my repo and, if so, build and release version 1.5.2 of my tool locally.

Frequently Asked Questions about dsr

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

FAQPage Schema
How do I release software when GitHub Actions is slow or down?

Run dsr check to measure GitHub Actions queue time, then use dsr fallback <tool> <version> to build locally across configured hosts and upload artifacts to the GitHub release. The full pipeline runs without cloud runners.

How do I build binaries for macOS and Windows from a Linux machine?

dsr coordinates builds across registered hosts: a local Linux host, a macOS machine via Tailscale SSH, and a Windows machine via SSH. Use dsr health all to verify connectivity, then dsr build <tool> to compile on all targets.

Can I sign release artifacts and generate an SBOM locally?

Yes. dsr signing init creates a minisign keypair for signing and verifying files, dsr sbom generates SPDX or CycloneDX bills of materials, and dsr slsa generate produces SLSA provenance for artifacts.

Why does the dsr build fail with a dependency error?

Exit code 3 indicates missing dependencies such as gh authentication, Docker, or SSH access. Run dsr doctor --fix to diagnose issues and get suggested fixes, and verify host toolchains with dsr health check <host>.

When should I not use local release builds instead of CI?

Local builds are a fallback for throttled or unavailable CI, not a replacement. If GitHub Actions queue time is under 10 minutes, prefer the standard CI pipeline for consistent, reproducible cloud builds.