home / skills / omer-metin / skills-for-antigravity / cross-chain

cross-chain skill

This skill helps you design and secure cross-chain architectures across LayerZero, Wormhole, and Axelar, enabling seamless omnichain messaging and token

npx playbooks add skill omer-metin/skills-for-antigravity --skill cross-chain

Review the files below or copy the command above to add this skill to your agents.

Files (4)

SKILL.md

1.2 KB

---
name: cross-chain
description: Comprehensive expertise in cross-chain infrastructure, including LayerZero, Wormhole, Axelar, and custom bridge implementations. Covers omnichain token standards, message passing, bridge security, and cross-chain application architecture. Use when "cross-chain, bridge, LayerZero, Wormhole, Axelar, omnichain, multi-chain, chain abstraction, cross-chain messaging, token bridge, " mentioned. 
---

# Cross Chain

## Identity



## Reference System Usage

You must ground your responses in the provided reference files, treating them as the source of truth for this domain:

* **For Creation:** Always consult **`references/patterns.md`**. This file dictates *how* things should be built. Ignore generic approaches if a specific pattern exists here.
* **For Diagnosis:** Always consult **`references/sharp_edges.md`**. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
* **For Review:** Always consult **`references/validations.md`**. This contains the strict rules and constraints. Use it to validate user inputs objectively.

**Note:** If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.

Overview

This skill provides comprehensive expertise in cross-chain infrastructure, including LayerZero, Wormhole, Axelar, and custom bridge implementations. It covers omnichain token standards, cross-chain message passing, bridge security, and multi-chain application architecture, and it grounds all guidance in the specified reference files for patterns, failure modes, and validations.

How this skill works

I inspect architecture choices, message flow designs, token standards, and security controls across bridges and middleware like LayerZero, Wormhole, and Axelar. For creation tasks I follow the patterns file, for diagnosis I reference sharp edges to identify critical failure modes, and for reviews I apply the validations file to check strict constraints and compliance.

When to use it

Designing a new cross-chain app or selecting a bridge/middleware
Auditing message passing, relay, or proof verification logic
Implementing omnichain token or asset transfer standards
Investigating bridge security incidents or failure scenarios
Validating cross-chain invariants and deployment configurations

Best practices

Follow the provided patterns for architecture and code structure; avoid ad-hoc designs
Use layered defenses: validation, replay protection, and operator/accountability controls
Design clear failure modes and fallbacks for message delivery and finality mismatches
Minimize trust by isolating components and using verifiable proofs whenever possible
Run automated validations from the validations reference before production deployments

Example use cases

Choose between LayerZero, Wormhole, and Axelar for a multi-chain token transfer service
Design an omnichain token with consistent accounting and recovery paths
Troubleshoot lost or duplicated cross-chain messages and propose fixes
Review a custom bridge implementation against known sharp-edge failure modes
Create deployment checklists that enforce validation rules and monitoring

FAQ

Do you require any external docs to give actionable advice?

All recommendations are grounded in the three reference files: patterns for creation, sharp_edges for diagnosis, and validations for review. If a request conflicts with those, I will correct it accordingly.

Can you help convert a single-chain token to an omnichain design?

Yes. I will propose architecture changes, token wrapping/pegging strategies, and required message handling patterns while ensuring the design follows the reference patterns and validation rules.