skills.rest
Yasuui
YasuuiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

evolve-bug-fix-may18

Fix strategy routing by extracting strategy_name from trade.strategy_name or trade.strategy.

4|1|Updated May 15, 2026
Search Tags:#bug fix#runtime validation#production incident#key mismatch#strategy learner#trade logging#data schema compatibility
One-click install
npx skills add https://github.com/Yasuui/hermes-community-skills --skill evolve-bug-fix-may18
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: evolve-bug-fix-may18
Source: https://github.com/Yasuui/hermes-community-skills/tree/main/skills/community/evolve-bug-fix-may18
Command: npx skills add https://github.com/Yasuui/hermes-community-skills --skill evolve-bug-fix-may18

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill resolves a production bug where trade logging stored strategy names under the wrong JSON key, causing strategies to be misclassified and lookups to fail during evolution.

Core Features & Use Cases

  • Key mismatch root-cause analysis: Identifies why strategy_name fell back to "default" when upstream payloads used "strategy".
  • Robust key fallback behavior: Updates extraction logic to accept either strategy_name or strategy so evolution targets the intended strategy.
  • Practical schema documentation guidance: Provides a lesson to prevent recurrence by documenting accepted key variants for shared JSON schemas.
  • Use Case Example: When a trading launcher sends {"trade":{"strategy":"owl-alpha-v3"}}, this Skill’s fix ensures logging and evolve both consistently recognize owl-alpha-v3 instead of silently using "default".

Quick Start

Update your trade logging and evolve pipeline to extract strategy_name from either strategy_name or strategy so the correct strategy is used during database evolution.

Frequently Asked Questions about evolve-bug-fix-may18

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

FAQPage Schema
Why does my strategy learner fall back to default during evolution?▼

Strategy learner evolution falls back to default when trade logging stores the strategy name under a mismatched JSON key, causing the extraction logic to miss the intended strategy and bucket it incorrectly.

How do I fix trade logging key mismatches for strategy_name in JSON payloads?▼

Fix trade logging key mismatches by implementing a fallback extraction chain that checks for strategy_name or strategy, ensuring the pipeline recognizes the correct strategy identifier from upstream payloads.

What causes strategy mis-bucketing and not_found lookups in a trading pipeline?▼

Strategy mis-bucketing and not_found lookups occur when upstream trading launchers send JSON payloads with different key variants for strategy identifiers, breaking the data schema compatibility needed for accurate strategy routing.

Can I use a fallback extraction chain for both sandbox and unified launcher payloads?▼

Yes, applying a fallback extraction chain for strategy_name from either strategy_name or strategy works across both sandbox and unified launcher payloads, ensuring persisted trade records remain compatible with the evolve workflow.

What is the best way to document accepted JSON key variants for shared data schemas?▼

Document accepted JSON key variants by explicitly listing allowed fields like strategy_name and strategy in your shared data schema documentation, preventing future extraction failures and ensuring runtime validation consistency.

How do I prevent data schema compatibility issues when evolving trading strategies?▼

Prevent data schema compatibility issues by updating trade logging and evolve pipelines to accept multiple key variants for strategy identifiers, ensuring correct strategy routing during database evolution from persisted records.

Related Skills

Explore More Software Engineering Skills→
Sahib-Sawhney-WHSahib-Sawhney-WH
4

error-codes

Diagnose DAPR error codes with root-cause analysis and remediation steps.

Community
Basic
adennngadennng
33

attempt-evaluation

Automate SignalAgent strategy evaluation with parameter search and backtesting.

Community
Intermediate
Renzo-TognellaRenzo-Tognella

implementing-api-schema-validation-security

Implement API schema validation with OpenAPI and JSON Schema to prevent injection and mass assignment.

Community
Advanced
kennypallchizaca-coderkennypallchizaca-coder

05-data-persistence

Define persistence layers with entities, repository interfaces, and migrations.

Community
Advanced