skills.rest
lgbarn
lgbarnCOMMUNITY
Explore all skills by this author →
GitHub

cross-platform-consistency

Flag indicator calculation drift across trading platforms after code modifications.

Updated Aug 23, 2026
Search Tags:#consistency#validation#cross-platform#drift#trading#indicator
One-click install
npx skills add https://github.com/lgbarn/quantdev --skill cross-platform-consistency
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cross-platform-consistency
Source: https://github.com/lgbarn/quantdev/tree/main/skills/cross-platform-consistency
Command: npx skills add https://github.com/lgbarn/quantdev --skill cross-platform-consistency

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the critical issue of indicator implementation drift across different trading platforms, which can lead to divergent signals and flawed backtests.

Core Features & Use Cases

  • Drift Detection: Identifies when indicator logic may have diverged between platforms (e.g., Go, Python, Pine Script, NinjaScript).
  • Validation Reminder: Prompts users to run cross-platform validation after any indicator code changes.
  • Use Case: After updating the ATR calculation in your Go indicator, this Skill ensures you remember to validate that the Pine Script and NinjaScript versions of the same indicator produce identical results within defined tolerances.

Quick Start

Remind me to validate the 'keltner' indicator across all platforms after I make a change to its Go implementation.

Frequently Asked Questions about cross-platform-consistency

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

FAQPage Schema
How do I prevent indicator calculation drift across multiple trading platforms?▼

Cross-platform validation detects indicator implementation drift by enforcing a single source of truth for math calculations and prompting validation procedures after code modifications. This ensures signals match within defined tolerances.

Why do my trading indicators show different signals on different platforms?▼

Trading indicators show different signals due to implementation drift across platforms. Validating indicator calculations against golden files after code modifications enforces a single source of truth and ensures outputs match within defined tolerances.

What is the best way to validate indicator math consistency after a code change?▼

The best way to validate indicator math consistency is to run golden file validation procedures across all platform implementations after modifying indicator code. This enforces a single source of truth and flags potential calculation drift.

Does this cross-platform validation approach work with Pine Script and NinjaScript?▼

Yes, this cross-platform validation applies to scenarios involving Pine Script, NinjaScript, Go, and Python. It ensures indicator calculations produce identical results within defined tolerances after any code modifications.

When do I need to run cross-platform validation for my trading indicators?▼

You need to run cross-platform validation for your trading indicators immediately after any indicator code modifications. This procedure detects potential calculation drift early and enforces a single source of truth for indicator math.

Related Skills

Explore More Software Engineering Skills→
nikhillinitnikhillinit

test-fixture-generator

Generate test fixtures and golden datasets via factories with schema validation.

Community
Intermediate
plurigridplurigrid
60

gay-mcp

Generate deterministic color palettes from seeds using SplitMix64 and golden-angle coloring.

Official
Advanced
masermediagroup-stackmasermediagroup-stack
1

implementing-gitops

Automate Kubernetes deployment across clusters using ArgoCD or Flux.

Community
Advanced
FaisalAlqarniFaisalAlqarni
5

flutter-verification

Verify Flutter applications through unit, integration, golden, performance, accessibility, and platform-specific testing.

Community
Advanced