Token导航 LogoToken导航TokenDH.com
待分类敏感数据github未标认证来源可访问许可证需确认审计提醒

wolverine-strategy狼獾策略

Agent Skill

wolverine-strategy 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

745

周安装

32

GitHub Stars

75

下载量

261
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:wolverine-strategy(狼獾策略)
来源仓库:https://github.com/senpi-ai/senpi-skills
仓库路径:skills/wolverine-strategy
安装命令:
npx skills add https://github.com/senpi-ai/senpi-skills --skill wolverine-strategy
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/senpi-ai/senpi-skills --skill wolverine-strategy

简介

wolverine-strategy 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。

  • 它可结合来源仓库、安装命令和原始 README 继续核验具体用法。
  • 安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。
  • 安装命令:npx skills add https://github.com/senpi-ai/senpi-skills --skill wolverine-strategy
  • 来源仓库:https://github.com/senpi-ai/senpi-skills

SKILL.md

🦡 WOLVERINE v2.3 — HYPE Alpha Hunter

Single asset. One thesis. Smart money commits, Wolverine pounces, DSL trails the trend.

What it does

Wolverine scans HYPE on Hyperliquid every 3 minutes for a confluence of momentum signals:

  • Smart Money consensus — pct of top traders gain ≥ minimum, trader count above threshold
  • Velocity acceleration — 15m and 1h contribution change positive AND building (15m > 1h)
  • Price confirmation — 4H and 1H both moving in the signal direction
  • Volume confirmation — bonus when volume spikes above 6h average
  • 15m freshness gate — penalizes stale signals (15m velocity < 0)

When the score reaches 8+, Wolverine fires a HYPE entry at conviction-scaled leverage (7x or 10x) with FEE_OPTIMIZED_LIMIT order type. Position management is delegated entirely to the DSL exit engine — Wolverine never closes a position itself, only opens.

v2.3 — chop-hardened

On 2026-04-14 Wolverine v2.2 took 5 consecutive losing HYPE trades over ~3 hours of chop for -$113 total. Every entry was a "fresh signal" by v2.2's criteria, but the scanner had no concept of "we just lost N times on this same coin." v2.3 adds three protections:

1. Chop-detection lockout

After 2 losses on HYPE within 3 hours, Wolverine refuses any new entry on HYPE for 6 hours from the last loss. The scanner emits CHOP_LOCKED and waits out the chop. Constants:

  • CHOP_WINDOW_HOURS = 3
  • CHOP_MAX_LOSSES = 2
  • CHOP_LOCKOUT_HOURS = 6

2. Direction-flip hard gate

If the new signal is OPPOSITE direction to the most recent trade on HYPE within 2 hours AND that trade was a loss, Wolverine hard-gates the new entry. Catches the LONG → SHORT → LONG whipsaw pattern even before the chop-lockout threshold fires. Winning flips are still allowed (legit reversal catch); losing flips are blocked (chop chasing).

3. Persistent entry log

Every ENTRY, EXIT, CHOP_LOCKOUT, and FLIP_BLOCKED event writes a JSON line to state/entry-log.jsonl. This log survives openclaw sessions clear --current — the data lives on disk, not in LLM context. When you ask "what scored that trade?" after a session reset, you can answer by tailing the log:

tail -20 /data/workspace/skills/wolverine-strategy/state/entry-log.jsonl | jq

4. Exit tracking hook

sync_closed_positions(wallet, state) runs at the start of every scan, compares current positions to the previous scan's snapshot, and appends EXIT events linked to prior ENTRY metadata. Closes the loop on chop detection so the scanner sees its own realized PnL per trade.

Fleet-standard guardrails (all present)

  • Self-executing via create_position (no external action layer needed)
  • Dynamic P&L-aware daily entry cap (PR #176)
  • has_resting_orders() auto-cancels stale maker orders >10 min (PR #177)
  • Stale-date bug fix in load_trade_counter() (PR #177)
  • Per-asset cooldown (180 min default)
  • Conviction-scaled leverage capped at 10x (fleet H12 audit)

Key settings

SettingValueWhy
AssetHYPESingle-asset focus, no parallel bets
Max positions1Concentration
Margin per trade50%High conviction commits high capital
Max leverage10xFleet cap (H12 audit found >10x destroys edge via fees)
Min score8Above this, conviction is real
Per-asset cooldown180 minPatience between trades
DSL hard timeout240 minHYPE winners often need 2-4 hours to develop
DSL Phase 1 max loss25% ROEStandard fleet floor
DSL Phase 2 tier 1+8% / 25% lockEarlier than fleet standard

⛔ Critical agent rules

  1. Install path is /data/workspace/skills/wolverine-strategy/
  2. THE SCANNER DOES NOT EXIT POSITIONS — DSL handles all exits
  3. MAX 1 POSITION — HYPE only
  4. Do not modify scanner constants without testing — fleet-wide thresholds were tuned by audit
  5. Do not rebase the cron to a faster cadence than 3 min — 3 min is the right cadence for HYPE momentum signals

Setup

Step 1 — Install path

The skill must live at /data/workspace/skills/wolverine-strategy/. The package contains:

wolverine/
├── README.md                     # User-facing summary
├── SKILL.md                      # This file (LLM-facing)
├── runtime.yaml                  # OpenClaw runtime config + DSL preset
├── config/
│   └── wolverine-config.json     # Wallet, strategy ID, chat ID
└── scripts/
    ├── wolverine-scanner.py      # Main scanner (v2.3)
    └── wolverine_config.py       # Helper module (atomic write, MCP, state I/O)

Pull from the senpi-skills GitHub repo:

mkdir -p /data/workspace/skills/wolverine-strategy/{config,scripts,state}

curl -s https://raw.githubusercontent.com/Senpi-ai/senpi-skills/main/wolverine/runtime.yaml \
  -o /data/workspace/skills/wolverine-strategy/runtime.yaml

curl -s https://raw.githubusercontent.com/Senpi-ai/senpi-skills/main/wolverine/SKILL.md \
  -o /data/workspace/skills/wolverine-strategy/SKILL.md

curl -s https://raw.githubusercontent.com/Senpi-ai/senpi-skills/main/wolverine/config/wolverine-config.json \
  -o /data/workspace/skills/wolverine-strategy/config/wolverine-config.json

curl -s https://raw.githubusercontent.com/Senpi-ai/senpi-skills/main/wolverine/scripts/wolverine-scanner.py \
  -o /data/workspace/skills/wolverine-strategy/scripts/wolverine-scanner.py

curl -s https://raw.githubusercontent.com/Senpi-ai/senpi-skills/main/wolverine/scripts/wolverine_config.py \
  -o /data/workspace/skills/wolverine-strategy/scripts/wolverine_config.py

Step 2 — Set wallet and chat ID

Set your strategy wallet address in runtime.yaml:

sed -i 's/${WALLET_ADDRESS}/<YOUR_STRATEGY_WALLET>/' /data/workspace/skills/wolverine-strategy/runtime.yaml
sed -i 's/${TELEGRAM_CHAT_ID}/<YOUR_TELEGRAM_CHAT_ID>/' /data/workspace/skills/wolverine-strategy/runtime.yaml

OR set them in config/wolverine-config.json directly (the scanner will fall back to the JSON values if env vars / runtime placeholders aren't set):

{
  "strategyId": "your-strategy-id",
  "wallet": "0xYourStrategyWallet",
  "chatId": "your-telegram-chat-id"
}

The scanner also supports environment variables: WOLVERINE_WALLET and WOLVERINE_STRATEGY_ID.

Step 3 — Install the runtime in OpenClaw

openclaw senpi runtime create --path /data/workspace/skills/wolverine-strategy/runtime.yaml
openclaw senpi runtime list && openclaw senpi status

Step 4 — Verify with a single manual scan

python3 /data/workspace/skills/wolverine-strategy/scripts/wolverine-scanner.py

Expected: clean exit, JSON output includes "_wolverine_version": "2.3". Most likely first run shows a heartbeat (no signal) — that's normal. Wolverine fires on HYPE momentum confluence, which is rare.

Step 5 — Run the scanner on a recurring schedule

The recommended pattern is a detached bash loop with zero LLM wake cost (matches Turbine pattern):

nohup bash -c 'while true; do python3 /data/workspace/skills/wolverine-strategy/scripts/wolverine-scanner.py >> /tmp/wolverine-loop.log 2>&1; sleep 180; done' > /tmp/wolverine-nohup.log 2>&1 &

# Verify the loop is running
ps aux | grep wolverine-scanner | grep -v grep
tail -5 /tmp/wolverine-loop.log

Alternative: configure an OpenClaw cron with sessionTarget: isolated. Avoid sessionTarget: main — that pattern was a $287/day bug on Sentinel and a $200/day timer-bomb on Scorpion before we caught it.

Operational notes

Tailing the entry log

After Wolverine takes its first trade, you can read the structured entry log to see exact scores, reasons, leverage, and outcomes:

tail -10 /data/workspace/skills/wolverine-strategy/state/entry-log.jsonl | jq

The log persists across session clears, so you can answer "what was the last entry score?" even after openclaw sessions clear --current.

Checking chop-lockout state

If Wolverine outputs CHOP_LOCKED notes, it has detected 2+ losses on HYPE within 3 hours and is sitting out for 6 hours from the last loss. To see when it unlocks:

grep CHOP_LOCKOUT /data/workspace/skills/wolverine-strategy/state/entry-log.jsonl | tail -1 | jq '.unlock_ts'

This is intentional behavior, not a bug. Wolverine is protecting capital during chop.

Verifying the resting-order auto-cancel

Wolverine cancels stale FEE_OPTIMIZED_LIMIT maker orders older than 10 minutes. If you see Auto-cancel attempted on stale order... in the log, that's the safety mechanism working.

Best for

  • Operators who want a single-asset HYPE momentum specialist
  • Trading environments where 2-4 trades per day is the right cadence (not high-frequency)
  • Accounts where one bad chop day could be expensive without circuit breakers
  • Operators who want the agent to be self-managing — no manual position closing required

Not for

  • Multi-asset diversification (use Phoenix, Condor, or Polar instead)
  • High-frequency scalping
  • Anyone who wants the scanner to make exit decisions (DSL handles all exits)
  • XYZ DEX equities (Wolverine is HYPE-only)

License

MIT — Copyright 2026 Senpi (https://senpi.ai).

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

33.34%
按下载量换算87

Claude

30.95%
按下载量换算81

Cursor

20.1%
按下载量换算52

Gemini CLI

9.69%
按下载量换算25

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills