skills.rest
LivTorgEx
LivTorgExOFFICIAL
Explore all skills by this author →
WebsiteGitHub

strategy-conditions

Defines LivTorgEx-compatible condition and value structures for strategy filters.

Updated Mar 29, 2026
Search Tags:#risk management#json schema#trading bot#livtorgex#indicator conditions#strategy filters#long short logic
One-click install
npx skills add https://github.com/LivTorgEx/strategy-skill --skill strategy-conditions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: strategy-conditions
Source: https://github.com/LivTorgEx/strategy-skill/tree/main/skills/strategy-conditions
Command: npx skills add https://github.com/LivTorgEx/strategy-skill --skill strategy-conditions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates guesswork and trial-and-error when creating LivTorgEx strategy filter logic by providing the exact condition, value, and action syntax the server expects.

Core Features & Use Cases

  • Condition syntax reference: Define filters with operations, boolean composition (Expression), and multi-match logic (FewOf) for robust entry/exit criteria.
  • Value building blocks: Construct comparable values such as numbers, directions, globals, variables, indicators, orders, and computed measures (price math and percentage/range calculations).
  • Safe action wiring guidance: Use supported action/filter patterns (including direction-aware comparisons like <A/>A) to avoid rejected payloads (e.g., >=/<=).

Quick Start

Ask your AI to generate a LivTorgEx filters array that enters long when RSI(14) is below 30 and exits when a position PnL exceeds 50 USDT, using only valid operations and value types from this skill.

Frequently Asked Questions about strategy-conditions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build valid JSON strategy filters for a trading bot?▼

Valid JSON strategy filters require using supported operations and exact value object forms like Direction, Global, Indicator, Order, and PriceMeasure to structure entry and exit logic without server rejection.

Why does my trading bot strategy filter payload get rejected when using >= or <=?▼

Strategy filter payloads are rejected because >= and <= are invalid comparisons. You must use supported direction-aware comparisons like <A or >A to satisfy schema constraints for long and short contexts.

How do I combine multiple indicator conditions in a trading strategy?▼

You combine multiple indicator conditions by using boolean composition (Expression) and multi-match logic (FewOf) within your filters array to create robust entry and exit criteria.

What value types can I use for risk management conditions in a LivTorgEx strategy?▼

Risk management conditions support comparable values including numbers, directions, globals, variables, indicators, orders, and computed measures such as price math and percentage or range calculations.

Can I use position metrics and order existence checks in my trading bot entry logic?▼

Yes, you can include position metrics and order existence checks in entry logic by specifying supported condition operations and using Order and Math value building blocks to construct valid gating and action logic.

Related Skills

Explore More Finance & Accounting Skills→
LivTorgExLivTorgEx

strategy-tp-sl

Define Take Profit and Stop Loss configuration rules for trading strategy JSON.

Official
Intermediate
casmidicasmidi

technical-analysis

Analyze RSI, MACD, moving averages, and Bollinger Bands to generate trading signals across multiple timeframes.

Community
Advanced
LivTorgExLivTorgEx

strategy-indicators

Map requested indicator usage to server-approved type, period, and property values.

Official
Basic
piriya33piriya33
1

planning-trading-systems

Generate a strategy-spec.md detailing trading system rules and risk.

Community
Intermediate