feat: add flare network skill

[fassko]

New Skill: flare

Description

Flare is an EVM-compatible L1 with enshrined data protocols.

Checklist

• Skill directory follows naming convention (lowercase, hyphens)
• SKILL.md has valid YAML frontmatter (name, description, chain, category)
• Description under 1024 characters
• Code examples are working and copy-paste ready
• Contract addresses verified onchain with "Last verified" date
• No hardcoded secrets, private keys, or RPC URLs
• Added to .claude-plugin/marketplace.json (alphabetical order)
• Tested with AI agent using realistic prompts

What LLM blind spots does this skill fix?

List 2-3 things AI agents currently get wrong about this protocol:

1. Hardcoding periphery contract addresses instead of resolving via FlareContractsRegistry.
2. Missing Flare compiler requirements (notably evmVersion: "cancun") and mixing up network-specific imports (coston2/ vs flare/ vs songbird/).
3. Treating FDC + FTSO like “normal oracles”: ignoring FDC finalization/waiting before fetching proofs, and mishandling FTSO decimals / fee paths / Coston2 test contract selection.

Testing

How did you verify the skill works correctly?

• Loaded in Claude Code and tested with prompts
• Code examples compile/run
• Contract addresses verified via cast code or eth_getCode

[vercel]

@fassko is attempting to deploy a commit to the init1's projects Team on Vercel.

A member of the Team first needs to authorize it.