Duola Quant Copy Engine
by @duolaamengweb3
Institutional-grade execution playbook for the published `duola` Polymarket copy-trading CLI in lobster-agent workflows. Use when tasks require production-st...
clawhub install duola-quant-copy-engineπ About This Skill
name: duola-lobster-agent description: "Institutional-grade execution playbook for the published
duola Polymarket copy-trading CLI in lobster-agent workflows. Use when tasks require production-style setup and operation: install/upgrade from npm, leader onboarding, trade synchronization, strategy backtesting, autopilot bootstrap, live loop control, diagnostics, and structured risk/performance reporting."
Duola Lobster Agent
Overview
Execute the standard operating workflow for duola as an agent toolchain.
Prefer staged rollout: sync -> backtest -> doctor -> limited live start -> status/log review.
Billing Setup (SkillPay)
Configure once in runtime environment:
export SKILLPAY_API_URL="https://skillpay.me"
export SKILLPAY_API_KEY="sk_***"
export SKILLPAY_SKILL_ID="77f983da-1eda-4793-b632-f7502d6beb4b"
export SKILLPAY_PRICE_USDT="0.01"
Use billing gate with commands that support --billing-user-id.
Supported: sync, backtest, follow start, autopilot onboard, autopilot start.
Check billing endpoints from CLI:
duola billing balance --user-id --output json
duola billing charge --user-id --amount 0.01 --output json
duola billing payment-link --user-id --amount 1 --output json
Execution Workflow
1) Verify Runtime and CLI
Run:
node -v
npm view duola version
duola --version
If duola is missing, install:
npm install -g duola
If global install is restricted, run project-local CLI:
npm install
npm run build
node dist/index.js --version
2) Register and Inspect Leader
duola leader add --name
duola leader list --output json
duola leader inspect --output json
Use deterministic aliases and keep one alias per leader address.
3) Sync and Baseline Backtest
duola sync --limit 500 --output json
duola backtest --lookback 30d --fixed-usd 25 --output json
If results are weak, tune before live mode:
--min-liquidity--min-time-to-expiry--fixed-usd4) Run Doctor Diagnostics
duola doctor --output json
Require passing API connectivity and secret checks before live mode.
5) Onboard Autopilot (Preferred Live Path)
Use stdin for private key and do not print secrets:
printf '%s' '' | duola autopilot onboard \\
--name --private-key-stdin --profile balanced --sync-limit 200
Start with explicit confirmation phrase:
duola autopilot start --confirm-live "I UNDERSTAND LIVE TRADING" --detach
6) Operate and Observe
duola autopilot status --output json
duola follow logs --tail 100 --output json
duola autopilot stop --output json
For limited-cycle validation:
duola follow start --confirm-live "I UNDERSTAND LIVE TRADING" --max-cycles 5 --output json
Reporting Contract
Return concise machine-usable summaries:
leader: alias, addresssync: fetched/inserted/skipped countsbacktest: win rate, total pnl, max drawdown, executed signalsdoctor: failed checks and remediationautopilot: status, detach state, heartbeat, recent errorsWhen live start is blocked, report the exact failed precondition and the next command.