[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6GSFP14NZ0YWWCBEEE1XPXG":3,"skill-same:01M6GSFP14NZ0YWWCBEEE1XPXG":115},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":60,"commitSha":61,"skillDirectory":62,"forksCount":63,"repositoryHtmlUrl":64,"repositoryHomepageUrl":6,"ownerHtmlUrl":65,"ownerBlogUrl":66,"ownerDescription":67,"updatedAt":68,"install":69,"resources":82},"01M6GSFP14NZ0YWWCBEEE1XPXG","binance-signal-engine",null,"Multi-timeframe crypto technical analysis with scored trading signals, structured trade plans, and position sizing via Binance public API. Use when user asks to \"analyze BTC\", \"what's the signal on ETH\u002FUSDT\", \"crypto analysis\", \"trade setup for SOL\", \"scan crypto pairs\", \"check the trend on BTC\", \"multi-timeframe analysis\", \"generate a trading signal\", \"what's the bias on ETH\", \"TA on BTC\u002FUSDT\", \"is it a good time to buy BTC\", or \"position size for a crypto trade\".","jiayaoqijia\u002Fcryptoskill","jiayaoqijia","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1453879?v=4","01M6GMYTX7Q7S504VC6E756ENR","YQ","01M6GMYV1QKJ1CC75MTTGT9PR0",81,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fbinance-signal-engine\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"signal","binance signal engine","engine","binance","signals","when","technical analysis","ta","ccxt","public api","scripts","trend","usdt","generate","time","uv","good","install","analyze","api","analysis","pandas","2026-11-10 10:12:30",false,"---\nname: binance-signal-engine\ndescription: Multi-timeframe crypto technical analysis with scored trading signals, structured trade plans, and position sizing via Binance public API. Use when user asks to \"analyze BTC\", \"what's the signal on ETH\u002FUSDT\", \"crypto analysis\", \"trade setup for SOL\", \"scan crypto pairs\", \"check the trend on BTC\", \"multi-timeframe analysis\", \"generate a trading signal\", \"what's the bias on ETH\", \"TA on BTC\u002FUSDT\", \"is it a good time to buy BTC\", or \"position size for a crypto trade\".\nversion: 1.0.2\nhomepage: https:\u002F\u002Fgithub.com\u002Feplt\u002Fbinance-signal-engine\nmetadata:\n  openclaw:\n    emoji: \"?\"\n    requires:\n      bins:\n        - python3\n    install:\n      - kind: uv\n        package: ccxt pandas numpy ta\n        label: \"Install Python dependencies (ccxt, pandas, numpy, ta)\"\n    files:\n      - \"scripts\u002F*\"\n\n---\n\n# Binance Signal Engine\n\nMulti-timeframe technical analysis signal generator for cryptocurrency markets. Layers three timeframes into a single weighted score and outputs a structured trade plan with position sizing.\n\n## When to Use\n\nUse this skill when the user wants to:\n\n- Analyze any Binance-listed crypto pair technically\n- Get a directional bias or trading signal (bullish\u002Fbearish\u002Fneutral)\n- Generate entry, stop-loss, and take-profit levels for a trade\n- Check trend regime (1D), momentum (4H), and entry timing (15m)\n- Size a position based on account risk parameters\n- Scan multiple symbols in one pass\n- Get a backtest-ready data row for a symbol\n\n## How It Works\n\nThe engine scores three independent timeframe layers and combines them:\n\n**1D — Trend Regime**\nEMA structure (9\u002F21\u002F50), ADX with directional indicators (DI+\u002FDI−). Determines whether the macro environment is bullish, bearish, or neutral. This is the directional anchor — momentum and trigger signals are interpreted relative to this regime.\n\n**4H — Momentum**\nMACD line vs signal crossovers, histogram direction, and Stochastic Oscillator crosses. Stochastic signals are weighted asymmetrically depending on the regime (e.g. a bullish stoch cross from oversold in a bullish regime scores higher than in a bearish one).\n\n**15m — Entry Trigger**\nRSI oversold\u002Foverbought reclaims, Bollinger Band re-entries, volume spikes relative to the 20-period moving average, and RSI divergence detection over a 20-bar lookback. This layer determines whether *right now* is a valid entry moment.\n\nEach component contributes a configurable weighted score. The composite maps to a five-tier bias scale: STRONG BULLISH → BULLISH → NEUTRAL → BEARISH → STRONG BEARISH, with corresponding action recommendations (BUY, WATCH LONG, WAIT, WATCH SHORT, SELL\u002FSHORT).\n\nWhen conditions align, the trade planner generates a full plan using rolling support\u002Fresistance levels, ATR-based stops, and configurable risk-reward targets. The position sizer respects account balance, risk percentage, exchange lot size rules, and minimum notional constraints.\n\n## Usage\n\n```bash\n# Single pair — human-readable summary\npython3 {baseDir}\u002Fscripts\u002Fbinance_signal_engine.py BTC\u002FUSDT\n\n# Multiple pairs\npython3 {baseDir}\u002Fscripts\u002Fbinance_signal_engine.py BTC\u002FUSDT ETH\u002FUSDT SOL\u002FUSDT\n\n# JSON output for programmatic consumption\npython3 {baseDir}\u002Fscripts\u002Fbinance_signal_engine.py BTC\u002FUSDT --output json\n\n# Futures mode with custom risk parameters\npython3 {baseDir}\u002Fscripts\u002Fbinance_signal_engine.py BTC\u002FUSDT \\\n  --market futures --leverage 3 --balance 5000 --risk 2\n\n# Use a JSON config file to override all indicator\u002Fscoring parameters\npython3 {baseDir}\u002Fscripts\u002Fbinance_signal_engine.py ETH\u002FUSDT --config my_config.json\n\n# Debug mode for verbose logging\npython3 {baseDir}\u002Fscripts\u002Fbinance_signal_engine.py BTC\u002FUSDT --debug\n```\n\n### CLI Flags\n\n| Flag | Short | Default | Description |\n|------|-------|---------|-------------|\n| `symbols` | | *(required)* | One or more trading pairs, e.g. `BTC\u002FUSDT ETH\u002FUSDT` |\n| `--market` | `-m` | `spot` | Market type: `spot` or `futures` |\n| `--exchange` | `-e` | `binance` | Exchange ID (ccxt-compatible) |\n| `--balance` | `-b` | `10000` | Account balance in USD |\n| `--risk` | `-r` | `1.0` | Risk per trade as a percentage |\n| `--leverage` | `-l` | `1.0` | Leverage multiplier (futures only) |\n| `--config` | `-c` | `None` | Path to a JSON config file for full parameter override |\n| `--output` | `-o` | `summary` | Output format: `summary` (human) or `json` (machine) |\n| `--debug` | | `off` | Enable debug-level logging |\n\n## Output Structure\n\nThe JSON output contains four sections:\n\n**signal** — composite score, per-layer breakdown (trend\u002Fmomentum\u002Ftrigger), bias, regime, action recommendation, and an array of human-readable reasoning strings explaining every scoring decision.\n\n**trade_plan** — side (long\u002Fshort), entry type (market\u002Flimit), entry price, stop-loss, take-profit, support, resistance, effective risk-reward ratio, tradeable flag, and plan status (ready\u002Fwaiting\u002Freject\u002Finvalid).\n\n**position_size** — units, notional value, risk budget, actual dollar risk, potential dollar reward, position as a percentage of account, and whether the position was capped by the notional limit.\n\n**backtest_row** — flat key-value record with timestamp, symbol, 15m close, total score, bias, plan side, tradeable flag, effective RR, and sized units. Suitable for appending to a CSV or DataFrame for historical analysis.\n\n## Configuration\n\nAll parameters are configurable via a JSON file passed with `--config`. Key areas include:\n\n- EMA periods (fast: 9, slow: 21, trend: 50)\n- MACD parameters (12\u002F26\u002F9)\n- ADX period and trend threshold (14, 25.0)\n- RSI period and oversold\u002Foverbought levels (14, 35\u002F65)\n- Stochastic window, smoothing, and levels (14, 3, 20\u002F80)\n- Bollinger Band window and standard deviation (20, 2.0)\n- ATR period and stop-loss multiplier (14, 1.5)\n- Volume MA period and spike threshold (20, 1.5x)\n- Support\u002Fresistance lookback and buffer multipliers\n- Per-layer scoring weights (15 weights total)\n- Score thresholds for weak\u002Fstrong signals (10\u002F30)\n- Risk-reward ratio, minimum acceptable RR, slippage buffer\n- Account balance, risk percentage, max notional, leverage\n\nDefaults are tuned for swing\u002Fintraday crypto trading on Binance.\n\n## Dependencies\n\nRequires Python 3.8+ with the following packages:\n\n```bash\npip install ccxt pandas numpy ta\n```\n\nNo API key is required. The skill uses only Binance's public OHLCV endpoints.\n\n## Limitations\n\n- Signals are analytical tools, not financial advice. Always apply your own judgment and risk management.\n- Public API rate limits apply (~1200 weight\u002Fmin on Binance). The skill includes built-in delays between requests.\n- The most recent (still-open) candle is automatically dropped to prevent lookahead bias.\n- Short signals and position sizing for shorts are only available in `futures` mode.\n- Backtest rows are point-in-time snapshots — this is not a full backtesting engine.\n\n## External Endpoints\n\n| Endpoint | Data Sent | Purpose |\n|----------|-----------|---------|\n| `https:\u002F\u002Fapi.binance.com` (via ccxt) | Symbol name, timeframe, candle limit | Fetch public OHLCV price data |\n\nNo authenticated endpoints are called. No orders are placed. No private data leaves your machine.\n\n## Security & Privacy\n\n- **No API keys needed** — only public market data endpoints are used\n- **No data exfiltration** — all indicator computation and scoring runs locally in Python\n- **No writes to exchange** — strictly read-only; no orders, no account access\n- **No local file writes** — output goes to stdout only unless you redirect it\n- **No background processes** — runs once, prints results, exits\n\n## Model Invocation Note\n\nThis skill may be invoked automatically by the agent when your request matches the trigger phrases in the description. This is standard OpenClaw behavior. You can disable automatic invocation by setting `disable-model-invocation: true` in the frontmatter if you prefer explicit `\u002Fbinance-signal-engine` invocation only.\n\n## Trust Statement\n\nBy installing this skill, you trust that: (1) the `ccxt` library will make HTTPS requests to Binance's public REST API to fetch candle data, and (2) all analysis runs locally on your machine. No credentials are required or sent. Only install if you are comfortable with public market data requests to `api.binance.com`.\n","# Binance Signal Engine\n\nMulti-timeframe technical analysis signal generator for cryptocurrency markets. Layers three timeframes into a single weighted score and outputs a structured trade plan with position sizing.\n\n## When to Use\n\nUse this skill when the user wants to:\n\n- Analyze any Binance-listed crypto pair technically\n- Get a directional bias or trading signal (bullish\u002Fbearish\u002Fneutral)\n- Generate entry, stop-loss, and take-profit levels for a trade\n- Check trend regime (1D), momentum (4H), and entry timing (15m)\n- Size a position based on account risk parameters\n- Scan multiple symbols in one pass\n- Get a backtest-ready data row for a symbol\n\n## How It Works\n\nThe engine scores three independent timeframe layers and combines them:\n\n**1D — Trend Regime**\nEMA structure (9\u002F21\u002F50), ADX with directional indicators (DI+\u002FDI−). Determines whether the macro environment is bullish, bearish, or neutral. This is the directional anchor — momentum and trigger signals are interpreted relative to this regime.\n\n**4H — Momentum**\nMACD line vs signal crossovers, histogram direction, and Stochastic Oscillator crosses. Stochastic signals are weighted asymmetrically depending on the regime (e.g. a bullish stoch cross from oversold in a bullish regime scores higher than in a bearish one).\n\n**15m — Entry Trigger**\nRSI oversold\u002Foverbought reclaims, Bollinger Band re-entries, volume spikes relative to the 20-period moving average, and RSI divergence detection over a 20-bar lookback. This layer determines whether *right now* is a valid entry moment.\n\nEach component contributes a configurable weighted score. The composite maps to a five-tier bias scale: STRONG BULLISH → BULLISH → NEUTRAL → BEARISH → STRONG BEARISH, with corresponding action recommendations (BUY, WATCH LONG, WAIT, WATCH SHORT, SELL\u002FSHORT).\n\nWhen conditions align, the trade planner generates a full plan using rolling support\u002Fresistance levels, ATR-based stops, and configurable risk-reward targets. The position sizer respects account balance, risk percentage, exchange lot size rules, and minimum notional constraints.\n\n## Usage\n\n```bash\n# Single pair — human-readable summary\npython3 {baseDir}\u002Fscripts\u002Fbinance_signal_engine.py BTC\u002FUSDT\n\n# Multiple pairs\npython3 {baseDir}\u002Fscripts\u002Fbinance_signal_engine.py BTC\u002FUSDT ETH\u002FUSDT SOL\u002FUSDT\n\n# JSON output for programmatic consumption\npython3 {baseDir}\u002Fscripts\u002Fbinance_signal_engine.py BTC\u002FUSDT --output json\n\n# Futures mode with custom risk parameters\npython3 {baseDir}\u002Fscripts\u002Fbinance_signal_engine.py BTC\u002FUSDT \\\n  --market futures --leverage 3 --balance 5000 --risk 2\n\n# Use a JSON config file to override all indicator\u002Fscoring parameters\npython3 {baseDir}\u002Fscripts\u002Fbinance_signal_engine.py ETH\u002FUSDT --config my_config.json\n\n# Debug mode for verbose logging\npython3 {baseDir}\u002Fscripts\u002Fbinance_signal_engine.py BTC\u002FUSDT --debug\n```\n\n### CLI Flags\n\n| Flag | Short | Default | Description |\n|------|-------|---------|-------------|\n| `symbols` | | *(required)* | One or more trading pairs, e.g. `BTC\u002FUSDT ETH\u002FUSDT` |\n| `--market` | `-m` | `spot` | Market type: `spot` or `futures` |\n| `--exchange` | `-e` | `binance` | Exchange ID (ccxt-compatible) |\n| `--balance` | `-b` | `10000` | Account balance in USD |\n| `--risk` | `-r` | `1.0` | Risk per trade as a percentage |\n| `--leverage` | `-l` | `1.0` | Leverage multiplier (futures only) |\n| `--config` | `-c` | `None` | Path to a JSON config file for full parameter override |\n| `--output` | `-o` | `summary` | Output format: `summary` (human) or `json` (machine) |\n| `--debug` | | `off` | Enable debug-level logging |\n\n## Output Structure\n\nThe JSON output contains four sections:\n\n**signal** — composite score, per-layer breakdown (trend\u002Fmomentum\u002Ftrigger), bias, regime, action recommendation, and an array of human-readable reasoning strings explaining every scoring decision.\n\n**trade_plan** — side (long\u002Fshort), entry type (market\u002Flimit), entry price, stop-loss, take-profit, support, resistance, effective risk-reward ratio, tradeable flag, and plan status (ready\u002Fwaiting\u002Freject\u002Finvalid).\n\n**position_size** — units, notional value, risk budget, actual dollar risk, potential dollar reward, position as a percentage of account, and whether the position was capped by the notional limit.\n\n**backtest_row** — flat key-value record with timestamp, symbol, 15m close, total score, bias, plan side, tradeable flag, effective RR, and sized units. Suitable for appending to a CSV or DataFrame for historical analysis.\n\n## Configuration\n\nAll parameters are configurable via a JSON file passed with `--config`. Key areas include:\n\n- EMA periods (fast: 9, slow: 21, trend: 50)\n- MACD parameters (12\u002F26\u002F9)\n- ADX period and trend threshold (14, 25.0)\n- RSI period and oversold\u002Foverbought levels (14, 35\u002F65)\n- Stochastic window, smoothing, and levels (14, 3, 20\u002F80)\n- Bollinger Band window and standard deviation (20, 2.0)\n- ATR period and stop-loss multiplier (14, 1.5)\n- Volume MA period and spike threshold (20, 1.5x)\n- Support\u002Fresistance lookback and buffer multipliers\n- Per-layer scoring weights (15 weights total)\n- Score thresholds for weak\u002Fstrong signals (10\u002F30)\n- Risk-reward ratio, minimum acceptable RR, slippage buffer\n- Account balance, risk percentage, max notional, leverage\n\nDefaults are tuned for swing\u002Fintraday crypto trading on Binance.\n\n## Dependencies\n\nRequires Python 3.8+ with the following packages:\n\n```bash\npip install ccxt pandas numpy ta\n```\n\nNo API key is required. The skill uses only Binance's public OHLCV endpoints.\n\n## Limitations\n\n- Signals are analytical tools, not financial advice. Always apply your own judgment and risk management.\n- Public API rate limits apply (~1200 weight\u002Fmin on Binance). The skill includes built-in delays between requests.\n- The most recent (still-open) candle is automatically dropped to prevent lookahead bias.\n- Short signals and position sizing for shorts are only available in `futures` mode.\n- Backtest rows are point-in-time snapshots — this is not a full backtesting engine.\n\n## External Endpoints\n\n| Endpoint | Data Sent | Purpose |\n|----------|-----------|---------|\n| `https:\u002F\u002Fapi.binance.com` (via ccxt) | Symbol name, timeframe, candle limit | Fetch public OHLCV price data |\n\nNo authenticated endpoints are called. No orders are placed. No private data leaves your machine.\n\n## Security & Privacy\n\n- **No API keys needed** — only public market data endpoints are used\n- **No data exfiltration** — all indicator computation and scoring runs locally in Python\n- **No writes to exchange** — strictly read-only; no orders, no account access\n- **No local file writes** — output goes to stdout only unless you redirect it\n- **No background processes** — runs once, prints results, exits\n\n## Model Invocation Note\n\nThis skill may be invoked automatically by the agent when your request matches the trigger phrases in the description. This is standard OpenClaw behavior. You can disable automatic invocation by setting `disable-model-invocation: true` in the frontmatter if you prefer explicit `\u002Fbinance-signal-engine` invocation only.\n\n## Trust Statement\n\nBy installing this skill, you trust that: (1) the `ccxt` library will make HTTPS requests to Binance's public REST API to fetch candle data, and (2) all analysis runs locally on your machine. No credentials are required or sent. Only install if you are comfortable with public market data requests to `api.binance.com`.\n",{"name":5,"version":46,"homepage":47,"metadata":48,"description":7},"1.0.2","https:\u002F\u002Fgithub.com\u002Feplt\u002Fbinance-signal-engine",{"openclaw":49},{"emoji":50,"files":51,"install":53,"requires":57},"?",[52],"scripts\u002F*",[54],{"kind":34,"label":55,"package":56},"Install Python dependencies (ccxt, pandas, numpy, ta)","ccxt pandas numpy ta",{"bins":58},[59],"python3","main","3df1d0d67b30ff15236561f8c0f9f06d33f42dfd","skills\u002Fexchanges\u002Fbinance-signal-engine",17,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia","https:\u002F\u002Feth2030.com","Hardcore infra. Building @alt-research and applied cryptography.","2026-11-12 02:28:42",{"source":8,"skillName":5,"commands":70,"prompt":80,"zipAvailable":81},[71,74,77],{"tool":72,"command":73},"npx","npx skills add jiayaoqijia\u002Fcryptoskill --skill binance-signal-engine",{"tool":75,"command":76},"bunx","bunx skills add jiayaoqijia\u002Fcryptoskill --skill binance-signal-engine",{"tool":78,"command":79},"pnpm","pnpm dlx skills add jiayaoqijia\u002Fcryptoskill --skill binance-signal-engine","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fbinance-signal-engine\u002FSKILL.md",true,[83,89,93,97,103,107,111],{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"_meta.json","REFERENCE","参考文档",140,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fbinance-signal-engine\u002F_meta.json",{"path":90,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":91,"sourceHtmlUrl":92},"README.md",4410,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fbinance-signal-engine\u002FREADME.md",{"path":94,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fguide.md",53793,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fbinance-signal-engine\u002Freferences\u002Fguide.md",{"path":98,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":101,"sourceHtmlUrl":102},"scripts\u002Fbinance_signal_engine.py","SCRIPT","脚本",37105,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fbinance-signal-engine\u002Fscripts\u002Fbinance_signal_engine.py",{"path":104,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":105,"sourceHtmlUrl":106},"skill-card.md",2190,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fbinance-signal-engine\u002Fskill-card.md",{"path":108,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":109,"sourceHtmlUrl":110},"SOURCE.md",258,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fbinance-signal-engine\u002FSOURCE.md",{"path":112,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":113,"sourceHtmlUrl":114},"TRUST.auto.yaml",2267,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fbinance-signal-engine\u002FTRUST.auto.yaml",[116,144,166,184,197,207],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":120,"licenseFileUrl":121,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":41},"01M712C436EQYE43342Q4E7GG1","recipe-performance","Diagnose a specific MetaMask user flow's real-app performance and Sentry critical-user-flow telemetry with deterministic mm-harness recipes. Use for CUF boundaries, cold\u002Fwarm\u002Fbackground-resume behavior, latency regressions, lifecycle tags, duplicate or blocking network requests, long tasks, layout\u002Fpaint cost, screen redraws, React rerenders, or browser trace analysis where tests alone cannot prove the real app.","MIT","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fwallets\u002Fmetamask-official-recipe-performance\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fwallets\u002Fmetamask-official-recipe-performance\u002FSKILL.md",[],[125,126,127,128,129,130,131,132,133,134,135,136,39,137,138,139,140,141,142,143],"performance","recipe performance","recipe","mm","sentry","harness","app","deterministic","recipes","flow","cold","critical","tasks","react","browser","layout","screen","network","metamask",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":148,"licenseFileUrl":149,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":41},"01M70XT2F8A5CQZ81JBP98KSW3","mexc-spot-websocket","MEXC Spot WebSocket workflows for public streams, protobuf handling, depth maintenance, listen keys, and private streams without exposing API keys.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fmncrftfrcnm-mexc-spot-websocket\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fmncrftfrcnm-mexc-spot-websocket\u002FSKILL.md",[],[153,154,155,38,156,157,158,159,160,161,162,163,164,165],"mexc spot websocket","spot","websocket","workflows","public","listen","streams","depth","keys","for","api keys","maintenance","protobuf",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":148,"licenseFileUrl":170,"sourceHtmlUrl":171,"categories":172,"keywords":173,"publishedAt":41},"01M70XT0MBXN3WZY1BKN0CPNKR","mexc-spot-rest","MEXC Spot REST workflows for public data, signed account requests, orders, wallet\u002Fadmin actions, and secure signing without exposing API keys.","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fmncrftfrcnm-mexc-spot-rest\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fmncrftfrcnm-mexc-spot-rest\u002FSKILL.md",[],[174,154,175,176,177,178,179,163,162,161,180,181,182,157,183,156,38],"mexc spot rest","REST","admin","signing","Wallet","requests","actions","secure","data","orders",{"skillNo":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":148,"licenseFileUrl":188,"sourceHtmlUrl":189,"categories":190,"keywords":191,"publishedAt":41},"01M70XSYSVZ2N0N91XCAR2CAK0","mexc-futures-websocket","MEXC Futures WebSocket workflows for public streams, private account\u002Forder\u002Fposition streams, ping\u002Fpong, subscriptions, and depth maintenance.","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fmncrftfrcnm-mexc-futures-websocket\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fmncrftfrcnm-mexc-futures-websocket\u002FSKILL.md",[],[192,193,155,194,195,164,162,196,160,159,157,156],"mexc futures websocket","futures","position","ping","subscriptions",{"skillNo":198,"name":199,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":120,"licenseFileUrl":200,"sourceHtmlUrl":201,"categories":202,"keywords":203,"publishedAt":41},"01M6H0ZWHVE5W04WG2DKQE2SQC","0xklen-version-and-refresh-sanctions-lists","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002F0xklen-version-and-refresh-sanctions-lists\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002F0xklen-version-and-refresh-sanctions-lists\u002FSKILL.md",[],[204,205,206],"refresh","0xklen version and refresh sanctions lists","version",{"skillNo":208,"name":209,"nameZh":6,"description":210,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":120,"licenseFileUrl":211,"sourceHtmlUrl":212,"categories":213,"keywords":214,"publishedAt":41},"01M6H0Z28Q3R8J0S799GJQWXM3","verify-tests-cover-changed-lines","Use when a PR adds code that the existing suite may not exercise. Measures patch coverage — the share of newly changed lines hit by tests — before approving.","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002F0xklen-verify-tests-cover-changed-lines\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002F0xklen-verify-tests-cover-changed-lines\u002FSKILL.md",[],[215,216,217,218,219,220,221,222,223,224,225],"tests","cover","verify tests cover changed lines","verify","coverage","pr","exercise","use","patch","code","share"]