teaceo-debug/DEEP6 / .claude/skills/tradingview-mcp-trading-operator
tradingview-mcp-trading-operator
Verified| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 949 B |
| knowledge.md | markdown | 2.6 KB |
| workflows/compile-loop.md | markdown | 5.4 KB |
| workflows/object-inspection.md | markdown | 4.8 KB |
| workflows/screenshot-verification.md | markdown | 4.1 KB |
SKILL.md
View on GitHub# TradingView MCP Trading Operator
Invoke this skill when the user asks you to:
- control the TradingView chart through MCP
- read or replace Pine source in the editor
- compile a script on chart and inspect errors, console output, or drawn objects
- take screenshots, query study values, or manage alerts
## Skill Entry Point
Load `knowledge.md` in this directory first.
## Workflow
1. Confirm MCP/TradingView connectivity first.
2. Choose the narrowest workflow: chart state, Pine source, compile, object inspection, screenshot, or alert operation.
3. Follow the tool sequence in `knowledge.md`.
4. Route strategy interpretation to `tradingview-strategy-backtesting-operator` when needed.
## Dependencies
- `tradingview-machine-profile` — connection/routing context
- `tradingview-pinescript-error-doctor` — when compile/runtime issues need diagnosis
## Base path: `C:\Users\Tea\DEEP6\.claude\skills\tradingview-mcp-trading-operator\`
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |