- name
SKILL.md
Le fichier du skill reste dans le dépôt de l'éditeur.
Collez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add LeoYeAI/agent-master-skills --skill 1m-trade -a cursor -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add LeoYeAI/agent-master-skills --skill 1m-trade -a claude-code -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add LeoYeAI/agent-master-skills --skill 1m-trade -a codex -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add LeoYeAI/agent-master-skills --skill 1m-trade -a grok -yEnvoyez le message copié dans un chat Grok Bot. Le Bot récupère ce SKILL.md sur GitHub et l'ajoute aux skills que partagent tous vos Bots.
Install this skill: https://github.com/LeoYeAI/agent-master-skills/tree/HEAD/skills/1m-tradeDe l'éditeur
Official website (wallet & account): https://www.1m-trade.com
Scan and verify all required dependencies for sub-skills and install what is needed. From this skill bundle root, run node auto_check.js to verify required binaries and .env entries (it does not print secrets).
1m-trade-news (required)This aggregator must have the 1m-trade-news sub-skill available: market intelligence, news, and BlockBeats API calls all go through it. Do not skip this step when installing the bundle.
Skill files: Ensure the bundle includes skills/1m-trade-news/ (SKILL.md, etc.) and that your OpenClaw / host loads that folder as the 1m-trade-news skill.
curl: Required on PATH for the documented API flows (see metadata requires.bins).
BlockBeats API key (BLOCKBEATS_API_KEY): Market and news workflows use the BlockBeats Pro API. Install-time, ensure BLOCKBEATS_API_KEY is set in the local 1m-trade state file (paths under Optional runtime override below).
Apply for / obtain a key (free tier):
curl --request GET --url "https://api-pro.theblockbeats.info/v1/api-key/free"
data.api_key and use it as BLOCKBEATS_API_KEY.~/.openclaw/.1m-trade/.env (or $OPENCLAW_STATE_DIR/.1m-trade/.env if you use that override), on its own line:
BLOCKBEATS_API_KEY=<api_key>
Do not remove unrelated lines; only add or update this variable.Reference: skills/1m-trade-news/SKILL.md → Get an API key (includes agent-safe steps to populate .env without printing the key).
Security: Do not paste API keys into chat; the model must not echo stored keys.
1m-trade-dex (required)This aggregator must have the 1m-trade-dex sub-skill available: trading, wallet queries, and hl1m all go through it. Do not skip this step when installing the bundle.
skills/1m-trade-dex/ (SKILL.md, reference.md, etc.) and that your OpenClaw / host loads that folder as the 1m-trade-dex skill.hl1m): Install the 1m-trade package so hl1m is on PATH (Python 3.11+ recommended):
pipx install 1m-trade
hl1m --help
If pipx is missing, install it per your OS (see skills/1m-trade-dex/SKILL.md → Setup).hl1m init-wallet (and related steps) so .env contains the Hyperliquid fields auto_check.js expects — see skills/1m-trade-dex/SKILL.md → Wallet initialization.Optional runtime override:
OPENCLAW_STATE_DIR can be set to change where local .1m-trade state files are read/written.~/.openclaw/.1m-trade/.Secret source-of-truth policy:
.env file under the paths above (typically after the user runs hl1m init-wallet and related CLIs locally)..env into context or quote stored secrets. For wallet bind, if the user voluntarily sends wallet address + proxy private key in one message (e.g. clearly labeled fields such as wallet address and proxy private key), follow 1m-trade-dex → parse and invoke hl1m init-wallet --address … --pri_key … in a trusted shell; do not repeat full keys in assistant replies. Otherwise prefer the user running init-wallet locally without pasting keys in chat.This skill (1m-trade) is an orchestration hub that integrates multiple sub-skills into a single coherent workflow. You describe your goal (e.g., "check today's sentiment", "analyze BTC fund flows and open a long with half my balance", "help me configure my Hyperliquid wallet with init-wallet", "auto-trade BTC"), and this skill decomposes the request and calls 1m-trade-news and 1m-trade-dex to complete the operation.
Based on intent keywords, this skill routes into one of the workflows below (or composes them).
Triggers: market, price, news, macro, fund flows, perps, search [keyword]
Skill: 1m-trade-news
Logic:
Example output:
📰 Market Report · 202X-XX-XX
===
1. 📊 Snapshot
Sentiment: 35 → Neutral
BTC ETF: +$120M net inflow today
On-chain tx volume: +15% vs yesterday
2. 💰 Hot flows (Solana)
1. JTO net inflow $4.2M
2. ...
3. 🌐 Macro
Global M2: +4.5% YoY → Liquidity easing
DXY: 104.2 → Relatively strong
Overall: Macro backdrop is neutral-to-bullish for crypto.
Triggers: init wallet, configure wallet, configure trading account, bind wallet, connect Hyperliquid, set up trading, wallet settings, proxy key, API key (wallet); same message with both wallet address and proxy private key (or non-English equivalents per 1m-trade-dex Natural-language binding).
Skill: 1m-trade-dex (see skills/1m-trade-dex/SKILL.md → Natural-language binding and skills/1m-trade-dex/reference.md)
Wallet operations (synced with sub-skill docs):
Logic:
wallet address and proxy private key, or other languages as mapped in 1m-trade-dex), follow 1m-trade-dex Natural-language binding: parse 0x + 40 hex (address) and 0x + 64 hex (proxy key), then run hl1m init-wallet --address <parsed> --pri_key <parsed> in a trusted shell; do not echo full keys in chat.hl1m init-wallet --address 0xYourWalletAddress --pri_key 0xYourProxyPrivateKey
hl1m query-user-state to confirm the account is visible.Triggers: trade, order, open, close, positions, price, kline, HIP3, AAPL, GOLD
Skill: 1m-trade-dex
Logic:
1m-trade-dex is installed and run node auto_check.js to verify prerequisites. If it fails, do not execute any trades.1m-trade-dex documentation for the specific command.Trigger examples: "check the market then decide whether to buy BTC", "after I init my wallet, show ETH kline"
Logic:
User: "How is the crypto market today? I also need to connect my Hyperliquid wallet."
1m-trade:
wallet address + proxy private key (or equivalent), parse and run hl1m init-wallet; otherwise give the placeholder command for local use (proxy key only; never the main wallet private key). Do not guide send-private-key.User: "Search for the latest news about 'Bitcoin halving', then show BTC kline."
1m-trade:
Triggers: enable auto trading, autonomous trading, managed, AI trade for me, run every N minutes, auto trade BTC
Logic:
Run the checker once before enabling cron:
node auto_check.jsnode <skill_bundle_root>/auto_check.js
If it fails, do not enable auto trading.Check whether the 1m-trade-auto-trader cron job exists:
openclaw cron list to verify whether it still exists.openclaw cron rm <task id>, then re-run openclaw cron list to confirm it is gone.Create a periodic workflow using the command below. --session isolated is fixed and must not be changed. The default interval is every 20 minutes (*/20); replace with */N if needed. Send the trading report to the user.
Security constraints for the cron message:
.env contents, tokens).Run:
openclaw cron add \
--name "1m-trade-auto-trader" \
--cron "*/20 * * * *" \
--session isolated \
--message "<Paste the FULL prompt from #### Workflow content through the end of the report template below; translate EVERY narrative line into the user's language (e.g. full Simplified Chinese if the user uses Chinese—no leftover English instructions). Keep skill names, hl1m subcommands, symbols, and <<...>> structure unchanged. No secrets. Each run outputs ONLY the final trading report; that report must be monolingual (all Chinese OR all English per user—no mixed prose). Replace this placeholder with that translated block.>" \
--timeoutSeconds 600 \
--announce \
--channel <channel e.g. telegram> \
--to "<user id>" \
Pre-start: dependency memory check All skills are installed locally.
Try reading: $OPENCLAW_STATE_DIR/.1m-trade/dependencies-status.md
Decide based on the status:
Only when initialization is needed: Ensure these skills are available in order:
Must execute: update/create the dependency memory file by overwriting:
# Dependency install marker - do not edit manually
Installed: true
Skills: 1m-trade-news (or others)
Skills Path: <skill paths>
LastChecked: 2026-03-15 14:30:00 UTC
Start execution
Start execution.
BTCETHSOLxyz:GOLD (alias: Gold)xyz:CL (alias: Crude Oil)xyz:SILVER (alias: Silver)xyz:NVDA (alias: NVIDIA)xyz:GOOGLE (alias: Google)xyz:NATGAS (alias: Natural Gas)xyz:BRENTOIL (alias: Brent Oil)xyz:HOOD (alias: Robinhood)
Quote currency: USDCExecution loop: When triggered, execute the following steps in order. Avoid requesting intermediate confirmations; proceed with execution.
1m-trade-news to fetch the latest 20 newsflashes/news and determine whether they mention assets in the market universe to infer sentiment.1m-trade-dex → query-kline (default 1h).1m-trade-dex → query-user-state.1m-trade-dex → query-mids.Decide based on news sentiment and kline trend:
Mandatory risk controls & calculations:
qty (--qty) = target notional (USDC) / latest price, using appropriate precision.Based on the decision, use 1m-trade-dex commands to trade.
market-orderplace-orderGenerate a brief report (not too long) describing the decision rationale and execution results. Follow this Markdown format strictly.
Locale: Infer the user’s primary language from the session (e.g. Chinese vs English). The report must be monolingual — no zh/en mix in narrative text.
Language rule (strict):
BTC, ETH, xyz:GOLD, …), the literal 1m-trade, pair suffixes like -USDC, numbers, and % where standard.<<...>> are schema hints in this template only — strip them in the final answer. Do not print literal << or >> in the user-visible report. For each slot, output normal Markdown: localized headings and body text (e.g. - **Fundamentals**: weak market sentiment…), not - **<<Fundamentals>>**: … or • <<Fundamentals>>: …. The reader must see finished prose, not bracket markers.<<...>> slot into the user’s language (including example values that stood in for real content).1m-trade anywhere.🤖 1m-trade <<AUTONOMOUS_TRADING_REPORT>>: <<ACCOUNT_BALANCE>>: <> <>: Table coverage (same idea as per-asset section): If the market universe is large, do not fill one row per symbol by default. Prefer: (a) a narrow table — only rows for assets with material activity this run (traded, opened/closed, non-Hold, or materially different), plus one summary line for “everything else” (e.g. all others: Hold / no action); or (b) a short bullet summary instead of a wide table. When the set is small, you may use the full table pattern below.
🧠 <<PER_ASSET_DECISIONS>>
Coverage rule: If the market universe is large or a full per-asset write-up would make the report too long, prefer a summary instead of repeating the block below for every symbol. In summary mode: give one cross-asset fundamentals/sentiment paragraph, portfolio-level account state, then short bullets only for assets that mattered (e.g. traded this run, non-Hold decision, material risk, or materially different from the rest). End with a brief execution recap. Strip <<...>> in final output; stay monolingual.
When the set is small (or the user asked for full detail), repeat per asset:
[ASSET]-USDC
|
---name: 1m-tradedescription: |---# skills/1m-trade/SKILL.mdFAQ
Téléchargez skills/1m-trade/SKILL.md auprès de l'éditeur, ou copiez le chemin et ouvrez le dépôt. PlugMCP répertorie le skill et n'héberge pas le fichier.
L'éditeur le maintient sur https://github.com/LeoYeAI/agent-master-skills.
Claude, Cursor, Codex et Grok Build peuvent lire un SKILL.md que vous ajoutez depuis le dépôt de l'éditeur. Grok Bot l'installe lorsque vous envoyez dans un chat le lien du dossier GitHub du skill.