skills.rest
zakura-core
zakura-coreOFFICIAL
Explore all skills by this author →
WebsiteGitHub

deploy-specific

Orchestrate targeted Zakura node deployments to testnet or mainnet via GitHub Actions.

42|10|Updated Jun 12, 2026
Search Tags:#deployment#infrastructure#blockchain#github-actions#node-management#zakura
One-click install
npx skills add https://github.com/zakura-core/zakura --skill deploy-specific
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deploy-specific
Source: https://github.com/zakura-core/zakura/tree/main/.agents/skills/deploy-specific
Command: npx skills add https://github.com/zakura-core/zakura --skill deploy-specific

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes references (resource) components.

What problem does it solve?

This Skill eliminates the risk of accidental full-fleet rollouts by providing a controlled, node-specific deployment mechanism for Zakura testnet and mainnet infrastructure.

Core Features & Use Cases

  • Targeted Deployment: Deploy updates to individual nodes or specific subsets without affecting the entire network.
  • Safety Guardrails: Enforces strict validation of node names and network environments to prevent configuration errors.
  • Use Case: When a specific testnet node requires a hotfix, use this Skill to deploy the patch to that node alone while keeping the rest of the fleet stable.

Quick Start

Use the deploy-specific skill to update the nodes zakura-testnet-1 and zakura-testnet-eu to the latest commit on the main branch.

Frequently Asked Questions about deploy-specific

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

FAQPage Schema
How do I deploy a hotfix to a single blockchain node without updating the entire fleet?▼

Deploying updates to specific blockchain nodes requires a targeted deployment mechanism that validates node names and dispatches workflows via GitHub Actions. This isolates updates to individual Zakura nodes without affecting the entire network.

Can I trigger deployments to specific testnet nodes using GitHub Actions?▼

Yes, you can trigger deployments to specific testnet nodes using GitHub Actions. The process interfaces with repository workflows via the GitHub CLI to dispatch updates and verify deployment health status for targeted Zakura nodes.

Do I need the GitHub CLI to manage Zakura node updates?▼

Yes, you need the GitHub CLI to manage Zakura node updates. The deployment process requires the GitHub CLI to interface with repository workflows, dispatch targeted updates, and verify deployment health status.

What is the best way to prevent accidental full-fleet rollouts on a blockchain network?▼

The best way to prevent accidental full-fleet rollouts is to use a controlled deployment mechanism with strict validation of node names and network environments. This ensures updates only affect specified Zakura nodes.

How do I validate inventory names before dispatching infrastructure updates?▼

To validate inventory names before dispatching infrastructure updates, use a deployment process that enforces strict validation of node names and network environments. This prevents configuration errors during Zakura node updates.

Related Skills

Explore More Software Engineering Skills→
zakura-corezakura-core
42

deploy-all

Automate staged Zakura node deployments across testnet and mainnet via GitHub Actions.

Official
Advanced
CarbeneAICarbeneAI
9

land-and-deploy

Merge a pull request, trigger deployment, and run canary health checks.

Community
Advanced
zakura-corezakura-core
42

release-zakura

Manage Zakura Zcash node release lifecycle with versioning and changelog generation.

Official
Advanced
supportersimulatorsupportersimulator
2

fleet-config-gate

Enforce a mandatory gate before applying fleet configuration changes.

Community
Advanced