download-release-artifacts

Downloads firmware hex files and configurator builds for a specified INAV release via GitHub CLI.

4|2|Updated Nov 30, 2025
One-click install
npx skills add https://github.com/sensei-hacker/inav-claude --skill download-release-artifacts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: download-release-artifacts
Source: https://github.com/sensei-hacker/inav-claude/tree/main/.claude/skills/download-release-artifacts
Command: npx skills add https://github.com/sensei-hacker/inav-claude --skill download-release-artifacts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the tedious and error-prone process of downloading firmware hex files and configurator builds from various sources for an INAV release.

Core Features & Use Cases

  • Firmware Download: Automatically fetch INAV firmware hex files from nightly releases.
  • Configurator Download: Retrieve INAV Configurator builds from GitHub Actions CI.
  • File Renaming: Standardize downloaded file names to match release conventions, removing CI suffixes.
  • Use Case: A release manager needs to gather all necessary firmware and configurator files for the upcoming 9.0.0-RC2 release, ensuring consistent naming and verifying file counts.

Quick Start

Download all release artifacts for INAV version 9.0.0-RC2.

Frequently Asked Questions about download-release-artifacts

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

FAQPage Schema
How do I automate downloading firmware and configurator builds from GitHub releases?

Automate firmware and configurator downloads by using GitHub CLI to fetch release artifacts, rename files to match conventions, and organize outputs by version. This eliminates manual retrieval and ensures consistent file naming across nightly releases and release candidates.

Can I download INAV firmware hex files and configurator builds for specific release versions?

Yes, you can download INAV firmware hex files and configurator builds for named releases by specifying the version. The process fetches assets from GitHub, verifies file counts, and structures downloads organized by platform—Linux, macOS, and Windows.

What's the best way to manage release artifacts across multiple platforms during CI workflows?

Manage release artifacts by automating discovery of GitHub releases, fetching platform-specific builds via GitHub CLI, standardizing file names by removing CI suffixes, and packaging outputs under a versioned directory structure for repeatable release management.

How do I verify and rename downloaded firmware files to match release conventions?

Verify downloaded firmware by counting fetched hex files and rename them to match release standards by stripping CI-generated suffixes. This ensures consistent naming conventions across nightly releases and release candidate builds.

Do I need GitHub CLI to download and organize release artifacts?

GitHub CLI is the prerequisite for fetching release assets and discovering releases programmatically. It enables automated discovery, asset retrieval, and verification workflows that integrate with CI pipelines for release management.