# Send K3 Blockhain Agent Skill to your agent Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually. ## Fast path - Download the package from Yavira. - Extract it into a folder your agent can access. - Paste one of the prompts below and point your agent at the extracted folder. ## Suggested prompts ### New install ```text I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete. ``` ### Upgrade existing ```text I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run. ``` ## Machine-readable fields ```json { "schemaVersion": "1.0", "item": { "slug": "k3-blockchain-agent", "name": "K3 Blockhain Agent Skill", "source": "tencent", "type": "skill", "category": "AI 智能", "sourceUrl": "https://clawhub.ai/alexgrankinukr-hash/k3-blockchain-agent", "canonicalUrl": "https://clawhub.ai/alexgrankinukr-hash/k3-blockchain-agent", "targetPlatform": "OpenClaw" }, "install": { "downloadUrl": "/downloads/k3-blockchain-agent", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=k3-blockchain-agent", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "packageFormat": "ZIP package", "primaryDoc": "SKILL.md", "includedAssets": [ "references/data-sources.md", "references/troubleshooting.md", "references/workflow-patterns.md", "references/node-types.md", "SKILL.md" ], "downloadMode": "redirect", "sourceHealth": { "source": "tencent", "slug": "k3-blockchain-agent", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-05-02T00:53:04.408Z", "expiresAt": "2026-05-09T00:53:04.408Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=k3-blockchain-agent", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=k3-blockchain-agent", "contentDisposition": "attachment; filename=\"k3-blockchain-agent-1.0.0.zip\"", "redirectLocation": null, "bodySnippet": null, "slug": "k3-blockchain-agent" }, "scope": "item", "summary": "Item download looks usable.", "detail": "Yavira can redirect you to the upstream package for this item.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/k3-blockchain-agent" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] } }, "links": { "detailUrl": "https://openagent3.xyz/skills/k3-blockchain-agent", "downloadUrl": "https://openagent3.xyz/downloads/k3-blockchain-agent", "agentUrl": "https://openagent3.xyz/skills/k3-blockchain-agent/agent", "manifestUrl": "https://openagent3.xyz/skills/k3-blockchain-agent/agent.json", "briefUrl": "https://openagent3.xyz/skills/k3-blockchain-agent/agent.md" } } ``` ## Documentation ### K3 Blockchain Agent Transform requests like "Send me daily updates about the WETH/USDC pool on Uniswap" into fully deployed workflows that fetch data, run AI analysis, and deliver reports automatically. ### Setup This skill requires the K3 Development MCP to be connected. The MCP provides tools like generateWorkflow, executeWorkflow, findAgentByFunctionality, and others that let you create and manage blockchain workflows programmatically. If the K3 MCP isn't connected yet, tell the user they need to add it before proceeding. Once connected, verify by calling listTeamMcpServerIntegrations() — this confirms the connection and shows what data source integrations (TheGraph, CoinGecko, etc.) the user's team has wired up. Every team's integrations will be different — discover what's available rather than assuming. ### How Workflow Building Works The K3 orchestrator is conversational. You describe what you want in plain language, and the orchestrator asks clarifying questions, then builds and deploys the workflow. Your job is to show up with the right information so the conversation is productive. The loop: UNDERSTAND → what does the user actually want? FIND DATA → how do we get that information into the workflow? TEST → does the data actually come back correctly? BUILD → give the orchestrator everything it needs DEPLOY → launch it and verify it works Skipping "test" is the most common mistake — you end up with a deployed workflow that returns empty data. ### Step 1: Understand the Request When a user asks for a workflow, figure out these parameters. Ask if anything is unclear — don't guess on addresses or emails. ParameterWhat to find outExamplesData targetWhat blockchain data do they need?pool metrics, token price, wallet balance, NFT dataProtocolWhich DeFi protocol or chain feature?Uniswap, Aave, SushiSwap, native transfersChainWhich blockchain?Ethereum, Arbitrum, Polygon, Base, StellarScheduleHow often / what triggers it?daily, hourly, on-demand, on wallet activity, on contract event, Telegram chatbotAnalysisWhat kind of insights?performance summary, anomaly alerts, trend report, trade signalDeliveryHow should results arrive?email, Telegram, Slack, Google SheetsActionsShould the workflow do anything?execute a swap, transfer tokens, write to a contractSpecificsAny addresses or IDs?pool address, token contract, wallet address If the user is new to DeFi, briefly explain relevant concepts as you go (what TVL means, what a liquidity pool is, etc.). Don't assume they know the jargon. ### Step 2: Find the Right Data This is the critical step. K3 has many ways to get data into a workflow, and you need to figure out which approach works for the user's specific request. ### K3 data functions These are the built-in functions for getting data into a workflow. Read references/node-types.md for full details on each. FunctionWhat it doesRead APICall any REST/GraphQL API — the most flexible optionRead Smart ContractQuery any smart contract directly on-chainRead Market DataGet token prices, volumes, market metricsRead WalletWallet balances, transfers, transaction historyRead NFTNFT collections, floor prices, traits, holdersRead GraphQuery TheGraph subgraphs with custom GraphQLRead DeploymentPull output from your own deployed code on K3AI Web ScraperExtract structured data from any web pageAI Agent with toolsAI that dynamically decides what to fetch ### How to find the data you need The goal is to figure out the best way to get the specific data the user wants. Think of it as problem-solving — there are multiple valid approaches and you should explore them: Check what the team already has — call listTeamMcpServerIntegrations() to see what MCP data sources are connected. If they have TheGraph, CoinGecko, or other integrations set up, those are the easiest path. Search for existing templates — call findAgentByFunctionality() with the user's intent. If someone already built a similar workflow, use it as a starting point. Think about which K3 function fits: Need on-chain contract data? → Read Smart Contract can query it directly Need token prices or market data? → Read Market Data has it built in Need complex DeFi metrics (TVL, volume, fees)? → Read Graph with the right subgraph, or Read API to a protocol's analytics endpoint Need wallet info? → Read Wallet for balances and history Need NFT data? → Read NFT for collections and metadata Need data from any public API? → Read API can call anything Need to scrape a website? → AI Web Scraper can extract and structure it Search the web for the right endpoint. If you need a specific protocol's data, look up {protocol name} API, {protocol name} subgraph, or {protocol name} GraphQL endpoint. Many protocols publish public APIs and subgraphs. Ask the user — they may know the API endpoint, have an API key, or know exactly which smart contract to read from. The key insight: there's rarely just one way to get the data. A Uniswap pool's TVL could come from Read Graph (subgraph query), Read API (calling an analytics endpoint), or even Read Smart Contract (reading the pool contract directly). Pick whichever is most reliable and gives you the data format you need. ### Test before you build Before constructing the full workflow, verify the data source actually returns what you expect: 1. Create a minimal test workflow with generateWorkflow() — just a trigger + one data fetch step, nothing else 2. Deploy and run it with executeWorkflow() 3. Check the output with getWorkflowRunById() (set includeWorkflowData: true) 4. If the data looks right → proceed to full build 5. If empty or wrong → try a different approach and test again This saves a lot of debugging later. A deployed workflow with bad data is worse than no workflow. ### Step 3: Build the Workflow Now give the K3 orchestrator everything it needs. Use generateWorkflow() with a detailed prompt that includes: Trigger type and schedule (e.g., "runs daily" or "triggers on wallet activity") Data source and how to query it (e.g., "use Read Graph to query pool X" or "use Read Smart Contract to get the pair's reserves") What the AI should analyze (e.g., "highlight TVL changes over 5%") Any actions to take (e.g., "execute a swap on Uniswap if condition is met") How to deliver results (e.g., "send Telegram alert" or "email the report") Any MCP integration IDs the orchestrator needs (from team integrations) Set deployWorkflow: false on the first call so you can review before deploying. The orchestrator will likely ask follow-up questions — answer them using editGeneratedWorkflow() with the same generatedWorkflowId. This back-and-forth is normal; expect 2-4 rounds. Once the configuration looks correct, call editGeneratedWorkflow() one final time with deployWorkflow: true. For the full list of available functions, triggers, AI models, and output options, read references/node-types.md. ### Step 4: Deploy and Verify After deploying: Run it manually with executeWorkflow() to trigger an immediate test Check the run with getWorkflowRuns() or getWorkflowRunById() Verify the full chain: Did data fetch? Did AI analyze? Did notification send? If something failed, use editGeneratedWorkflow() to fix it — you don't need to start over. See references/troubleshooting.md for common issues. Tell the user what happened: "Your workflow is live and will run daily. I just ran a test — here's what the first report looks like: [summary]." ### K3 MCP Tool Reference ToolWhat it doesgenerateWorkflowStart building a workflow from natural languageeditGeneratedWorkflowContinue the conversation with the orchestratorexecuteWorkflowRun a workflow manuallygetWorkflowByIdGet workflow details and configgetWorkflowRunsList execution historygetWorkflowRunByIdGet a specific run's details and outputupdateWorkflowPause/unpause a scheduled workflowfindAgentByFunctionalitySearch for existing workflow templateslistAgentTemplatesBrowse all available templatesgetAgentTemplateByIdGet details on a specific templatelistTeamMcpServerIntegrationsSee what data sources the team has connectedlistMcpServerIntegrationsBrowse all available MCP data sources ### Important Rules Always test data sources before building the full workflow. A quick test fetch saves a lot of debugging time. The orchestrator is conversational — expect multiple rounds of back-and-forth via editGeneratedWorkflow. That's how it's designed to work. Ask the user for anything you can't look up — never guess email addresses, Telegram handles, or wallet addresses. Discover team integrations — call listTeamMcpServerIntegrations() to see what's available. Every team is different. Verify workflows work before telling the user it's done. Run it, check the output, confirm delivery. Be mindful of context — don't call many K3 MCP tools at once or dump large responses. Fetch what you need, check it, move on. Use web search to find API endpoints, subgraph URLs, and smart contract addresses when you don't know them. The web is your research tool. ### Going Deeper references/node-types.md — All trigger types, data functions, AI functions, DeFi/trading actions, and notification options references/data-sources.md — How to discover and evaluate data sources for different blockchain data needs references/workflow-patterns.md — Common workflow architectures and when to use each one references/troubleshooting.md — Diagnosing and fixing common workflow issues ## Trust - Source: tencent - Verification: Indexed source record - Publisher: alexgrankinukr-hash - Version: 1.0.0 ## Source health - Status: healthy - Item download looks usable. - Yavira can redirect you to the upstream package for this item. - Health scope: item - Reason: direct_download_ok - Checked at: 2026-05-02T00:53:04.408Z - Expires at: 2026-05-09T00:53:04.408Z - Recommended action: Download for OpenClaw ## Links - [Detail page](https://openagent3.xyz/skills/k3-blockchain-agent) - [Send to Agent page](https://openagent3.xyz/skills/k3-blockchain-agent/agent) - [JSON manifest](https://openagent3.xyz/skills/k3-blockchain-agent/agent.json) - [Markdown brief](https://openagent3.xyz/skills/k3-blockchain-agent/agent.md) - [Download page](https://openagent3.xyz/downloads/k3-blockchain-agent)