mcpField
O
orca-strategy

orca-strategy

github.com/senpi-aiOther14069 installsUpdated today
Repository

About orca-strategy

orca-strategy is a Senpi trading skill that scans markets for Gen-1 vanilla Striker entries. It uses runtime risk guardrails and signal-based actions, with fixed limits on positions, daily entries, leverage, and per-asset cooldowns.

Key features

  1. 01Gen-1 vanilla Striker market scanner
  2. 02Single leaderboard markets scan call
  3. 03Signal push with runtime-gated action
  4. 04Runtime risk guardrails
  5. 05Leverage clamping and entry limits

Use cases

  1. 01Scanning markets for FIRST_JUMP entry signals
  2. 02Enforcing position and daily entry caps
  3. 03Applying per-asset trading cooldowns

MCP support

The skill instructs operators to verify Senpi MCP during setup. Its runtime uses the Senpi trading runtime.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/senpi-ai/senpi-skills --skill orca-strategy

After installing, type/orca-strategyin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

README.md
runtime.yaml
config/
orca-config.json
references/
skill-attribution.md
scripts/
orca_config.py
orca-producer.py

Details

From the project README

🐋 ORCA v4.0.0 — Gen-1 Vanilla Striker

v4.0.0 (2026-05-12) — plumbing-only migration

NO thesis change. v3.0 Gen-1 vanilla Striker logic preserved verbatim. Migration: mcporter → SenpiClient, scanner-side create_position → producer push_signal() with LLM-gated runtime action, Python state files for daily cap → runtime.yaml risk.guard_rails, MARKET exits → FEE_OPTIMIZED_LIMIT.

Back to pure FIRST_JUMP explosions.

v3.0 changelog (fleet-fix batch 4)

Reverted Gen-2 quality confirmation. Orca's own self-diagnosis: "Gen-2 confirmation adds latency and buys local tops after the move."

  • Removed leaderboard_get_momentum_events API call
  • Removed TCS ELITE/RELIABLE gate and ELITE_BONUS booster
  • Removed contribution_pct_change_4h acceleration booster
  • Back to single API call per scan (leaderboard_get_markets)
  • Leverage clamping applied to emitted entry (get_safe_leverage)

⛔ CRITICAL AGENT RULES

RULE 1: Install path is /data/workspace/skills/orca-strategy/
RULE 2: THE SCANNER DOES NOT EXIT POSITIONS — DSL only.
RULE 3: MAX 3 POSITIONS
RULE 4: Verify runtime on every session start
RULE 5: Never modify parameters
RULE 6: MAX 6 ENTRIES PER DAY
RULE 7: 120-minute per-asset cooldown

Runtime Setup

sed -i 's/${WALLET_ADDRESS}/<WALLET>/' /data/workspace/skills/orca-strategy/runtime.yaml
sed -i 's/${TELEGRAM_CHAT_ID}/<CHAT_ID>/' /data/workspace/skills/orca-strategy/runtime.yaml
openclaw senpi runtime create --path /data/workspace/skills/orca-strategy/runtime.yaml
openclaw senpi runtime list
openclaw senpi status

Bootstrap Gate

On EVERY session start, check config/bootstrap-complete.json. If missing:

  1. Read senpi-trading-runtime skill
  2. Verify Senpi MCP
  3. Set wallet and telegram in runtime.yaml
  4. Install runtime
  5. Verify: openclaw senpi runtime list and openclaw senpi status
  6. Create scanner cron (90s, main)
  7. Write config/bootstrap-complete.json
  8. Send: "🐋 ORCA v3.0 online. Vanilla Striker. Silence = no explosions."

Risk

RuleValue
Max positions3
Max entries/day6
Leverage7x
Cooldown120 min per asset
Min score9

Files

FilePurpose
scripts/orca-scanner.pyGen-1 vanilla Striker scanner
scripts/orca_config.pyConfig helper
config/orca-config.jsonWallet, strategy ID
runtime.yamlRuntime YAML for DSL plugin

License

MIT — Built by Senpi (https://senpi.ai).

Skill Attribution

When creating a strategy, include skill_name and skill_version in the call. See references/skill-attribution.md for details.

Comments

Markdown supported