stock-buddy

Debug Stock Buddy's TradingView webhook integration across APIs, database, and frontend.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Samaara-Das/Tradingview-to-Everywhere --skill stock-buddy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stock-buddy
Source: https://github.com/Samaara-Das/Tradingview-to-Everywhere/tree/main/.claude/skills/stock-buddy
Command: npx skills add https://github.com/Samaara-Das/Tradingview-to-Everywhere --skill stock-buddy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Stock Buddy skill helps engineers understand and debug the end-to-end Stock Buddy web application and its integration with TradingView via TTE, including REST APIs, data models, and frontend signal visualization.

Core Features & Use Cases

  • Two-tier signal workflow: explains NWE and OBDIV data paths and how signals are confirmed.
  • API endpoints & data models: documents the REST endpoints, collections, and schemas used by TTE and Stock Buddy.
  • Rotation, hot-list, and lifecycle: covers symbol rotation, hot symbols, expiration, and signal lifecycle.
  • Frontend signal display: describes UI components that render signals and status.

Quick Start

Explore the Stock Buddy integration by following the quick-start guide to inspect APIs, flows, and frontend components.

Frequently Asked Questions about stock-buddy

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

FAQPage Schema
How do I debug a TradingView webhook integration in a Next.js application?

Debug TradingView webhook integration by tracing the end-to-end Stock Buddy workflow, inspecting Next.js API routes, the Python orchestrator, and MongoDB collections to identify where signal data fails to persist or route correctly.

How does the two-tier signal confirmation workflow process NWE and OBDIV data paths?

The two-tier signal workflow processes NWE and OBDIV data paths by validating incoming TradingView webhook payloads and confirming signals through the Python orchestrator before visualizing them on the frontend components.

What is the best way to manage MongoDB schema changes for stock signal rotations and hot lists?

Manage MongoDB schema changes for signal rotations by referencing the documented collections and schemas, ensuring hot symbols, expiration rules, and rotation state align with the REST API endpoints handling lifecycle events.

Does this Stock Buddy workflow support custom combo and tiered signal logic?

The workflow supports custom combo and tiered signal logic by allowing modifications to the Python orchestrator and MongoDB collections, enabling engineers to adjust how TradingView webhooks trigger and confirm complex multi-stage signals.

Why are my frontend signal visualization components not displaying updated rotation state?

Frontend signal visualization components fail to display updated rotation state when Next.js API routes return stale data, making it necessary to debug the MongoDB queries and Python orchestrator feeding the UI components.