debridge-common

Detect the runtime environment, set up MCP access, and discover wallets and signers.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/debridge-finance/debridge-skills --skill debridge-common
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debridge-common
Source: https://github.com/debridge-finance/debridge-skills/tree/main/skills/common
Command: npx skills add https://github.com/debridge-finance/debridge-skills --skill debridge-common

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ethers, viem.

What problem does it solve?

When starting a deBridge-enabled session, agents need a reliable initialization path that detects the runtime environment, configures the MCP connection, and auto-discovers signers and wallet addresses to enable safe, on-chain operations.

Core Features & Use Cases

  • Environment detection across CLI, MCP Desktop, browser, headless, and chat-only contexts.
  • Automatic MCP access setup and wallet discovery to obtain ready-to-use signer addresses.
  • Output of discovery results (wallets and signers) for downstream skills like bridge, swap, and balance checks.

Quick Start

Run this skill at startup to auto-detect your environment, set up MCP access, and discover signers.

Frequently Asked Questions about debridge-common

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

FAQPage Schema
How do I initialize a deBridge environment and discover available wallets?

To initialize a deBridge environment, run a startup skill that performs environment detection, configures MCP access, and auto-discovers signers and wallet addresses. This process outputs discovered wallets, available signers, and accessible RPC endpoints for immediate use.

Does deBridge environment detection work across CLI, headless, and browser agents?

deBridge environment detection works across CLI, MCP Desktop, browser, headless, and chat-only contexts. It establishes a consistent initialization path by detecting the runtime environment and setting up MCP connections for any initial deBridge operation.

How do I set up signers and RPC endpoints for downstream deBridge operations?

Set up signers and RPC endpoints by running environment detection and wallet discovery at startup. The process auto-discovers ready-to-use signer addresses and accessible RPC endpoints, passing these results to downstream skills like bridge, swap, and balance checks.

What's the best way to configure MCP access for deBridge on-chain operations?

The best way to configure MCP access is through automated environment detection at session startup. This reliably detects the runtime context, sets up the MCP connection, and discovers wallets to enable safe, on-chain deBridge operations.

Do I need ethers or viem to bootstrap deBridge wallet discovery?

You need ethers or viem dependencies to bootstrap deBridge wallet discovery. These libraries support the environment detection and MCP access setup processes that auto-discover signers and obtain ready-to-use wallet addresses for downstream operations.