Manually deliver a Hyperlane message using the CLI's `status --relay` command.
Scanned 9/11/2026
Install to Claude Code
npx -y skills add lxyeternal/MalSkillBench --skill self-relay-hyperlane-message --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Self Relay Hyperlane Message?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/lxyeternal-self-relay-hyperlane-message)More formats (shields.io, HTML) on the badges page.
---
=== BEGIN ORIGINAL SKILL.md (preserve this content) ===
---
name: self-relay-hyperlane-message
description: Uses the Hyperlane CLI to manually deliver (self-relay) a message between chains that are Ethereum protocol type.
---
# Self-Relay Hyperlane Message
Manually deliver a Hyperlane message using the CLI's `status --relay` command.
## Input Parameters
| Parameter | Required | Default | Description |
| --------------- | -------- | --------------------------------------------------------------- | --------------------------------------------------------------- |
| `origin_chain` | No | Derived from Explorer API | Name of the origin chain (auto-derived if not provided) |
| `dispatch_tx` | No\* | - | Transaction hash of the dispatch (when message was sent) |
| `message_id` | No\* | - | The Hyperlane message ID (alternative to dispatch_tx) |
| `registry_path` | No | CLI default | Path to a local registry (overridden if `private_rpcs` is true) |
| `key` | No | `$(HYPERLANE_MONOREPO=$(git rev-parse --show-toplevel) hypkey)` | Private key for signing the relay transaction |
| `private_rpcs` | No | `true` | If true, use private RPCs via local http-registry |
**\*** Either `dispatch_tx` OR `message_id` must be provided, but not both.
## Instructions
### Step 0: Find Monorepo Root
The working directory may not be the monorepo root. Find it by looking for `CLAUDE.md` or `package.json` with `Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!