# Pmm Config Playbook

> Ready-to-deploy pmm_mister config profiles (aggressive / balanced / conservative) — full parameter coverage including spreads, effectivization times, tolerance, order types, skew, and global TP/SL.

- Skill: `hummingbot/pmm-config-playbook` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add hummingbot/pmm-config-playbook`
- Raw SKILL.md: https://api.skillmd.com/api/skills/hummingbot/pmm-config-playbook/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: hummingbot (https://skillmd.com/u/hummingbot)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/hummingbot/pmm-config-playbook

---


# pmm_mister Config Playbook

Three vetted `pmm_mister` profiles, one per risk posture. Each profile lives in a
**companion file** — fetch only the one you need so the others never load into
context:

```
manage_skill(action="read_file", name="pmm_config_playbook", file="config_aggressive.md")
```

## Pick a profile by regime

| Regime                                  | Profile          | File                        |
|-----------------------------------------|------------------|-----------------------------|\n| Quiet / low-vol ranging (ADX < 18)      | **Aggressive**   | `config_aggressive.md`      |
| Ranging / normal (ADX < 25)             | **Balanced**     | `config_balanced.md`        |
| Volatile / trending / uncertain         | **Conservative** | `config_conservative.md`    |

- **Aggressive** — tight spreads, fast refresh, short effectivization (60s),
  wide inventory bands, high allocation. Maximizes fill rate in calm markets.
  Most inventory/PnL risk.
- **Balanced** — the default. Moderate spreads, 120s effectivization, standard
  tolerances. Good steady-state when regime is unclear.
- **Conservative** — wide spreads, slow refresh, long effectivization (300s),
  tight inventory bands, strong skew enforcement (min_skew=2.0), low
  allocation/leverage, both global TP and SL active. Capital preservation in
  chop/vol.

## How to use a template

1. Read the chosen companion file. It contains a full `config_data` block for
   `manage_controllers(action="upsert", target="config")`.
2. **Always adapt** these to the actual operation before deploying:
   - `connector_name`, `trading_pair`
   - `total_amount_quote` (respect the strategy's risk limit)
   - `leverage` (never above the strategy's cap; templates default low)
3. Deploy via the normal flow (`manage_controllers` upsert → `manage_bots` deploy).
   Live retunes go through `manage_bots(action="update_config", confirm_override=true)`.

## Key parameter reference

Parameters most commonly tuned in real operations:

**Inventory & allocation**
- `portfolio_allocation` — fraction of `total_amount_quote` actively deployed per iteration
- `target_base_pct` / `min_base_pct` / `max_base_pct` — inventory band; skew
  kicks in when base drifts outside min/max
- `min_skew` — minimum spread multiplier applied to the heavy side when inventory
  drifts; 1.0 = no minimum, 2.0 = at least 2× wider on the accumulating side
- `max_active_executors_by_level` — max concurrent open executors per level;
  controls total directional exposure (fills × allocation per level)

**Order timing**
- `executor_refresh_time` — how often (seconds) the controller checks and potentially
  replaces open orders; lower = tighter to mid price but more rate limit usage
- `buy/sell_cooldown_time` — after a fill, how long to wait before placing a new order
  on that side; lower = faster re-entry, more risk of accumulating at similar prices
- `buy/sell_position_effectivization_time` — how long (seconds) the per-fill
  LIMIT_MAKER TP order stays on the book after a fill; when this expires, the TP
  order is **removed** and the position transitions to "hold" mode managed only by
  the global SL/TP layer. Lower = TP has less time to fill → positions accumulate
  into hold faster. Higher = TP order stays on book longer → more chances of hitting TP.

**Spread & refresh tolerance**
- `price_distance_tolerance` — minimum price gap required between open orders at
  the same level; prevents stacking orders too close together
- `refresh_tolerance` — minimum mid-price move required to trigger a quote
  refresh/replacement; lower = more responsive, higher cancel/replace churn
- `tolerance_scaling` — multiplier applied to tolerance values as the number of
  active executors grows; prevents cancel-loops when multiple orders are open at
  the same level

**Order types** (3 = LIMIT_MAKER / post-only, 2 = LIMIT, 1 = MARKET)
- `open_order_type` — order type for entry orders (always use 3 unless exchange rejects)
- `take_profit_order_type` — order type for TP orders (always 3)

**Per-fill risk**
- `take_profit` — offset from fill price where the LIMIT_MAKER TP order is placed;
  must be > round-trip fees to be profitable

**Global portfolio guardrails (position hold phase)**
- `global_tp_enabled` / `global_take_profit` — when total held position gains this %, close and restart MM
- `global_sl_enabled` / `global_stop_loss` — when total held position loses this %, close and restart MM
- `global_sl_activation_from` — inventory threshold from which global SL activates
  (`"min_base"` = when base is light, `"target_base"` = from neutral)
- `global_tp_activation_from` — inventory threshold from which global TP activates
- `global_pnl_reference` — PnL basis: `"position"` (unrealized open PnL) or
  `"portfolio"` (total portfolio value)
- `position_profit_protection` — blocks inventory reduction at unfavorable prices

**Other**
- `tick_mode` — if true, controller runs only on candle ticks; false = continuous (default)

The full regime→param decision logic lives in the `pmm_mister_operator` strategy.
These templates are starting points — every deploy still goes through normal
risk/confirmation controls.