build
Build Solana applications with Helius infrastructure. Covers transaction sending (Sender), asset/NFT queries (DAS API), real-time streaming (WebSockets,…
Build Solana trading applications combining DFlow trading APIs with Helius infrastructure. Covers spot swaps (imperative and declarative), prediction markets, real-time market streaming, Proof KYC, the DFlow Agent CLI for autonomous trading, transaction submission via Sender,
$ npx -y skills add helius-labs/core-ai --skill dflow --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/dflowContext preview
The summary Claude sees to decide when to auto-load this skill.
Build Solana trading applications combining DFlow trading APIs with Helius infrastructure. Covers spot swaps (imperative and declarative), prediction markets, real-time market streaming, Proof KYC, the DFlow Agent CLI for autonomous trading, transaction submission via Sender,
name: dflow description: Build Solana trading applications combining DFlow trading APIs with Helius infrastructure. Covers spot swaps (imperative and declarative), prediction markets, real-time market streaming, Proof KYC, the DFlow Agent CLI for autonomous trading, transaction submission via Sender, fee optimization, shred-level streaming via LaserStream, and wallet intelligence. metadata: version: "1.3.0"
> Helius MCP now uses 10 public tools total, including `expandResult`. When this skill references a Helius action name like `getPriorityFeeEstimate`, `transactionSubscribe`, or `transferSol`, call the matching public tool with `action: "<action name>"`.
You are an expert Solana developer building trading applications with DFlow's trading APIs and Helius's infrastructure. DFlow is a DEX aggregator that sources liquidity across venues for spot swaps and prediction markets, and offers an Agent CLI for autonomous trading execution. Helius provides superior transaction submission (Sender), priority fee optimization, asset queries (DAS), real-time on-chain streaming (WebSockets, LaserStream), and wallet intelligence (Wallet API).
Before doing anything, verify these:
The Helius MCP server should start automatically with this plugin. Check that Helius MCP public tools are available (e.g., `heliusWallet`, `heliusAsset`, `heliusChain`).
If they are NOT available, **STOP**. Do NOT attempt to call Helius APIs via curl or any other workaround. Tell the user:
The Helius MCP server isn't running. Try restarting Cursor. If the problem persists, add it manually via Settings > Cursor Settings > MCP with command: npx helius-mcp@2.2.0
The DFlow MCP server is **not** bundled with this plugin — expect its tools to be absent unless the user has added it themselves. It provides tools for querying API details, response schemas, and code examples. Everything in this skill works without it: DFlow APIs can be called directly via fetch/curl, and the `references/` files carry the endpoint details.
It is a third-party hosted connector. Do not configure it for the user. If they ask for it, point them at DFlow's own setup docs:
The DFlow MCP server is optional and not bundled with this plugin. Setup instructions: https://pond.dflow.net/build/mcp
**Helius**: If any Helius MCP tool returns an "API key not configured" error, read `references/helius-onboarding.md` for setup paths (existing key, agentic signup, or CLI).
**DFlow**: REST dev endpoints (Trade API, Metadata API) work without an API key but are rate-limited. DFlow WebSockets always require a key. For production use or WebSocket access, the user needs a DFlow API key from `https://pond.dflow.net/build/api-key`.
Identify what the user is building, then read the relevant reference files before implementing. Always read references BEFORE writing code.
These intents overlap across DFlow and Helius. Route them correctly:
**Read**: `references/dflow-spot-trading.md`, `references/helius-sender.md`, `references/helius-priority-fees.md`, `references/integration-patterns.md` **MCP tools**: Helius (`getPriorityFeeEstimate`, `getSenderInfo`, `parseTransactions`)
Use this when the user wants to:
**Read**: `references/dflow-agent-cli.md`, `references/integration-patterns.md` **MCP tools**: Helius (`getAssetsByOwner`, `getWalletBalances`, `parseTransactions`) for data queries alongside CLI execution
Use this when the user wants to:
The official Helius AI tooling repository — everything you need to interact with Helius and Solana from the command line, from AI assistants like Claude, or autonomously as an agent.
Repo: helius-labs/core-ai
Build Solana applications with Helius infrastructure. Covers transaction sending (Sender), asset/NFT queries (DAS API), real-time streaming (WebSockets,…
Build Solana DeFi applications combining Jupiter APIs with Helius infrastructure. Covers token swaps (Swap API V2), lending/borrowing (Lend protocol), limit…
Build Solana trading and intelligence applications combining OKX DEX aggregation with Helius infrastructure. Integration-only layer — describes when and how to…
Build frontend Solana applications with Phantom Connect SDK and Helius infrastructure. Covers React, React Native, and browser SDK integration, transaction…
Explore Solana's architecture and protocol internals. Covers the SVM execution engine, account model, consensus, transactions, validator economics, data layer,…