orca-strategy
ORCA v4.0.0 — Gen-1 Vanilla Striker, senpi_runtime_helpers migration. Plumbing-only flip from openclaw cron + mcporter subprocess to in-process SenpiClient + long-lived producer_daemon. Thesis preserved verbatim from v3.0: pure FIRST_JUMP detection + base Striker scoring + volume confirmation. DSL exit managed by plugin runtime via runtime.yaml.
How do I install this agent skill?
npx skills add https://github.com/senpi-ai/senpi-skills --skill orca-strategyIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill is a standard trading strategy implementation for the Senpi platform. It utilizes platform-specific CLI tools and MCP calls to fetch market data and manage trading logic. No malicious patterns, data exfiltration, or unauthorized command execution were detected.
- Socketwarn
1 alert: gptSecurity
- Snykwarn
Risk: MEDIUM · 1 issue
- Runlayerwarn
4/5 files flagged
- ZeroLeakspass
Score: 93/100 · 2 sections analyzed
What does this agent skill do?
🐋 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_eventsAPI call - Removed TCS ELITE/RELIABLE gate and ELITE_BONUS booster
- Removed
contribution_pct_change_4hacceleration 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:
- Read senpi-trading-runtime skill
- Verify Senpi MCP
- Set wallet and telegram in runtime.yaml
- Install runtime
- Verify:
openclaw senpi runtime listandopenclaw senpi status - Create scanner cron (90s, main)
- Write
config/bootstrap-complete.json - Send: "🐋 ORCA v3.0 online. Vanilla Striker. Silence = no explosions."
Risk
| Rule | Value |
|---|---|
| Max positions | 3 |
| Max entries/day | 6 |
| Leverage | 7x |
| Cooldown | 120 min per asset |
| Min score | 9 |
Files
| File | Purpose |
|---|---|
scripts/orca-scanner.py | Gen-1 vanilla Striker scanner |
scripts/orca_config.py | Config helper |
config/orca-config.json | Wallet, strategy ID |
runtime.yaml | Runtime 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.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/senpi-ai/senpi-skills/orca-strategy">View orca-strategy on skillZs</a>