Skip to content
Back to skills

Cross Chain

ASecurity

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.

  • 137 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added February 10, 2026
data-aisecurity

Security analysis

A100/100

Pro scans all 4 files and shows the line behind each finding

Scanned February 10, 2026

npx -y skills add omer-metin/skills-for-antigravity --skill cross-chain --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Cross Chain?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Cross Chain
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/omer-metin-cross-chain/badge)](https://www.skillsdirectory.com/skills/omer-metin-cross-chain)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
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.

Files in this skill

  • SKILL.md1.2 KB
  • references/patterns.md6.1 KB
  • references/sharp_edges.md10.4 KB
  • references/validations.md1.7 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…