senpi-strategy-ops SKILL.md skillA

senpi-strategy-ops from senpi-ai/senpi-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

mdr add senpi-ai/senpi-skills/senpi-strategy-ops@v3.29.4

Pins v3.29.4 in mdr.lock. Pin the fingerprint instead.

Audit grade

A, 17 of 17 checks passed

Kind

SKILL.md skill

Repository

senpi-ai/senpi-skills

Path

senpi-strategy-ops/SKILL.md

Versions recorded

51

Latest version

v3.29.4, committed Nov 5, 2026

First version recorded

Aug 14, 2026

Size

43,268 bytes

Repository stars

144

License

MIT

Deploy / monitor / close a NAMED Senpi trading strategy. Monitoring is on demand: never an agent-turn cron to watch a strategy (a model call per firing) — the runtime supervises it at zero model cost, and there is no paper-trading mode ($10 floor = the test). Use when the user names a strategy to run — "install spider", "deploy polar", "set up kodiak", "reinstall athena", "run the spider strategy", "is my strategy live?", "what am I running", "list my strategies" (→ status.py), A STRATEGY IS A…

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Senpi Strategy Ops — deploy, monitor, close

A strategy is a **package**: `strategy.yaml` (the deploy manifest) + one `runtime.yaml` per instance +
`<instance>/scanners/`. The runtime **spawns and supervises** each `scanners/scan.py`, calling
`scan(inputs, ctx)` every `interval_seconds` and owning everything downstream — signal validation,
sizing/execution, the two-phase DSL exit, risk guard-rails. **There is no separate scanner daemon, no
`push_signal`.** Ops owns the deployed lifecycle. Deploy is **one verb**, run as a **detached job**:
funds preflight → wallet create+fund → runtime install → one observed scanner tick. It returns in ~1s
and you poll until it is terminal.

```
openclaw senpi validate <recipe-dir>                                    # 0a. does it RUN? records the proof create needs
python3 /data/.openclaw/skills/senpi-strategy-ops/scripts/deploy.py validate <id>              # 0b. preflight — structurally deploy-ready? (no money, nothing installed; a bare id is fetched to disk)
python3 /data/.openclaw/skills/senpi-strategy-ops/scripts/deploy.py fork <id>                  # 0c. their copy on disk — only when levers move before funding
…

Read the whole file at its exact version.

How to install

mdr add senpi-ai/senpi-skills/senpi-strategy-ops@sha256:1ac450848a1ad709

[![mdr](https://markdownregistry.com/badge/art_rp4sqhji44vs2nvn.svg)](https://markdownregistry.com/a/art_rp4sqhji44vs2nvn)

Versions

The registry has recorded 51 versions of this file, between Aug 14, 2026 and Nov 5, 2026, about one every 2 days.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_rp4sqhji44vs2nvn
GET https://markdownregistry.com/api/v1/resolve?ref=senpi-ai/senpi-skills/senpi-strategy-ops
GET https://markdownregistry.com/api/v1/blob/1ac450848a1ad709d9286508422dd717a5d0c82102e0418d0517d882fb07f131

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from senpi-ai/senpi-skills

Every file in senpi-ai/senpi-skills

Browse by kind, by grade A, or by owner.