{"slug":"romankurnovskii-create-strategy","name":"create-strategy","description":"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.","long_description":"---\nname: create-strategy\ndescription: >\n Guide for creating a new Etemaro LP strategy from scratch or adapting an existing preset.\n Use this skill whenever a user asks to \"create a strategy\", \"add a new strategy\", \"set up a strategy\",\n \"configure LP strategy\", \"what strategy should I use\", \"tweak my strategy\", \"change my strategy\", or any\n variant involving Etemaro strategy setup, customization, or deployment configuration. Also trigger when the\n user describes a trading goal (e.g. \"I want to go bullish on SOL\", \"I want to earn fees on a stable pair\",\n \"I have a volatile token\") and needs it translated into a concrete config. Strategies are immutable by\n default: this skill always creates a NEW strategy (new id) and a NEW config file, and never edits or\n overwrites an existing strategy without explicit user confirmation.\nmetadata:\n version: 2.0.0\n author: etemaro\nlicense: MIT\n---\n\n# Create Strategy — Etemaro\n\nThis skill walks an agent through creating or selecting an LP strategy for the Etemaro trading daemon,\nthen generates a ready-to-use config patch and (when needed) a new strategy-library entry.\n\n---\n\n## Strategy Immutability (Non-Negotiable)\n\nStrategies and their config files are **immutable by default**.\n\n- **\"Create a strategy\" ⇒ always create a NEW strategy.** New unique library `id`, new versioned config\n file. Never rename, overwrite, or edit an existing entry or config.\n- Applies to: entries in `config/shared/strategy-library.json`, and config files under\n `config/instances/`.\n- **Bundled presets are read-only.** `config/shared/strategy-library.shared.json` (and its source of truth\n `packages/core/src/domain/strategy-library-shared.ts`) ship with the repo. Never edit them in place —\n copy to a new private entry instead.\n- **If the agent believes an existing strategy needs to change** (market conditions shifted, performance is\n bad, a filter is wrong):\n 1. **STOP.** Do not edit.\n 2. State the exact field(s), current value(s), and proposed value(s).\n 3. Give the reason and evidence (logs, metrics, `file:line`).\n 4. **Ask for explicit user confirmation.**\n 5. Recommend creating a **new variant** (copy the old entry/config → new id + new config file) so the\n original stays intact and comparable. This is the default suggestion, even with confirmation.\n\n### Only exception: missing / malformed required data\n\nWhen a strategy or config is **missing required data or is malformed**, fix the minimum needed to restore\nvalidity — no separate confirmation gate, but report exactly what changed:\n\n- Missing required string `id` or `name`.\n- Invalid JSON / a parse error.\n- `strategy.activeStrategyId` pointing at a non-existent library id.\n- Active strategy missing `smartWalletListId` while the smart-wallet entry source is active.\n- Legacy snake_case keys (`lp_strategy`, `token_criteria`, `exit.take_profit_pct`, …).\n- Missing `screening.market.enabled` / `screening.smartWallets.enabled` so no entry source resolves.\n\nWhile fixing, **do not change intent or behavior** — only restore the missing/broken data.\n\n### Decision flow\n\n```text\nUser asks to change an existing strategy/config?\n ├─ missing or invalid required data? → fix in place (minimal), report the change\n └─ otherwise → propose change → ask confirmation → recommend NEW variant\n\nUser asks to create or tune a strategy?\n → always create a NEW library id + a NEW config file\n```\n\n### Why this matters\n\nLibrary entries are mostly **metadata** — see the next section. Editing an entry in place usually does not\nchange bot behavior; behavior lives in the agent config. So \"changing\" a strategy means shipping a new\nconfig + a new entry, which also preserves the ability to compare runs.\n\n---\n\n## What Actually Controls Runtime Behavior\n\nRead this before \"adjusting a strategy\" — it determines where a change has to go.\n\n| Setting | Where | Effect |\n| --- | --- | --- |\n| `strategy.activeStrategyId` | agent config | Selects the active library entry (context + smart-wallet list). **USED** |\n| `strategy.strategyMeteora` | agent config | Actual deploy shape: `spot` \\| `curve` \\| `bid_ask`. **USED** |\n| `strategy.minBinsBelow` / `maxBinsBelow` / `defaultBinsBelow` / `minSafeBinsBelow` | agent config | Bin range below active bin. **USED** |\n| `management.*` | agent config | Stop-loss, take-profit, trailing, sizing, cooldowns. **USED** |\n| `screening.common` / `market` / `smartWallets` | agent config | Pool filters and entry source. **USED** |\n| `opportunity.*` | agent config | Opportunity poller + smart-wallet score bonus. **USED** |\n| `risk.maxPositions` / `maxDeployAmount` | agent config | Global capital caps. **USED** |\n| `smartWalletListId` | library entry | Startup validation + smart-wallet screening. **USED** |\n| `lpStrategy`, `tokenCriteria`, `range`, `exit.takeProfitPct`, `bestFor`, `raw` | library entry | Stored / descriptive. `condition`, `notes`, `bestFor` feed the LLM strategy context; the rest are **not** read at deploy. |\n\nThere is **no `bins_above` config field** and no ratio field: directional bias is expressed through\n`strategyMeteora` (shape) plus the `*BinsBelow` counts.\n\n---\n\n## Phase 1: Gather Minimum Required Information\n\nCollect the following from the user. Ask as a single, concise message — don't split into separate turns\nunless an answer is ambiguous. Extract anything already given in the conversation and ask only for what is\nmissing.\n\n### Checklist (all required)\n\n1. **Directional view** — bullish, bearish, or neutral on the token?\n2. **Token type** — volatile/narrative, stable/high-volume pool, or blue-chip (SOL, ETH)?\n3. **Risk tolerance** — conservative (tight stop-loss, quick exits), moderate, aggressive (hold through\n dips, re-seed)?\n4. **Capital per position (SOL)** — how much SOL per position? (Drives `deployAmountSol` / `positionSizePct`.)\n5. **Exit preference** — take profit at a %/threshold, trail the price, or let it run and re-seed?\n6. **Smart-wallet tracking** — gate entry on smart-wallet presence (KOL/alpha wallets)? Affects\n `opportunity.smartWalletScoreBonus` and the opportunity poller.\n\n---\n\n## Phase 2: Review the Strategy Library\n\nThe library is **two files, merged at runtime**:\n\n| File | Contents | Editable? |\n| --- | --- | --- |\n| `config/shared/strategy-library.shared.json` | Bundled open-source presets (5) | **Read-only** |\n| `config/shared/strategy-library.json` | Private/user strategies (where new entries go) | New entries only |\n\nMerged by `StrategyLibraryManager.loadMerged()` (`packages/core/src/domain/strategy-library.ts:76-108`):\nprivate **overrides** shared on an id collision and logs a warning. Prefer private entries first, then\nshared presets; only create something new if nothing fits.\n\nRead both files. Bundled presets:\n\n| ID | Name | LP Shape | Best For |\n| --- | --- | --- | --- |\n| `custom_ratio_spot` | Custom Ratio Spot | spot | Directional bias, earn fees both ways |\n| `single_sided_reseed` | Single-Sided Bid-Ask + Re-seed | bid_ask | Volatile tokens, DCA-out on dip |\n| `fee_compounding` | Fee Compounding | any | Stable volume pools, compounding yield |\n| `multi_layer` | Multi-Layer | mixed | Custom distributions, one position |\n| `partial_harvest` | Partial Harvest | any | High-fee pools, incremental profit-taking |\n\nPrivate examples already present: `copy_trade_lag`, `smart_wallet_follow`\n(see `docs/strategies/README-smart-wallet-follow.md` for a worked example).\n\n### Recommendation Logic\n\nMap the user's intent to an existing strategy **first**. Only propose a new one if no existing strategy\nfits.\n\n| User Intent | Recommended Strategy |\n| --- | --- |\n| Bullish / bearish directional view | `custom_ratio_spot` |\n| Volatile token, exit on dump | `single_sided_reseed` |\n| Stable pair, maximize yield | `fee_compounding` |\n| Custom bin distribution | `multi_layer` |\n| Lock in gains incrementally | `partial_harvest` |\n| Neutral / range-bound | `fee_compounding` or `multi_layer` |\n\nPresent the recommendation with a one-sentence rationale. Example:\n\n> \"Based on your bullish view, I'd recommend `custom_ratio_spot` — it places more liquidity below the\n> current price so you earn fees as the token rises, with a shape that leans into the move.\"\n\nThen state the immutability rule and ask: **\"Use this existing strategy in a new config, or create a new\nstrategy entry from scratch?\"** Either way a **new config file** is produced.\n\n---\n\n## Phase 3: Smart-Wallet Decision\n\nAsk (if not already answered in Phase 1):\n\n> \"Do you want to track smart wallets (KOL/alpha wallets) for this strategy? If enabled, the opportunity\n> poller gives a score bonus to pools where tracked wallets are LPs, letting the agent enter pools it\n> would otherwise skip.\"\n\nCanonical config fields (nested under `opportunity` — the flat `opportunityPollEnabled` /\n`opportunitySmartWalletBonus` / `opportunityMinScore` names are legacy aliases only):\n\n```json\n\"opportunity\": {\n \"enabled\": true,\n \"minScore\": 40,\n \"smartWalletScoreBonus\": 20\n}\n```\n\n- **Yes** → `opportunity.enabled: true`, `opportunity.smartWalletScoreBonus: 20` (or higher). Set\n `smartWalletListId` on the new library entry and make sure that list exists in\n `config/shared/smart-wallets.json`. Populate via Telegram:\n `add smart wallet
name=