← ClaudeAtlas

create-strategylisted

Guide for creating a new Etemaro LP strategy from scratch or adapting an existing preset. Use this skill whenever a user asks to "create a strategy", "add a new strategy", "set up a strategy", "configure LP strategy", "what strategy should I use", "tweak my strategy", "change my strategy", or any variant involving Etemaro strategy setup, customization, or deployment configuration. Also trigger when the user describes a trading goal (e.g. "I want to go bullish on SOL", "I want to earn fees on a stable pair", "I have a volatile token") and needs it translated into a concrete config. Strategies are immutable by default: this skill always creates a NEW strategy (new id) and a NEW config file, and never edits or overwrites an existing strategy without explicit user confirmation.
romankurnovskii/etemaro · ★ 43 · AI & Automation · score 67
Install: claude install-skill romankurnovskii/etemaro
# Create Strategy — Etemaro This skill walks an agent through creating or selecting an LP strategy for the Etemaro trading daemon, then generates a ready-to-use config patch and (when needed) a new strategy-library entry. --- ## Strategy Immutability (Non-Negotiable) Strategies and their config files are **immutable by default**. - **"Create a strategy" ⇒ always create a NEW strategy.** New unique library `id`, new versioned config file. Never rename, overwrite, or edit an existing entry or config. - Applies to: entries in `config/shared/strategy-library.json`, and config files under `config/instances/`. - **Bundled presets are read-only.** `config/shared/strategy-library.shared.json` (and its source of truth `packages/core/src/domain/strategy-library-shared.ts`) ship with the repo. Never edit them in place — copy to a new private entry instead. - **If the agent believes an existing strategy needs to change** (market conditions shifted, performance is bad, a filter is wrong): 1. **STOP.** Do not edit. 2. State the exact field(s), current value(s), and proposed value(s). 3. Give the reason and evidence (logs, metrics, `file:line`). 4. **Ask for explicit user confirmation.** 5. Recommend creating a **new variant** (copy the old entry/config → new id + new config file) so the original stays intact and comparable. This is the default suggestion, even with confirmation. ### Only exception: missing / malformed required data When a strategy or config