Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Productivity
Vincent - Trading Engine
Strategy-driven automated trading for Polymarket. Use this skill when users want to create trading strategies, set stop-loss/take-profit/trailing stop rules,...
skill openclawclawhub Free
Strategy-driven automated trading for Polymarket. Use this skill when users want to create trading strategies, set stop-loss/take-profit/trailing stop rules,...
โฌ 0 downloads โ
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- 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.
New install
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
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.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.69
Provenance
- Publisher
- glitch003
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Vincent Trading Engine - Strategy-Driven Automated Trading
Use this skill to create and manage automated trading strategies for Polymarket prediction markets and HyperLiquid perpetuals/spot. The Trading Engine combines driver-based monitoring (web search, Twitter, newswire, price feeds) with a signal pipeline and LLM-powered decision-making to automatically trade based on your thesis. It also includes standalone stop-loss, take-profit, and trailing stop rules that work without the LLM. All commands use the @vincentai/cli package.
How It Works
The Trading Engine is a unified system with two modes: LLM-Powered Strategies โ Create a versioned strategy with a structured thesis, weighted drivers (web search keywords, Twitter accounts, newswire topics, price triggers), and an escalation policy. When drivers detect new information, signals are scored and batched. When the escalation threshold is met, an LLM (Claude via OpenRouter) evaluates the signals against your thesis and decides whether to trade, update the thesis, set protective orders, or alert you. Standalone Trade Rules โ Set stop-loss, take-profit, and trailing stop rules on positions. These execute automatically when price conditions are met โ no LLM involved. Architecture: Integrated into the Vincent backend (no separate service to run) Strategy endpoints under /api/skills/polymarket/strategies/... Trade rule endpoints under /api/skills/polymarket/rules/... HyperLiquid rules use venue: "hyperliquid" and route through the HL adapter Uses the same API key as the Polymarket or HyperLiquid skill (depending on venue) All trades go through Vincent's policy-enforced pipeline LLM costs are metered and deducted from the user's credit balance Every LLM invocation is recorded with full audit trail (tokens, cost, actions, duration)
Security Model
LLM cannot bypass policies โ all trades go through the venue's policy-enforced skill (polymarketSkill.placeBet() or hyperliquidSkill.trade()) which enforces spending limits, approval thresholds, and allowlists Backend-side LLM key โ the OpenRouter API key never leaves the server. Agents and users cannot invoke the LLM directly Credit gating โ no LLM invocation without sufficient credit balance Tool constraints โ the LLM's available tools are controlled by the strategy's config.tools settings. If canTrade: false, the trade tool is not provided Rate limiting โ max concurrent LLM invocations is capped to prevent runaway costs Audit trail โ every invocation is recorded with full prompt, response, actions, cost, and duration No private keys โ the Trading Engine uses the Vincent API for all trades. Private keys stay on Vincent's servers
Core Concepts
Instrument: A tradeable asset on a venue. Defined by id, type (stock, perp, swap, binary, option), venue, and optional constraints (leverage, margin, liquidity, fees). Thesis: Your directional view โ estimate (target price/value), direction (long/short/neutral), confidence (0โ1), and reasoning. Driver: A named information source that feeds the signal pipeline. Each driver has a weight, direction (bullish/bearish/contextual), and monitoring config (entities, keywords, embedding anchor, sources, polling interval). Escalation Policy: Controls when the LLM is woken up. signalScoreThreshold (minimum score to batch), highConfidenceThreshold (score that triggers immediate wake), maxWakeFrequency (e.g. "1 per 15m"), batchWindow (e.g. "5m"). Trade Rules: Entry rules (min edge, order type), exit rules (thesis invalidation triggers), auto-actions (stop-loss, take-profit, trailing stop, price delta triggers), and sizing rules (method, max position, portfolio %, max trades/day).
Signal Pipeline
Strategies process information through a 6-layer pipeline: Ingest โ Raw data from driver sources (web search, Twitter, newswire, price feeds, RSS, Reddit, on-chain, filings, options flow) Filter โ Deduplication and relevance filtering. Drops signals already seen or below quality threshold Score โ Each signal is scored (0โ1) based on driver weight, embedding similarity to the anchor, and entity/keyword matches Escalate โ Scored signals are batched according to the escalation policy. Low-score signals accumulate in a batch window; high-confidence signals trigger immediate LLM wake LLM โ The LLM evaluates batched signals against the current thesis. It can update the thesis, issue trade decisions, update driver states, or take no action Execute โ Trade decisions pass through policy enforcement and are routed to the appropriate venue adapter for execution
Strategy Lifecycle
Strategies follow a versioned lifecycle: DRAFT โ ACTIVE โ PAUSED โ ARCHIVED DRAFT: Can be edited. Not yet monitoring or invoking the LLM. ACTIVE: Drivers are running. New signals trigger the pipeline. PAUSED: Monitoring is stopped. Can be resumed. ARCHIVED: Permanently stopped. Cannot be reactivated. To iterate on a strategy, duplicate it as a new version (creates a new DRAFT with incremented version number and the same config).
Create a Strategy
npx @vincentai/cli@latest trading-engine create-strategy \ --key-id <KEY_ID> \ --name "BTC Momentum" \ --config '{ "instruments": [ { "id": "btc-usd-perp", "type": "perp", "venue": "polymarket" }, { "id": "BTC", "type": "perp", "venue": "hyperliquid" } ], "thesis": { "estimate": 105000, "direction": "long", "confidence": 0.7, "reasoning": "ETF inflows accelerating, halving supply shock imminent" }, "drivers": [ { "name": "ETF Flow Monitor", "weight": 2.0, "direction": "bullish", "monitoring": { "entities": ["BlackRock", "Fidelity"], "keywords": ["bitcoin ETF", "BTC inflow"], "embeddingAnchor": "Bitcoin ETF institutional inflows", "sources": ["web_search", "newswire"] } }, { "name": "Crypto Twitter", "weight": 1.0, "direction": "contextual", "monitoring": { "entities": ["@BitcoinMagazine", "@saborskycnbc"], "keywords": ["bitcoin", "BTC"], "sources": ["twitter"] } } ], "escalation": { "signalScoreThreshold": 0.3, "highConfidenceThreshold": 0.8, "maxWakeFrequency": "1 per 15m", "batchWindow": "5m" }, "tradeRules": { "entry": { "minEdge": 0.05, "orderType": "limit", "limitOffset": 0.01 }, "autoActions": { "stopLoss": -0.10, "takeProfit": 0.25, "trailingStop": -0.05 }, "exit": { "thesisInvalidation": ["ETF outflows exceed $500M/week"] }, "sizing": { "method": "edgeScaled", "maxPosition": 500, "maxPortfolioPct": 20, "maxTradesPerDay": 5, "minTimeBetweenTrades": "30m" } }, "notifications": { "onTrade": true, "onThesisChange": true, "channel": "none" } }' Parameters: --name: Strategy name --config: Full strategy config JSON (see Core Concepts above for structure) --data-source-secret-id: Optional DATA_SOURCES secret ID for driver monitoring API calls --poll-interval: Polling interval in minutes for driver monitoring (default: 15)
List Strategies
npx @vincentai/cli@latest trading-engine list-strategies --key-id <KEY_ID>
Get Strategy Details
npx @vincentai/cli@latest trading-engine get-strategy --key-id <KEY_ID> --strategy-id <STRATEGY_ID>
Update a Strategy
Update a DRAFT strategy. Pass only the fields you want to change โ config is a partial object. npx @vincentai/cli@latest trading-engine update-strategy --key-id <KEY_ID> --strategy-id <STRATEGY_ID> \ --name "Updated Name" --config '{ "thesis": { "confidence": 0.8, "reasoning": "Updated reasoning" } }' Parameters: --strategy-id: Strategy ID (required) --name: New strategy name --config: Partial strategy config JSON โ only include fields to update --data-source-secret-id: DATA_SOURCES secret ID --poll-interval: New polling interval in minutes
Activate a Strategy
Starts driver monitoring and signal pipeline processing. Strategy must be in DRAFT status. npx @vincentai/cli@latest trading-engine activate --key-id <KEY_ID> --strategy-id <STRATEGY_ID>
Pause a Strategy
Stops monitoring. Strategy must be ACTIVE. npx @vincentai/cli@latest trading-engine pause --key-id <KEY_ID> --strategy-id <STRATEGY_ID>
Resume a Strategy
Resumes monitoring. Strategy must be PAUSED. npx @vincentai/cli@latest trading-engine resume --key-id <KEY_ID> --strategy-id <STRATEGY_ID>
Archive a Strategy
Permanently stops a strategy. Cannot be undone. npx @vincentai/cli@latest trading-engine archive --key-id <KEY_ID> --strategy-id <STRATEGY_ID>
Duplicate a Strategy (New Version)
Creates a new DRAFT with the same config, incremented version number, and a link to the parent version. npx @vincentai/cli@latest trading-engine duplicate-strategy --key-id <KEY_ID> --strategy-id <STRATEGY_ID>
View Version History
See all versions of a strategy lineage. npx @vincentai/cli@latest trading-engine versions --key-id <KEY_ID> --strategy-id <STRATEGY_ID>
View LLM Invocation History
See the LLM decision log for a strategy โ what data triggered it, what the LLM decided, what actions were taken, and the cost. npx @vincentai/cli@latest trading-engine invocations --key-id <KEY_ID> --strategy-id <STRATEGY_ID> --limit 20
View Cost Summary
See aggregate LLM costs for all strategies under a secret. npx @vincentai/cli@latest trading-engine costs --key-id <KEY_ID>
View Performance Metrics
See performance metrics for a strategy: P&L, win rate, trade count, and per-instrument breakdown. npx @vincentai/cli@latest trading-engine performance --key-id <KEY_ID> --strategy-id <STRATEGY_ID>
Driver Configuration
Web Search Drivers Add a driver with "sources": ["web_search"]. The engine periodically searches Brave for the driver's keywords and triggers the signal pipeline when new results appear. { "name": "AI News Monitor", "weight": 1.5, "direction": "bullish", "monitoring": { "keywords": ["AI tokens", "GPU shortage", "prediction market regulation"], "embeddingAnchor": "AI technology investment trends", "sources": ["web_search"] } } Each keyword is searched independently. Results are deduplicated โ the same URLs won't trigger the pipeline twice. Twitter Drivers Add a driver with "sources": ["twitter"]. The engine periodically checks the specified entities for new tweets. { "name": "Crypto Twitter", "weight": 1.0, "direction": "contextual", "monitoring": { "entities": ["@DeepSeek", "@nvidia", "@OpenAI"], "keywords": ["AI", "GPU"], "sources": ["twitter"] } } Tweets are deduplicated by tweet ID โ only genuinely new tweets trigger the pipeline. Newswire Drivers (Finnhub) Add a driver with "sources": ["newswire"]. The engine periodically polls Finnhub's market news API and triggers the pipeline when new headlines matching your keywords appear. { "name": "Market News", "weight": 1.5, "direction": "contextual", "monitoring": { "keywords": ["artificial intelligence", "GPU shortage", "semiconductor"], "sources": ["newswire"] } } Headlines and summaries are matched case-insensitively. Articles are deduplicated by headline hash with a sliding window. Note: Requires a FINNHUB_API_KEY env var on the server. Finnhub's free tier allows 60 API calls/min. No per-call credit deduction. Price Triggers Price triggers are evaluated in real-time via the Polymarket WebSocket feed. When a price condition is met, the signal pipeline is invoked with the price data. Trigger types: ABOVE โ triggers when price exceeds a threshold BELOW โ triggers when price drops below a threshold CHANGE_PCT โ triggers on a percentage change from reference price Price triggers are one-shot: once fired, they're marked as consumed. The LLM can create new triggers if needed.
Thesis Best Practices
The thesis is your structured directional view. Good theses include: A clear estimate: Target price or value the market should reach A confidence level: Start at 0.5โ0.7 and let the LLM adjust as new data arrives Specific reasoning: "ETF inflows accelerating, halving supply shock imminent" is better than "BTC will go up" Explicit invalidation conditions: Use tradeRules.exit.thesisInvalidation to define what would break your thesis
LLM Available Tools
When the LLM is invoked, it can use these tools (depending on strategy config): ToolDescriptionRequiresplace_tradeBuy or sell a positioncanTrade: true in trade rulesset_stop_lossSet a stop-loss rule on a positioncanSetRules: true in trade rulesset_take_profitSet a take-profit rulecanSetRules: true in trade rulesset_trailing_stopSet a trailing stopcanSetRules: true in trade rulesalert_userSend an alert without tradingAlways availableno_actionDo nothing (with reasoning)Always available
Cost Tracking
Every LLM invocation is metered: Token costs: Input and output tokens are priced per the model's rate Deducted from credit balance: Same pool as data source credits (dataSourceCreditUsd) Pre-flight check: If insufficient credit, the invocation is skipped and logged Data source costs: Brave Search ($0.005/call) and Twitter ($0.005-$0.01/call) are also metered. Finnhub newswire calls are free (no credit deduction) Typical LLM invocation cost: $0.05โ$0.30 depending on context size.
Part 2: Standalone Trade Rules
Trade rules execute automatically when price conditions are met โ no LLM involved. These are stop-loss, take-profit, and trailing stop rules that protect your positions.
Check Worker Status
npx @vincentai/cli@latest trading-engine status --key-id <KEY_ID> # Returns: worker status, active rules count, last sync time, circuit breaker state
Create a Stop-Loss Rule
Automatically sell a position if price drops below a threshold: # Polymarket โ triggerPrice is 0โ1 (outcome token price) npx @vincentai/cli@latest trading-engine create-rule --key-id <KEY_ID> \ --market-id 0x123... --token-id 456789 \ --rule-type STOP_LOSS --trigger-price 0.40 # HyperLiquid โ triggerPrice is absolute USD price, marketId and tokenId are the coin name npx @vincentai/cli@latest trading-engine create-rule --key-id <KEY_ID> \ --venue hyperliquid --market-id BTC --token-id BTC \ --rule-type STOP_LOSS --trigger-price 95000 Parameters: --venue: polymarket (default) or hyperliquid --market-id: Polymarket condition ID, or coin name for HyperLiquid (e.g. BTC, ETH) --token-id: Polymarket outcome token ID, or coin name for HyperLiquid --rule-type: STOP_LOSS (sells if price <= trigger), TAKE_PROFIT (sells if price >= trigger), or TRAILING_STOP --trigger-price: Price threshold โ 0 to 1 for Polymarket, absolute USD price for HyperLiquid
Create a Take-Profit Rule
Automatically sell a position if price rises above a threshold: # Polymarket npx @vincentai/cli@latest trading-engine create-rule --key-id <KEY_ID> \ --market-id 0x123... --token-id 456789 \ --rule-type TAKE_PROFIT --trigger-price 0.75 # HyperLiquid npx @vincentai/cli@latest trading-engine create-rule --key-id <KEY_ID> \ --venue hyperliquid --market-id ETH --token-id ETH \ --rule-type TAKE_PROFIT --trigger-price 4500
Create a Trailing Stop Rule
A trailing stop moves the stop price up as the price rises: # Polymarket npx @vincentai/cli@latest trading-engine create-rule --key-id <KEY_ID> \ --market-id 0x123... --token-id 456789 \ --rule-type TRAILING_STOP --trigger-price 0.45 --trailing-percent 5 # HyperLiquid npx @vincentai/cli@latest trading-engine create-rule --key-id <KEY_ID> \ --venue hyperliquid --market-id SOL --token-id SOL \ --rule-type TRAILING_STOP --trigger-price 170 --trailing-percent 5 Trailing stop behavior: --trailing-percent is percent points (e.g. 5 = 5%) Computes candidateStop = currentPrice * (1 - trailingPercent/100) If candidateStop > current triggerPrice, updates triggerPrice triggerPrice never moves down Rule triggers when currentPrice <= triggerPrice
List Rules
# All rules npx @vincentai/cli@latest trading-engine list-rules --key-id <KEY_ID> # Filter by status npx @vincentai/cli@latest trading-engine list-rules --key-id <KEY_ID> --status ACTIVE
Update a Rule
npx @vincentai/cli@latest trading-engine update-rule --key-id <KEY_ID> --rule-id <RULE_ID> --trigger-price 0.45
Cancel a Rule
npx @vincentai/cli@latest trading-engine delete-rule --key-id <KEY_ID> --rule-id <RULE_ID>
View Monitored Positions
npx @vincentai/cli@latest trading-engine positions --key-id <KEY_ID>
View Event Log
# All events npx @vincentai/cli@latest trading-engine events --key-id <KEY_ID> # Events for specific rule npx @vincentai/cli@latest trading-engine events --key-id <KEY_ID> --rule-id <RULE_ID> # Paginated npx @vincentai/cli@latest trading-engine events --key-id <KEY_ID> --limit 50 --offset 100 Event types: RULE_CREATED โ Rule was created RULE_TRAILING_UPDATED โ Trailing stop moved triggerPrice upward RULE_EVALUATED โ Worker checked the rule against current price RULE_TRIGGERED โ Trigger condition was met ACTION_PENDING_APPROVAL โ Trade requires human approval, rule paused ACTION_EXECUTED โ Trade executed successfully ACTION_FAILED โ Trade execution failed RULE_CANCELED โ Rule was manually canceled
Rule Statuses
ACTIVE โ Rule is live and being monitored TRIGGERED โ Condition was met, trade executed PENDING_APPROVAL โ Trade requires human approval; rule paused CANCELED โ Manually canceled before triggering FAILED โ Triggered but trade execution failed
Step 1: Place a bet with the Polymarket skill
npx @vincentai/cli@latest polymarket bet --key-id <KEY_ID> --token-id 123456789 --side BUY --amount 10 --price 0.55
Step 2: Create a strategy to monitor the thesis
npx @vincentai/cli@latest trading-engine create-strategy --key-id <KEY_ID> \ --name "Bitcoin Bull Thesis" \ --config '{ "instruments": [ { "id": "123456789", "type": "binary", "venue": "polymarket" } ], "thesis": { "estimate": 0.85, "direction": "long", "confidence": 0.7, "reasoning": "Bitcoin is likely to break $100k on ETF inflows" }, "drivers": [ { "name": "ETF News", "weight": 2.0, "direction": "bullish", "monitoring": { "keywords": ["bitcoin ETF inflows", "bitcoin institutional"], "sources": ["web_search", "newswire"] } }, { "name": "Crypto Twitter", "weight": 1.0, "direction": "contextual", "monitoring": { "entities": ["@BitcoinMagazine", "@saborskycnbc"], "sources": ["twitter"] } } ], "escalation": { "signalScoreThreshold": 0.3, "highConfidenceThreshold": 0.8, "maxWakeFrequency": "1 per 15m", "batchWindow": "5m" }, "tradeRules": { "entry": { "minEdge": 0.05 }, "autoActions": { "stopLoss": -0.15, "takeProfit": 0.30, "trailingStop": -0.05 }, "exit": { "thesisInvalidation": ["ETF outflows accelerate above $500M/week"] }, "sizing": { "method": "edgeScaled", "maxPosition": 100, "maxPortfolioPct": 20, "maxTradesPerDay": 5 } } }' \ --poll-interval 10
Step 3: Set a standalone stop-loss as immediate protection
npx @vincentai/cli@latest trading-engine create-rule --key-id <KEY_ID> \ --market-id 0xabc... --token-id 123456789 \ --rule-type STOP_LOSS --trigger-price 0.40
Step 4: Activate the strategy
npx @vincentai/cli@latest trading-engine activate --key-id <KEY_ID> --strategy-id <STRATEGY_ID>
Step 5: Monitor activity
# Check strategy invocations npx @vincentai/cli@latest trading-engine invocations --key-id <KEY_ID> --strategy-id <STRATEGY_ID> # Check trade rule events npx @vincentai/cli@latest trading-engine events --key-id <KEY_ID> # Check costs npx @vincentai/cli@latest trading-engine costs --key-id <KEY_ID> # Check performance npx @vincentai/cli@latest trading-engine performance --key-id <KEY_ID> --strategy-id <STRATEGY_ID>
Step 1: Open a perp position with the HyperLiquid skill
npx @vincentai/cli@latest hyperliquid trade --key-id <KEY_ID> \ --coin BTC --is-buy true --sz 0.001 --limit-px 106000 --order-type market
Step 2: Set a stop-loss rule for the position
npx @vincentai/cli@latest trading-engine create-rule --key-id <KEY_ID> \ --venue hyperliquid --market-id BTC --token-id BTC \ --rule-type STOP_LOSS --trigger-price 95000
Step 3: Set a take-profit rule
npx @vincentai/cli@latest trading-engine create-rule --key-id <KEY_ID> \ --venue hyperliquid --market-id BTC --token-id BTC \ --rule-type TAKE_PROFIT --trigger-price 115000
Step 4: Create a strategy to monitor your thesis
npx @vincentai/cli@latest trading-engine create-strategy --key-id <KEY_ID> \ --name "BTC Perp Momentum" \ --config '{ "instruments": [ { "id": "BTC", "type": "perp", "venue": "hyperliquid" } ], "thesis": { "estimate": 115000, "direction": "long", "confidence": 0.7, "reasoning": "ETF inflows accelerating, halving supply shock imminent" }, "drivers": [ { "name": "ETF News", "weight": 2.0, "direction": "bullish", "monitoring": { "keywords": ["bitcoin ETF inflows", "bitcoin institutional"], "sources": ["web_search", "newswire"] } } ], "escalation": { "signalScoreThreshold": 0.3, "highConfidenceThreshold": 0.8, "maxWakeFrequency": "1 per 15m", "batchWindow": "5m" }, "tradeRules": { "entry": { "minEdge": 0.05 }, "autoActions": { "stopLoss": -0.10, "takeProfit": 0.25, "trailingStop": -0.05 }, "sizing": { "method": "edgeScaled", "maxPosition": 500, "maxPortfolioPct": 20, "maxTradesPerDay": 5 } } }' \ --poll-interval 10
Step 5: Activate and monitor
npx @vincentai/cli@latest trading-engine activate --key-id <KEY_ID> --strategy-id <STRATEGY_ID> npx @vincentai/cli@latest trading-engine events --key-id <KEY_ID>
Background Workers
The Trading Engine runs two independent background workers: Strategy Engine Worker โ Ticks every 30s, checks which strategy drivers are due, fetches new data, scores signals, and invokes the LLM when the escalation threshold is met. Hooks into venue WebSocket feeds (Polymarket and HyperLiquid) for real-time price trigger evaluation. Trade Rule Worker โ Monitors prices in real-time via WebSocket (with polling fallback), evaluates stop-loss/take-profit/trailing stop rules, executes trades when conditions are met. Supports both Polymarket and HyperLiquid venues. Circuit Breaker: Both workers use a circuit breaker pattern. If a venue API fails 5+ consecutive times, the worker pauses and resumes after a cooldown. Check status with: npx @vincentai/cli@latest trading-engine status --key-id <KEY_ID>
Best Practices
Start with confidence: 0.5 and let the LLM adjust โ avoid overconfidence in the initial thesis Weight drivers by importance โ a driver with weight: 3.0 has 3x the signal score contribution of weight: 1.0 Use edgeScaled sizing for adaptive position sizes based on thesis confidence and edge Set maxPortfolioPct to limit exposure โ even high-confidence strategies shouldn't risk the entire portfolio Set both stop-loss and take-profit on positions for protection (via autoActions in the config or standalone rules) Use thesisInvalidation exit rules to define explicit conditions that should trigger position exits Monitor invocation costs โ check the costs command regularly Iterate with versions โ duplicate a strategy to tweak the config without losing the original Don't set triggers too close to current price โ market noise can trigger prematurely
Example User Prompts
When a user says: "Create a strategy to monitor AI tokens" โ Create strategy with web search + Twitter drivers "Set a stop-loss at 40 cents" โ Create STOP_LOSS rule "What has my strategy been doing?" โ Show invocations for the strategy "How is my strategy performing?" โ Show performance metrics "How much has the trading engine cost me?" โ Show cost summary "Pause my strategy" โ Pause the strategy "Make a new version with a different thesis" โ Duplicate, then update the draft "Set a 5% trailing stop" โ Create TRAILING_STOP rule
Output Format
Strategy creation: { "strategyId": "strat-123", "name": "BTC Momentum", "status": "DRAFT", "version": 1 } Rule creation: { "ruleId": "rule-456", "ruleType": "STOP_LOSS", "triggerPrice": 0.4, "status": "ACTIVE" } LLM invocation log entries: { "invocationId": "inv-789", "strategyId": "strat-123", "trigger": "web_search", "actions": ["place_trade"], "costUsd": 0.12, "createdAt": "2026-02-26T12:00:00.000Z" }
Error Handling
ErrorCauseResolution401 UnauthorizedInvalid or missing API keyCheck that the key-id is correct; re-link if needed403 Policy ViolationTrade blocked by server-side policyUser must adjust policies at heyvincent.ai402 Insufficient CreditNot enough credit for LLM invocationUser must add credit at heyvincent.aiINVALID_STATUS_TRANSITIONStrategy can't transition to requested stateCheck current status (e.g., only DRAFT can activate)CIRCUIT_BREAKER_OPENPolymarket API failures triggered circuit breakerWait for cooldown; check status command429 Rate LimitedToo many requests or concurrent LLM invocationsWait and retry with backoffKey not foundAPI key was revoked or never createdRe-link with a new token from the wallet owner
Important Notes
Authorization: All endpoints require the API key for the relevant venue (Polymarket or HyperLiquid wallet key) Local only: The API listens on localhost:19000 โ only accessible from the same VPS No private keys: All trades use the Vincent API โ your private key stays secure on Vincent's servers Policy enforcement: All trades (both LLM and standalone rules) go through Vincent's policy checks Idempotency: Rules only trigger once. LLM invocations are deduplicated by driver state.
Category context
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
1 Docs
- SKILL.md