flare-general

Provide consolidated Flare network, protocol, and developer tooling knowledge.

19|5|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/flare-foundation/flare-ai-skills --skill flare-general-flare-foundation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flare-general
Source: https://github.com/flare-foundation/flare-ai-skills/tree/main/skills/flare-general-skill
Command: npx skills add https://github.com/flare-foundation/flare-ai-skills --skill flare-general-flare-foundation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides general domain knowledge about the Flare network, its core protocols, and developer tooling to help answer questions and guide implementation.

Core Features & Use Cases

  • Flare overview: interoperable EVM L1 with enshrined data protocols (FTSO, FDC, FAssets, Smart Accounts, FCC/TEE).
  • Networks and access: mainnet, coston2, songbird, coston; RPC endpoints, explorers, and faucets.
  • Developer tooling guidance: Hardhat/Foundry setup, ContractRegistry patterns, EVM compatibility, and libs for contract interactions.
  • Use it for onboarding, architecture reference, and tooling setup.

Quick Start

Explore the Flare docs to learn the core protocols and network details, then apply this knowledge to start your integration.

Frequently Asked Questions about flare-general

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

FAQPage Schema
What is the Flare network and what are its core protocols?

Flare is an interoperable EVM Layer 1 network with enshrined data protocols. Its core protocols include FTSO, FDC, FAssets, Smart Accounts, and FCC/TEE, which provide decentralized data and interoperability for developers building integrations.

How do I get started with Flare developer tooling and network setup?

Flare developer tooling setup involves configuring Hardhat or Foundry for EVM compatibility, utilizing ContractRegistry patterns, and connecting to mainnet, Songbird, Coston2, or Coston via their specific RPC endpoints, chain IDs, and explorers.

Does Flare support standard EVM development environments like Hardhat and Foundry?

Yes, Flare supports EVM-compatible development environments. Developers can set up Hardhat or Foundry to deploy contracts, interact with core protocols, and use available libraries for seamless contract interactions across Flare networks.

What Flare networks, RPC endpoints, and faucets are available for testing?

Flare provides mainnet, Songbird, Coston2, and Coston networks for deployment and testing. Developers can access these networks via specific RPC endpoints and chain IDs, and use available faucets to obtain test tokens for development.

What is the ContractRegistry pattern when building on Flare?

The ContractRegistry is a core developer tooling pattern on Flare used to locate and interact with enshrined protocol contracts. It ensures integrations correctly reference active system addresses across mainnet and testnets.

When should I use FTSO versus FDC in my Flare architecture design?

Use FTSO for decentralized price and data feeds, and FDC for attesting to off-chain data. Selecting between them depends on your integration requirements for reliable external data inputs within your Flare smart contracts.