Sablier Payment Stream Creation

Overview

Create open-ended token payment streams using the Sablier Flow protocol. Flow streams accrue debt at a configurable rate per second with no predefined end date. Anyone can deposit tokens into a stream at any time to keep it solvent — no upfront funding is required. Each stream mints an NFT to the recipient.

This skill is a coordinator for payment stream creation and execution routing.

Arguments

Argument	Description
`chain_name`	EVM chain where to create the payment stream
`token_address`	ERC-20 token contract address to stream. Token symbols cannot be resolved to addresses — the user must provide the exact contract address.
`payment_details`	The streaming rate, recipient, and funding preference

Workflow

1. Confirm product fit before implementation details

Verify the user needs open-ended, rate-based token streaming with no predefined end date.
If the user needs fixed-schedule vesting, airdrop campaigns, or is unsure which product to use, route to sablier-product-selection. If this skill is unavailable, recommend installing it with:

npx skills add sablier-labs/sablier-skills --skill sablier-product-selection

2. Check requested features

Stop and call out unsupported requests before selecting an execution path.

Treat the following as unsupported by this skill and by Sablier Flow:

Streaming native tokens (ETH, BNB, AVAX, etc.). Only ERC-20 tokens can be streamed. If the user wants to stream a native token, inform them they must wrap it first (e.g. WETH) and provide the wrapped token contract address.
Tokens with more than 18 decimals. The Flow contract requires token decimals ≤ 18.
Fixed-schedule vesting with upfront deposit and defined end date. Route to sablier-create-vesting.
Launching tokens for users. Require the user to explicitly provide an existing token address as input.
Resolving token symbols (e.g. "USDC") to contract addresses. If the user provides a symbol instead of an address, ask them to provide the exact ERC-20 contract address.

3. Clarify payment details

If any of the following are missing or ambiguous from the user's input, use the AskUserQuestion tool to ask the user to clarify before proceeding:

Streaming rate (amount of tokens per time period, e.g. "1000 USDC per month")
Recipient address(es)
Whether to fund the stream upfront (determines create vs createAndDeposit)
If funding upfront: deposit amount
Start time (if not specified, defaults to immediate)

If the missing detail is the token address, use the AskUserQuestion tool to ask for the exact ERC-20 contract address and tell the user they can look it up on a blockchain explorer such as Etherscan.

Do not guess or silently apply defaults for the streaming rate, recipient, or upfront funding decision. Only proceed once all required inputs are confirmed.

If the user explicitly requests a streaming amount "per month":

Do not imply that Flow can deliver the exact same amount for each calendar month.
Before the final broadcast confirmation, show a caveat that Flow uses a fixed per-second rate, calendar months have unequal numbers of seconds, and exact calendar-month equality is not possible.
State that the requested "per month" amount will be implemented using a 30-day month approximation for the ratePerSecond calculation.
Only add this caveat when the user explicitly used "per month" in their request. Do not add it for other periods or for monthly wording introduced by the agent.

4. Infer intent before selecting references

Execution intent: user wants the agent to create a payment stream on their behalf (run CLI transactions).
Onchain integration intent: user wants developer integration guidance.

5. Validate chain support before routing

Check whether the user's desired chain is listed on Supported Chains.
If the chain is not supported, inform the user and stop execution of this skill.
If the user did not mention a chain, ask them to specify the chain.
If the user requests Solana, inform them that Sablier Flow is not available on Solana and stop.

6. Route in two steps

Classify the request as one of:
- Payment stream creation on the user's behalf
- Onchain integration guidance
- Any other integration type (frontend, backend, indexer, etc.)
If the request is any other integration type, inform the user that this skill does not support non-onchain integrations and stop.
Otherwise, follow the route below.

Intent	EVM	Solana
Payment stream creation on the user's behalf	Use evm-cli.md	Not available. Sablier Flow is EVM-only.
Onchain integration guidance	Use evm-onchain.md	Not available. Sablier Flow is EVM-only.

sablier-create-payment