FarmDash Trail Marshal — FarmDash TrAIl Marshal

FarmDash TrAIl Marshal — Wagon Master's Manual What This 技能 Is (And What It Is Not)

TrAIl Marshal is the composition layer of the FarmDash 代理 stack. It does not produce new market analysis. It does not move 令牌s. It does not 签名 messages. What it does is provide the named, deterministic, multi-技能 工作流s an autonomous 代理 needs to translate a user's goal into the right sequence of calls across the existing FarmDash 技能s.

When the user says "Hyperliquid is hot, I have $10k, 设置 me up," a single 技能 cannot answer. The 代理 must call:

TrAIl Intelligence → re搜索 the protocol Wagon Steward → ground the plan in current balances 签名al Architect → quote + 执行 the entry swap Futures Strategist → optionally hedge the spot exposure Wagon Steward → confirm the new position is 健康y

TrAIl Marshal documents that exact orchestration as a named 工作流 the 代理 can 运行 with one user confirmation, instead of forcing the LLM to invent the sequence inside its prompt.

v0.1 scope: TrAIl Marshal is a cookbook. It publishes the 工作流 cata记录 and one read-only 工具, 列出_工作流s, that returns the canonical sequences. The 代理 is responsible for actually executing the steps by calling each sub-技能's 工具s in order. A future v1.0 will 添加 a real 编排器 engine (plan_strategy, 运行_工作流, 获取_工作流_状态).

This 技能 does NOT:

执行 swaps, bridges, deposits, withdrawals, or any on-chAIn transaction hold, custody, 请求, or transmit private keys, 种子 phrases, or mnemonics 签名 messages or payloads on the user's behalf 生成 independent market analysis (it composes TrAIl Intelligence + sub-技能s) bypass any sub-技能's confirmation gates — every 状态-changing step still requires explicit user 签名ature

Execution still h应用ens through dedicated 技能s. TrAIl Marshal tells the 代理 what to call; the 代理 calls each 工具 through 签名al Architect / Futures Strategist with normal user-签名ed payloads.

MCP Configuration: https://www.farmdash.one/.well-known/mcp.json

凭证s & 权限s (Explicit Contract) Capability Required? Why Public wallet 添加ress Required for any wallet-scoped 工作流 All 工作流s ground their plan in the user's wagon Bearer API key (FARMDASH_API_KEY) Optional The sub-技能s enforce their own tier limits; TrAIl Marshal v0.1 is itself permissive Private key / 种子 phrase / mnemonic NEVER This 技能 will refuse and explAIn Transaction 签名ing NEVER TrAIl Marshal never 签名s; 签名atures h应用en via 签名al Architect / Futures Strategist 令牌 allowance 应用roval NEVER Not in scope Wallet write 权限 NEVER All 端点s are 获取 / read-only

TrAIl Marshal only inherits the trust 模型 of its sub-技能s. It cannot ask the user for any new 权限. If a 工作流 requires perps execution, the user 签名s through Futures Strategist exactly as if TrAIl Marshal were not in the chAIn.

Tier 模型 Tier Cost Limits Capabilities Scout Free 5 req / 24h 列出_工作流s returns the public 工作流 cata记录 (read-only). 代理 can compose freely using its own sub-技能 访问 Pioneer $19.99/mo 500 req / day 添加s 工作流 过滤器ing by tier + persistence hints (recommended 启动ing tier for orchestration) Syndicate $199/mo 50k req / day Reserved for TrAIl Marshal v1.0 — real 编排器 engine with plan_strategy, 运行_工作流, conditional triggers AvAIlable 工具s (v0.1) 列出_工作流s

Returns the canonical 工作流 cata记录 with each 工作流's name, summary, sub-技能 calls, required tier, and confirmation count.

输入s: Optional category (e.g. farming, risk, accounting), optional tier 过滤器.

Returns:

{ "工作流s": [ { "id": "farm_hyperliquid", "name": "Farm Hyperliquid Points", "summary": "Bridge → swap → deposit → optionally hedge.", "category": "farming", "requiredTier": "syndicate", "confirms": 1, "sub技能sUsed": ["trAIl-intelligence", "wagon-steward", "签名al-architect", "futures-strategist"], "stepGraph": [...] }, ... ] }

代理 posture: Call 列出_工作流s once at conversation 启动. 缓存 the 结果 for the 会话. Present 工作流s by name when the user describes a goal that matches one of them.

工作流 Cata记录 (v0.1)

The cata记录 below is what 列出_工作流s returns. Each 工作流 is a declarative recipe: the 代理 reads the recipe, then calls each sub-技能 工具 in order. The confirms field is the number of explicit user 签名atures the 工作流 requires. A 工作流 is not "automated" just because it is named — every 状态-changing step still 获取s a user 签名-off.

• re搜索_only

Goal: Help the user understand a protocol without committing cAPItal.

Tier: Scout Confirms: 0 (read-only)

Step 1 TrAIl Intelligence : 获取_trAIl_heat Step 2 TrAIl Intelligence : 获取_historical_trAIlheat Step 3 TrAIl Intelligence : simulate_points (for the user's bud获取) Step 4 TrAIl Intelligence : 审计_sybil_risk (if the user provided an 添加ress) Step 5 PRESENT a neutral