polkadot-chain-connection

Creates typed clients for Polkadot chains with pluggable or preset configurations.

2|2|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/paritytech/polkadot-apps --skill polkadot-chain-connection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: polkadot-chain-connection
Source: https://github.com/paritytech/polkadot-apps/tree/main/skills/polkadot-chain-connection
Command: npx skills add https://github.com/paritytech/polkadot-apps --skill polkadot-chain-connection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Connects to Polkadot ecosystem chains using strongly-typed APIs to simplify integration and development.

Core Features & Use Cases

  • Typed access to Asset Hub, Bulletin, and Individuality via @polkadot-apps/chain-client and @polkadot-apps/descriptors.
  • BYOD and Preset (zero-config) connection modes with optional host routing for containerized environments.
  • Real-world scenarios include building multi-chain dashboards, cross-chain data queries, and contract interactions via the raw PolkadotClient.

Quick Start

Connect to Polkadot ecosystem chains by creating a typed ChainClient for assetHub, bulletin, and individuality using BYOD or preset paths.

Frequently Asked Questions about polkadot-chain-connection

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

FAQPage Schema
How do I connect to Polkadot chains with typed APIs?

You can connect to Polkadot chains with typed APIs by using getChainAPI for zero-config environments or BYOD with custom descriptors. This provides typed access to Asset Hub, Bulletin, and Individuality via the chain-client.

Do I need custom chain descriptors to connect to Asset Hub?

No, you do not need custom chain descriptors to connect to Asset Hub if you use the preset zero-config mode. Alternatively, you can use BYOD with custom descriptors for lazy loading and specific configurations.

Can I use host routing for Polkadot RPC connections in containerized environments?

Yes, you can use optional host routing for Polkadot RPC connections in containerized environments. The Skill supports configured RPC endpoints with both host and direct RPC routing methods.

What is BYOD for Polkadot chain connections?

BYOD, or Bring Your Own Descriptors, is a connection mode for Polkadot chains that allows you to supply custom chain descriptors. It enables lazy descriptor loading for presets and facilitates typed API integrations.

How do I query cross-chain data on Polkadot using a typed API?

You can query cross-chain data on Polkadot using the typed ChainClient provided by this Skill. It enables multi-chain dashboard building and cross-chain data queries by interacting with the raw PolkadotClient.

When should I use direct RPC routing instead of host routing for Polkadot clients?

You should use direct RPC routing instead of host routing for Polkadot clients when operating outside containerized environments or when custom network configurations are required. Host routing is optional and primarily targets containerized setups.