Build

Execute GitHub Actions YAML pipelines to build and publish releases on push.

111|9|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/Jahrome907/minecraft-agent-skills --skill build-jahrome907
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Build
Source: https://github.com/Jahrome907/minecraft-agent-skills/tree/main/tests/fixtures/validators/ci-release/valid
Command: npx skills add https://github.com/Jahrome907/minecraft-agent-skills --skill build-jahrome907

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the release phase of CI by running a GitHub Actions workflow that builds artifacts and publishes releases, requiring authentication tokens to distribute builds.

Core Features & Use Cases

  • Trigger CI release on pushes to the main branch with a minimal workflow.
  • Manage required secrets (MODRINTH_TOKEN, CURSEFORGE_TOKEN) securely in GitHub Actions.
  • Use cases include automated builds, artifact publishing, and quick-release cycles for Minecraft mods/assets.

Quick Start

Push changes to the main branch to trigger the Build workflow and publish the release using the configured secrets.

Frequently Asked Questions about Build

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

FAQPage Schema
How do I automate CI release workflows for Minecraft mods on GitHub?

Automate CI release workflows by triggering a GitHub Actions YAML pipeline on push to main. It builds artifacts and publishes releases to Modrinth and CurseForge using configured authentication tokens.

What secrets do I need to publish artifacts to Modrinth and CurseForge?

You must securely manage MODRINTH_TOKEN and CURSEFORGE_TOKEN secrets in GitHub Actions. These authentication tokens are required to distribute builds and publish releases to their respective platforms.

When do I need a GitHub Actions workflow for automated builds?

You need a GitHub Actions workflow for automated builds when your project requires quick-release cycles and artifact publishing immediately after code is merged to the main branch.

How do I trigger the build workflow to publish a release?

Trigger the build workflow by pushing changes to the main branch. This automatically executes the YAML pipeline to build artifacts and publish the release using the configured secrets.

Does this CI release workflow support platforms other than Modrinth and CurseForge?

The workflow specifically enforces artifact publishing steps for Modrinth and CurseForge. It applies to projects requiring automated builds where publishing to these defined platforms is needed.