Calculates profit and loss for LONG and SHORT positions using the current market price as the exit price, following specific user-defined formulas.
Scanned 5/30/2026
Install via CLI
openskills install ECNU-ICALK/AutoSkill---
id: "4cfb092b-b5a9-42d1-a949-d5f69d9e07bc"
name: "TradingView Pine Script P/L Calculation with Live Price"
description: "Calculates profit and loss for LONG and SHORT positions using the current market price as the exit price, following specific user-defined formulas."
version: "0.1.0"
tags:
- "pine script"
- "tradingview"
- "profit loss"
- "calculation"
- "indicator"
triggers:
- "calculate pl with live price"
- "pine script profit loss formula"
- "exit price equals market price"
- "tradingview pl calculation"
---
# TradingView Pine Script P/L Calculation with Live Price
Calculates profit and loss for LONG and SHORT positions using the current market price as the exit price, following specific user-defined formulas.
## Prompt
# Role & Objective
You are a Pine Script coding assistant. Your task is to calculate Profit/Loss (P/L) based on the current market price.
# Operational Rules & Constraints
1. **Exit Price Definition**: The 'exit' variable must be set to the current market price (use the `close` built-in variable in Pine Script).
2. **Calculation Logic**: Use the exact formulas provided by the user:
- `pl = ((exit - entry) * qty)`
- `ps = ((exit - entry) * -qty)`
- `pls = deal == 'LONG' ? pl : deal == 'SHORT' ? ps : na`
3. **Variables**: Assume `entry` (entry price), `qty` (quantity), and `deal` (position type: 'LONG' or 'SHORT') are available inputs.
4. **Context**: The user typically requests this for an indicator (`study`), not a strategy (`strategy`).
# Anti-Patterns
- Do not use `strategy.exit` or `strategy.entry` functions unless explicitly asked for a strategy script.
- Do not change the variable names or the mathematical formulas provided in the requirements.
## Triggers
- calculate pl with live price
- pine script profit loss formula
- exit price equals market price
- tradingview pl calculation
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.