package-release
Automates creating deb and rpm release packages from binaries.
Install
mkdir -p .claude/skills/package-release && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2576" && unzip -o skill.zip -d .claude/skills/package-release && rm skill.zipInstalls to .claude/skills/package-release
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Package voxtype for release. Creates deb and rpm packages from binaries. Use when building distribution packages.Key capabilities
- →Build deb and rpm packages from binaries
- →Validate binary CPU instruction compatibility
- →Verify deb package structure and control fields
- →Target x86_64 or aarch64 architectures
- →Set custom package release numbers
How it works
The script automates the packaging process by wrapping binaries with fpm and rpmbuild while performing structural and instruction-set validation.
Inputs & outputs
When to use package-release
- →Creating linux distribution packages
- →Releasing voxtype updates
- →Validating binary package structure
- →Targeting specific CPU architectures
About this skill
Package Release
Build distribution packages (deb, rpm) for voxtype releases.
Prerequisites
fpm- Install withgem install fpmrpmbuild- Install withsudo dnf install rpm-buildorsudo pacman -S rpm-tools- Pre-built binaries in
releases/${VERSION}/
Quick Package
If binaries already exist:
./scripts/package.sh --skip-build ${VERSION}
Full Build + Package
Build binaries and create packages:
./scripts/package.sh ${VERSION}
Options
| Flag | Description |
|---|---|
--skip-build | Use existing binaries, don't rebuild |
--deb-only | Build only Debian package |
--rpm-only | Build only RPM package |
--no-validate | Skip package validation |
--release N | Set package release number (default: 1) |
--arch ARCH | Target architecture: x86_64 or aarch64 |
Output
Packages are created in releases/${VERSION}/:
voxtype_${VERSION}-1_amd64.debvoxtype-${VERSION}-1.x86_64.rpm
Validation
The script automatically:
- Validates binaries for CPU instruction contamination
- Checks deb package structure for duplicate fields
- Verifies required control file fields
Workflow
- Build binaries (Docker for AVX2/Vulkan, local for AVX-512)
- Verify binary versions match expected version
- Run
./scripts/package.sh --skip-build ${VERSION} - Test package installation in a VM or container
Common Issues
Binary not found:
Error: Binary not found: releases/0.4.14/voxtype-0.4.14-linux-x86_64-avx2
Build binaries first or check the version number.
fpm not found:
gem install fpm
Validation failed: Check the specific error. Usually means Docker cache is stale.
When not to use it
- →When binaries are missing from the release directory
- →When the build environment lacks fpm or rpmbuild
Prerequisites
Limitations
- →Requires specific build tools installed on the host
- →Binary validation may fail if Docker cache is stale
How it compares
This workflow automates the validation of binary architecture and package metadata compared to manual packaging commands.
Compared to similar skills
package-release side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| package-release (this skill) | 2 | 6mo | Review | Intermediate |
| gcp-cloud-run | 5 | 5mo | Review | Intermediate |
| flow-nexus-platform | 6 | 4mo | Review | Beginner |
| smithery-mcp-deployment | 8 | 8mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by peteonrails
View all by peteonrails →You might also like
gcp-cloud-run
aj-geddes
Deploy containerized applications on Google Cloud Run with automatic scaling, traffic management, and service mesh integration. Use for container-based serverless computing.
flow-nexus-platform
ruvnet
Comprehensive Flow Nexus platform management - authentication, sandboxes, app deployment, payments, and challenges
smithery-mcp-deployment
CaullenOmdahl
Best practices for creating, optimizing, and deploying MCP servers to Smithery. Use this skill when:(1) Creating new MCP servers for Smithery deployment(2) Optimizing quality scores (achieving 90/100)(3) Troubleshooting deployment issues (0/0 tools, missing annotations, low scores)(4) Migrating existing MCP servers to Smithery format(5) Understanding Smithery's schema format requirements(6) Adding workflow prompts, tool annotations, or documentation resources(7) Configuring smithery.yaml and package.json for deployment
deployment-pipeline-design
wshobson
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use when architecting deployment workflows, setting up continuous delivery, or implementing GitOps practices.
vercel-deployment
davila7
Expert knowledge for deploying to Vercel with Next.js Use when: vercel, deploy, deployment, hosting, production.
netlify-deploy
openai
Deploy web projects to Netlify using the Netlify CLI (`npx netlify`). Use when the user asks to deploy, host, publish, or link a site/repo on Netlify, including preview and production deploys.