Trigger Docker Image Builds

VerifiedCaution

Triggers Hyperlane Docker image build workflows via GitHub Actions (Rust agent, monorepo, Node services) and publishes to GHCR.

Sby Skills Guide Bot
DevOpsBeginner
10/30/2026
Claude Code
#docker#github-actions#ci-cd#ghcr#image-build

Recommended for

Automated summary

Triggers GitHub Actions workflows that build and publish Hyperlane Docker images (agent, monorepo, node services) to GHCR.

Strengths

  • Clear table mapping each workflow to the image it produces and its contents.
  • Provides ready-to-use `gh workflow run`, `gh run list`, and `gh run watch` commands.
  • Explains the image tag format and the `ghcr.io/hyperlane-xyz/*` registry location.
  • Documents the `include_arm64` option for multi-architecture builds.

Limitations

  • Highly specific to the Hyperlane ecosystem and its named workflows.
  • Assumes `gh` is authenticated and the user has access to the repository and GHCR.
  • Does not cover build failure diagnosis or pre-validating the requested ref.
When to use it

Use when you need to build and publish a Hyperlane Docker image from a branch, tag, or commit.

When not to use it

Use `/find-docker-image` to locate an existing image, and do not use this skill for non-Hyperlane projects.

Security analysis

Caution
Quality score84/100

The skill is transparent and does only what it documents: dispatching existing GitHub Actions workflows via the `gh` CLI and reporting run URLs. There is no destructive command, no credential exfiltration, no obfuscation, and no attempt to override agent instructions. Because it does invoke powerful network/shell tooling with side effects (publishing images to a registry) and declares no allowed-tools, it is rated caution rather than safe; impact is bounded by GitHub's own workflow permissions.

Findings
  • •No allowed-tools declared, yet the skill instructs execution of `gh workflow run`/`gh run` commands (shell/network access) without an explicit tool declaration.
  • •Triggering CI workflows publishes artifacts to a shared registry (ghcr.io/hyperlane-xyz/*), which is a legitimate but side-effecting operation; arbitrary `--ref` values flow into workflow dispatch and could build/publish untrusted branches.
  • •No validation or confirmation of the target ref/repository before dispatching builds.
  • •No allowed-tools are declared, yet the skill instructs the agent to run `gh` CLI commands (bash/network access) and publish container images to a public registry — capability is powerful but scoped and legitimate.
  • •Steps 1 and 2 both call `gh run list` for the same workflow, which is redundant but harmless.
  • •Relies on the ambient `gh` authentication token; no token handling, no exfiltration, no obfuscation, no destructive commands.
How this analysis is made

Examples

Build agent image from a branch
Build the Hyperlane agent Docker image from the release/1.2 branch and give me the GitHub Actions run URL.
Multi-arch node services build
Trigger a multi-arch build of the hyperlane-node-services image from commit abc1234.
Build all images from main
Build all Hyperlane Docker images from main and watch the runs until they finish.

name: build-docker-image description: Trigger Docker image builds for Hyperlane agent, monorepo, or node service images. Use when the user wants to build new Docker images for a branch, commit, or tag.

Trigger Docker Image Builds

Build and publish Docker images to GHCR (ghcr.io/hyperlane-xyz/*).

Workflows

| Workflow | Image(s) | Contents | | -------------------------- | ------------------------- | -------------------------------------------------------------------------------- | | rust-docker.yml | hyperlane-agent | Rust relayer, validator, scraper | | monorepo-docker.yml | hyperlane-monorepo | Full TS/Solidity monorepo | | node-services-docker.yml | hyperlane-node-services | All TS node services (rebalancer, warp-monitor, ccip-server, keyfunder, relayer) |

How to Trigger

Use gh workflow run with --ref to specify the branch, tag, or commit:

# Agent image (Rust)
gh workflow run rust-docker.yml --ref <branch>

# Monorepo image
gh workflow run monorepo-docker.yml --ref <branch>

# Node services (single unified image)
gh workflow run node-services-docker.yml --ref <branch>

# Include arm64 (multi-arch, slower)
gh workflow run rust-docker.yml --ref <branch> -f include_arm64=true

--ref defaults to main if omitted.

After Triggering

  1. Get the run URL:

    gh run list --workflow=<workflow>.yml --limit=1 --json url --jq '.[].url'
    
  2. Get the run ID (wait a few seconds after triggering for the run to appear):

    gh run list --workflow=<workflow>.yml --limit=1 --json databaseId,status,createdAt --jq '.[0]'
    
  3. Watch it:

    gh run watch <run-id>
    
  4. The resulting image tag will be <7-char-sha>-<YYYYMMDD>-<HHMMSS>, e.g. c558a9f-20260304-105241.

  5. Images are at ghcr.io/hyperlane-xyz/<image-name>:<tag>.

Instructions

  1. Ask the user which image(s) they want to build (agent, monorepo, node services, or all).
  2. Ask which branch/ref (default: main).
  3. Ask if arm64 is needed (default: no).
  4. Trigger the workflow(s) with gh workflow run.
  5. Fetch and report the run URL(s) using gh run list.
  6. Optionally watch for completion if the user wants to wait.

References

  • To find existing images instead of building, use the /find-docker-image skill.
  • See docs/docker-image-policy.md for the full Docker image policy.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/trigger-docker-image-builds-mvg6txnm/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/trigger-docker-image-builds-mvg6txnm' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/trigger-docker-image-builds-mvg6txnm/download' --output '.skill-downloads/trigger-docker-image-builds-mvg6txnm/SKILL.md.part' && mv '.skill-downloads/trigger-docker-image-builds-mvg6txnm/SKILL.md.part' '.skill-downloads/trigger-docker-image-builds-mvg6txnm/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/trigger-docker-image-builds-mvg6txnm/SKILL.md' && test -s '.skill-downloads/trigger-docker-image-builds-mvg6txnm/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/build-docker-image' && cp -R '.skill-downloads/trigger-docker-image-builds-mvg6txnm' '.claude/skills/build-docker-image'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/trigger-docker-image-builds-mvg6txnm'

openskills read 'trigger-docker-image-builds-mvg6txnm'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/trigger-docker-image-builds-mvg6txnm/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills