flow

Name: flow
Author: basezh

15stars1forks

How to install flow?

basezh/agent-skills-on-base/flow

$npx -y skills add basezh/agent-skills-on-base --skill flow

Installs into the current project.

Summary

Flow protocol operations on Base: discover auctions, launch tokens, submit bids, claim/exit bids, deploy liquidity, and perform deployer admin actions. Use when agents must build and submit Flow transactions via the Flow API. Always preserve msg.sender ownership.

Files · 1

View on GitHub

SKILL.md

1	# Flow Protocol Skill
2
3	Flow enables permissionless token launches via Continuous Clearing Auctions (CCA) with automatic Uniswap V4 liquidity deployment on Base.
4
5	For Agents: Load only the resource you need (see decision tree below). Each resource is self-contained with all required code. API base URL: `https://api.flow.bid`
6
7	> Transaction Building: Use `POST /launches/build-tx` for token launches, `POST /bids/build-tx` for bids, `POST /claims/build-tx` for claims/exits. Pass the user's wallet address - this determines ownership. Validate wallet setup directly with Bankr API.
8
9	## Normative Language (RFC-2119)
10
11	This skill uses RFC-2119 keywords:
12	- MUST / MUST NOT: non-optional safety or correctness requirements
13	- SHOULD / SHOULD NOT: recommended defaults that can be overridden with clear reason
14	- MAY: optional behavior
15
16	If instructions conflict, follow in this order:
17	1. Safety requirements (`MUST`)
18	2. Ownership correctness (`msg.sender`, wallet identity)
19	3. Endpoint/schema correctness from `references/constants-and-schemas.md`
20	4. UX conventions
21
22	For every confirmed on-chain transaction, agents MUST include a BaseScan link in the user-facing confirmation message: `https://basescan.org/tx/{txHash}`.
23
24	> UX Guideline: Agents SHOULD NOT display raw transaction data (hex-encoded calldata, `transactions` arrays from build-tx responses) during user confirmations. Summarize the action in plain language (e.g., "Bid 500 USDC at $45k max FDV on $TOKEN"). Only show raw transaction data if the user explicitly requests it.
25
26	## Overview
27
28	- Continuous Clearing Auction (CCA): Fair price discovery where tokens release gradually over time
29	- Graduation: Auction succeeds when minimum raise threshold is met (configurable by deployer, default 2000 USDC for USDC auctions)
30	- Liquidity Deployment: Upon graduation, raised funds + tokens automatically seed a Uniswap V4 pool
31	- Base Network: All operations on Base (Chain ID: 8453)
32
33	---
34
35	## Prerequisites
36
37	Before using Flow, ensure:
38
39	- [ ] Wallet configured - Bankr or equivalent (see `resources/setup.md`)
40	- [ ] ETH for gas - ~0.001 ETH minimum on Base
41	- [ ] USDC for bidding - If participating in auctions (no minimum amount)
42	- [ ] Security reviewed - Read `security.md` for risk awareness
43
44	\| Network \| Chain ID \| Block Time \| Default Currency \|
45	\|---------\|----------\|------------\|------------------\|
46	\| Base \| 8453 \| ~2s \| USDC \|
47
48	---
49
50	## Cron Job Configuration
51
52	For automated operations (scheduled bids, claims, etc.), agents must use the correct session configuration to access blockchain tools:
53
54	\| Setting \| Required Value \| Why \|
55	\|---------\|----------------\|-----\|
56	\| `sessionTarget` \| `"main"` \| Grants access to Bankr and blockchain tools \|
57	\| `payload.kind` \| `"systemEvent"` \| Required for main session execution \|
58
59	> CRITICAL: Using `sessionTarget: "isolated"` will cause blockchain operations to fail silently - the agent won't have access to wallet providers like Bankr.
60
61	### Two-Part Cron Job System
62
63	To prevent API overload at auction start time, agents MUST use a two-part system for scheduled bids:
64
65	1. At schedule time: Call `/bids/build-tx` and store the pre-built transactions in the cron job payload
66	2. At execution time: Submit the pre-built transactions directly to Bankr (no Flow API call needed)
67
68	This distributes API load across scheduling times rather than concentrating it at auction start.
69
70	See `resources/submit-bid.md` for complete cron job examples with correct configuration.
71
72	---
73
74	## Resources
75
76	Access detailed implementation guides in this directory:
77
78	\| Resource \| Path \| Description \|
79	\|----------\|------\|-------------\|
80	\| Discover Auctions \| `https://flow.bid/skill/resources/discover-auctions.md` \| Find auctions using the Flow API \|
81	\| Launch Token \| `https://flow.bid/skill/resources/launch.md` \| Launch a token (default or custom params) \|
82	\| Submit Bid \| `https://flow.bid/skill/resources/submit-bid.md` \| Bid submission and trust assessment \|
83	\| Deploy Liquidity \| `https://flow.bid/skill/resources/deploy-liquidity.md` \| Permissionless liquidity deployment \|
84	\| Claim Tokens \| `https://flow.bid/skill/resources/claim-tokens.md` \| Token claiming with checkpoint hints \|
85	\| Deployer Admin \| `https://flow.bid/skill/resources/deployer-admin.md` \| Claim vesting, collect fees, transfer roles \|
86
87	### Canonical References
88
89	\| Reference \| Path \| Description \|
90	\|----------\|------\|-------------\|
91	\| Constants & Schemas \| `https://flow.bid/skill/references/constants-and-schemas.md` \| Single source of truth: addresses, selectors, endpoint catalog, canonical response shapes \|
92	\| Execution Contract \| `https://flow.bid/skill/references/execution-contract.md`

People who liked this also viewed

6 picks

Type

flow

15stars1forks

View on GitHub

How to install flow?

basezh/agent-skills-on-base/flow

$npx -y skills add basezh/agent-skills-on-base --skill flow

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Flow Protocol Skill
2
3	Flow enables permissionless token launches via Continuous Clearing Auctions (CCA) with automatic Uniswap V4 liquidity deployment on Base.
4
5	For Agents: Load only the resource you need (see decision tree below). Each resource is self-contained with all required code. API base URL: `https://api.flow.bid`
6
7	> Transaction Building: Use `POST /launches/build-tx` for token launches, `POST /bids/build-tx` for bids, `POST /claims/build-tx` for claims/exits. Pass the user's wallet address - this determines ownership. Validate wallet setup directly with Bankr API.
8
9	## Normative Language (RFC-2119)
10
11	This skill uses RFC-2119 keywords:
12	- MUST / MUST NOT: non-optional safety or correctness requirements
13	- SHOULD / SHOULD NOT: recommended defaults that can be overridden with clear reason
14	- MAY: optional behavior
15
16	If instructions conflict, follow in this order:
17	1. Safety requirements (`MUST`)
18	2. Ownership correctness (`msg.sender`, wallet identity)
19	3. Endpoint/schema correctness from `references/constants-and-schemas.md`
20	4. UX conventions
21
22	For every confirmed on-chain transaction, agents MUST include a BaseScan link in the user-facing confirmation message: `https://basescan.org/tx/{txHash}`.
23
24	> UX Guideline: Agents SHOULD NOT display raw transaction data (hex-encoded calldata, `transactions` arrays from build-tx responses) during user confirmations. Summarize the action in plain language (e.g., "Bid 500 USDC at $45k max FDV on $TOKEN"). Only show raw transaction data if the user explicitly requests it.
25
26	## Overview
27
28	- Continuous Clearing Auction (CCA): Fair price discovery where tokens release gradually over time
29	- Graduation: Auction succeeds when minimum raise threshold is met (configurable by deployer, default 2000 USDC for USDC auctions)
30	- Liquidity Deployment: Upon graduation, raised funds + tokens automatically seed a Uniswap V4 pool
31	- Base Network: All operations on Base (Chain ID: 8453)
32
33	---
34
35	## Prerequisites
36
37	Before using Flow, ensure:
38
39	- [ ] Wallet configured - Bankr or equivalent (see `resources/setup.md`)
40	- [ ] ETH for gas - ~0.001 ETH minimum on Base
41	- [ ] USDC for bidding - If participating in auctions (no minimum amount)
42	- [ ] Security reviewed - Read `security.md` for risk awareness
43
44	\| Network \| Chain ID \| Block Time \| Default Currency \|
45	\|---------\|----------\|------------\|------------------\|
46	\| Base \| 8453 \| ~2s \| USDC \|
47
48	---
49
50	## Cron Job Configuration
51
52	For automated operations (scheduled bids, claims, etc.), agents must use the correct session configuration to access blockchain tools:
53
54	\| Setting \| Required Value \| Why \|
55	\|---------\|----------------\|-----\|
56	\| `sessionTarget` \| `"main"` \| Grants access to Bankr and blockchain tools \|
57	\| `payload.kind` \| `"systemEvent"` \| Required for main session execution \|
58
59	> CRITICAL: Using `sessionTarget: "isolated"` will cause blockchain operations to fail silently - the agent won't have access to wallet providers like Bankr.
60
61	### Two-Part Cron Job System
62
63	To prevent API overload at auction start time, agents MUST use a two-part system for scheduled bids:
64
65	1. At schedule time: Call `/bids/build-tx` and store the pre-built transactions in the cron job payload
66	2. At execution time: Submit the pre-built transactions directly to Bankr (no Flow API call needed)
67
68	This distributes API load across scheduling times rather than concentrating it at auction start.
69
70	See `resources/submit-bid.md` for complete cron job examples with correct configuration.
71
72	---
73
74	## Resources
75
76	Access detailed implementation guides in this directory:
77
78	\| Resource \| Path \| Description \|
79	\|----------\|------\|-------------\|
80	\| Discover Auctions \| `https://flow.bid/skill/resources/discover-auctions.md` \| Find auctions using the Flow API \|
81	\| Launch Token \| `https://flow.bid/skill/resources/launch.md` \| Launch a token (default or custom params) \|
82	\| Submit Bid \| `https://flow.bid/skill/resources/submit-bid.md` \| Bid submission and trust assessment \|
83	\| Deploy Liquidity \| `https://flow.bid/skill/resources/deploy-liquidity.md` \| Permissionless liquidity deployment \|
84	\| Claim Tokens \| `https://flow.bid/skill/resources/claim-tokens.md` \| Token claiming with checkpoint hints \|
85	\| Deployer Admin \| `https://flow.bid/skill/resources/deployer-admin.md` \| Claim vesting, collect fees, transfer roles \|
86
87	### Canonical References
88
89	\| Reference \| Path \| Description \|
90	\|----------\|------\|-------------\|
91	\| Constants & Schemas \| `https://flow.bid/skill/references/constants-and-schemas.md` \| Single source of truth: addresses, selectors, endpoint catalog, canonical response shapes \|
92	\| Execution Contract \| `https://flow.bid/skill/references/execution-contract.md`

People who liked this also viewed

6 picks

Type