strategy-indicators

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

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/LivTorgEx/strategy-skill --skill strategy-indicators
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: strategy-indicators
Source: https://github.com/LivTorgEx/strategy-skill/tree/main/skills/strategy-indicators
Command: npx skills add https://github.com/LivTorgEx/strategy-skill --skill strategy-indicators

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of using incorrect indicator types, period values, or property names that break strategy validation on the LivTorgEx server.

Core Features & Use Cases

  • Canonical indicator schema lookup: Fetches the authoritative indicator list via MCP so your strategy JSON matches server-supported fields.
  • Period and property correctness: Provides the exact valid period and property options for each indicator type, including handling indicators that have no period.
  • Practical strategy-building support: Helps you assemble indicator wrappers with correct timeframe, idx, and optional modify direction semantics (LONG/SHORT/BOTH) when specifying conditions.

Quick Start

Ask your agent to list valid indicator types and then generate a correctly formatted indicator object for RSI with an allowed period and property for the 1h timeframe.

Frequently Asked Questions about strategy-indicators

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

FAQPage Schema
How do I build valid trading indicator definitions for strategy filters?

To build valid trading indicator definitions, map requested indicator usage to server-approved type, period, and property values fetched via the MCP list_indicators endpoint, ensuring correct timeframe selection and candle indexing.

Why does my trading strategy validation fail on the server?

Strategy validation fails when indicator objects include incorrect indicator types, period values, or property names not permitted by the server, requiring canonical schema lookup to match supported fields exactly.

How do I configure indicator period and property values for a specific timeframe?

Configuring indicator period and property values requires fetching the authoritative indicator list via MCP to retrieve exact valid options for each type, including handling indicators that have no period parameter.

Can I use optional direction modification when specifying trading indicator conditions?

Yes, you can specify optional direction modification using LONG, SHORT, or BOTH semantics when assembling indicator wrappers with correct timeframe and candle index values for strategy conditions.

What is the canonical source of truth for permitted indicator fields in bot settings?

The MCP endpoint list_indicators serves as the canonical source of truth, providing the authoritative indicator schema so your strategy JSON only includes fields permitted for the selected indicator type.

How do I ensure my strategy JSON matches server-supported indicator fields?

Ensure your strategy JSON matches server-supported fields by fetching the canonical indicator schema via MCP and building indicator objects that only include permitted type, period, and property values.