一键在 Manus 中运行任何 Skill

flow-cli

星标5

分支1

更新时间2026年4月20日 18:57

Complete reference for the Flow CLI — the command-line tool for developing, testing, and deploying on the Flow blockchain. Covers project initialization, account management, contract deployment, transaction sending, script execution, dependency management, key generation, scheduled transactions, and emulator usage. TRIGGER when: using the Flow CLI, running flow commands, "flow accounts get", "flow accounts create", "flow init", "flow project deploy", "flow scripts execute", "flow transactions send", "flow test", "flow emulator", "flow keys generate", "flow dependencies install", "flow accounts fund", "deploy contract to testnet", "how to create a Flow account", "check account balance on Flow", "run cadence script", "send a transaction", "flow accounts add-contract", "flow accounts staking-info". DO NOT TRIGGER when: writing Cadence contract code (use cadence-lang), building React frontends (use flow-react-sdk), auditing code (use cadence-audit).

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

onflow

onflow/flow-ai-tools

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Flow CLI

The Flow CLI manages the full development lifecycle: project setup, account management, contract deployment, transaction sending, script execution, and local testing.

Quick Start

flow init my-project     # Initialize project
flow emulator            # Start local emulator
flow project deploy      # Deploy contracts
flow test                # Run tests

Navigation Map

Task	Reference
Full command list, global flags, output options, MCP server	commands-overview.md
Account commands: get, create, fund, staking, contracts	accounts.md
Project commands: init, generate, deploy, test, deps, config	project.md
Query blockchain: accounts, blocks, events, transactions, scripts	query-blockchain.md
Ready-to-use Cadence script recipes (balance, staking, NFT, EVM)	cadence-scripts.md

Key Principles

Default network is emulator — always specify --network testnet or --network mainnet for non-local operations
Use --output json when parsing output programmatically
Account names resolve via flow.json — use addresses directly when no config is present
Flow addresses accept both 0x-prefixed and raw hex formats

Companion Skills

cadence-lang — Consult when writing Cadence scripts for flow scripts execute or transactions for flow transactions send. The Cadence code must follow all language rules for access control, entitlements, and resource handling.
flow-project-setup — Consult for flow.json configuration, deployment strategies, and the overall development workflow that ties CLI commands together.
cadence-scaffold — Use to generate contracts and transactions before deploying them with the CLI.
cadence-audit — Use to review contracts before deploying with flow project deploy or flow accounts add-contract.

同仓库更多 Skills

同仓库

flow-ecosystem

onflow/flow-ai-tools

Use when a developer is building, analyzing, or shipping on Flow (Cadence or Flow EVM) and needs an ecosystem tool: on-chain analytics, metrics, a query, or a dashboard (Dune); a Flow EVM RPC endpoint, node access, or reading chain state from an app (Alchemy); or swapping tokens, adding liquidity, getting a price quote, or integrating a DEX (PunchSwap / KittyPunch). Routes the builder to the right Flow ecosystem integration and supplies how to call it (MCP server, docs, or on-chain contract). Triggers on requests like "building on Flow and need a tool for X", "how do I get Flow on-chain data or a dashboard", "what should I use to query Flow", "Flow EVM RPC or node provider", "how do I swap or add liquidity on Flow", "integrate a DEX on Flow", or "is there a Flow tool for X". Not for non-Flow chains, and not for Cadence language correctness.

2026-06-235

cadence-lang

onflow/flow-ai-tools

Comprehensive guide for writing correct, secure, and idiomatic Cadence smart contract code on the Flow blockchain. Covers language fundamentals (resources, contracts, transactions, interfaces, accounts, references, imports), access control and entitlements, capabilities, pre/post conditions, security best practices, anti-patterns to avoid, and proven design patterns. TRIGGER when: writing or debugging Cadence code, asking about Cadence syntax, access(self), access(all), entitlements, resources, move operator (<-), capabilities, references, pre/post conditions, storage paths, "how do I write cadence", "cadence error", "compile error in .cdc", "what does access(self) mean", "how do resources work", "capability-based security". DO NOT TRIGGER when: building NFT/FT token contracts (use cadence-tokens), setting up flow.json or FCL (use flow-project-setup), reviewing existing code for vulnerabilities (use cadence-audit), generating new contracts from scratch (use cadence-scaffold).

2026-05-065

cadence-scaffold

onflow/flow-ai-tools

Generate production-ready Cadence smart contracts, transactions, and DeFi transactions from scratch following security-first standards. Scaffolds secure code with proper access control, entitlements, events, storage paths, and phase discipline. TRIGGER when: creating new Cadence contracts, generating transactions, scaffolding DeFi transactions, building smart contracts from scratch, "generate contract", "create transaction", "scaffold", "new contract", "new transaction", "build a contract for", "write me a contract", "help me create a", "template for", "boilerplate", "starter contract", "create an NFT contract", "generate a transfer transaction". DO NOT TRIGGER when: reviewing or auditing existing code (use cadence-audit), asking about Cadence syntax or language rules (use cadence-lang), configuring flow.json (use flow-project-setup).

2026-05-065

cadence-testing

onflow/flow-ai-tools

Guide for writing, running, and debugging unit tests for Cadence smart contracts using the built-in Cadence Testing Framework and `flow test`. Covers test file structure (_test.cdc, setup/beforeEach/tearDown), assertions and matchers, blockchain emulation (accounts, deployments, events, time manipulation), coverage reports, CI integration, and testing patterns. TRIGGER when: writing Cadence unit tests, debugging failing tests, using Test.assert / Test.expect / Test.assertEqual / Test.expectFailure, matchers (Test.equal, Test.beGreaterThan, etc.), Test.createAccount / Test.deployContract / Test.executeTransaction / Test.executeScript in tests, Test.moveTime, Test.eventsOfType in tests, Test.reset, `flow test`, `flow test --cover`, coverage reports, `_test.cdc`, "how do I test this contract", "test is flaky", "mock a capability in a test". DO NOT TRIGGER when: writing contract or transaction code itself (use cadence-lang), generating new contracts/transactions from scratch (use cadence-scaffold), auditing non-t

2026-04-235

cadence-audit

onflow/flow-ai-tools

Comprehensive audit and review skill for Cadence smart contracts on the Flow blockchain. Identifies security vulnerabilities, bugs, code quality issues, and optimization opportunities. Produces severity-rated findings (Critical/High/Medium/Low) with actionable fixes. TRIGGER when: auditing, reviewing, or improving Cadence code, checking for security issues, performing code review on .cdc files, looking for anti-patterns or vulnerabilities, optimizing smart contract code, "review cadence", "audit cadence", "check cadence security", "validate cadence contract", "review my .cdc file", "security review", "code review", "find vulnerabilities", "check this contract", "is this code secure", "audit my project". DO NOT TRIGGER when: writing new contracts from scratch (use cadence-scaffold), asking about Cadence syntax or patterns (use cadence-lang), building token contracts (use cadence-tokens).

2026-04-205

cadence-tokens

onflow/flow-ai-tools

Guide for developing NFT and Fungible Token contracts on the Flow blockchain using Cadence. Covers NonFungibleToken and FungibleToken interface conformance, MetadataViews integration for marketplace compatibility, collection patterns, minting, standard paths, event emission, and modular NFT architectures for complex traits and evolution. TRIGGER when: building NFT contracts, FT token contracts, implementing NonFungibleToken or FungibleToken interfaces, working with MetadataViews, creating collections, minting tokens, "create an NFT", "build a token contract", "mint NFT", "NFT collection", "fungible token vault", "royalties", "MetadataViews.Display", "NonFungibleToken.Collection", "token standards", "FungibleToken.Vault". DO NOT TRIGGER when: asking about general Cadence syntax or patterns (use cadence-lang), setting up flow.json or deploying (use flow-project-setup), auditing code (use cadence-audit).

2026-04-205

name

flow-cli

description

Flow CLI

The Flow CLI manages the full development lifecycle: project setup, account management, contract deployment, transaction sending, script execution, and local testing.

Quick Start

flow init my-project     # Initialize project
flow emulator            # Start local emulator
flow project deploy      # Deploy contracts
flow test                # Run tests

Navigation Map

Task	Reference
Full command list, global flags, output options, MCP server	commands-overview.md
Account commands: get, create, fund, staking, contracts	accounts.md
Project commands: init, generate, deploy, test, deps, config	project.md
Query blockchain: accounts, blocks, events, transactions, scripts	query-blockchain.md
Ready-to-use Cadence script recipes (balance, staking, NFT, EVM)	cadence-scripts.md

Key Principles

Default network is emulator — always specify --network testnet or --network mainnet for non-local operations
Use --output json when parsing output programmatically
Account names resolve via flow.json — use addresses directly when no config is present
Flow addresses accept both 0x-prefixed and raw hex formats

Companion Skills

cadence-lang — Consult when writing Cadence scripts for flow scripts execute or transactions for flow transactions send. The Cadence code must follow all language rules for access control, entitlements, and resource handling.
flow-project-setup — Consult for flow.json configuration, deployment strategies, and the overall development workflow that ties CLI commands together.
cadence-scaffold — Use to generate contracts and transactions before deploying them with the CLI.
cadence-audit — Use to review contracts before deploying with flow project deploy or flow accounts add-contract.