Chainlink VRF Skill

Overview

Route VRF requests to the simplest valid path while keeping side effects and credential exposure out of the agent runtime. Generate working VRF v2.5 code on first attempt when possible. Detect legacy V1/V2 patterns and refuse to emit them — offer migration guidance instead.

Progressive Disclosure

1. Keep this file as the default guide.
2. Read references/subscription.md only when the user wants to build a subscription-based consumer, manage a subscription, use VRFConsumerBaseV2Plus, call requestRandomWords, or handle the fulfillRandomWords callback.
3. Read references/direct-funding.md only when the user wants direct funding (no subscription), uses VRFV2PlusWrapperConsumerBase, or asks about a one-off randomness request.
4. Read references/migration-from-v2.md when you detect V1 or V2 patterns in user-supplied code (VRFConsumerBaseV2, VRFConsumerBase, positional requestRandomWords, uint64 subscription IDs, VRFV2WrapperConsumerBase, or memory randomWords in a subscription consumer) or when the user asks how to migrate.
5. Read references/billing.md only when the user asks about costs, LINK vs native payment, subscription funding, or premium percentages.
6. Read references/supported-networks.md only when the user needs coordinator addresses, wrapper addresses, LINK token addresses, or key hashes for a specific network.
7. Read references/security-and-best-practices.md only when the agent is developing consumer contracts with this skill and when the user asks about security, bias resistance, gas limit sizing, request cancellation, or production readiness.
8. Read references/official-sources.md only when the answer depends on live data the reference files do not contain.
9. Do not load reference files speculatively.

Routing