pinescript

v2.56.0

Pine Script v6 patterns: syntax, performance, error diagnosis, backtesting, visualization. Use when working with PineScript, TradingView, indicators, strateg...

0· 127·0 current·0 all-time
byIlia Alshanetsky@iliaal
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description (Pine Script guidance for TradingView) matches the SKILL.md content: syntax rules, performance tips, debugging patterns, backtesting and publishing guidance. The skill requests no binaries, env vars, or config paths — appropriate for a documentation-style helper.
Instruction Scope
SKILL.md contains purely Pine Script development guidance and actionable patterns to use inside TradingView's Pine Editor. It does not instruct the agent to read arbitrary files, access credentials, or transmit data to third-party endpoints. The only external action suggested is to 'search current docs via search_docs' to confirm version-specific syntax, which is reasonable for keeping code up to date.
Install Mechanism
No install spec and no code files are present. As an instruction-only skill, it does not download or write code to disk, which is the lowest-risk install posture.
Credentials
The skill declares no required environment variables or credentials; the guidance does not request secrets or access to unrelated services. This is proportionate for a language/formatting helper for Pine Script.
Persistence & Privilege
The skill is not set to always: true and does not request system-wide configuration changes. Autonomous invocation is allowed (platform default) but combined with the minimal footprint this presents no additional coherence concern.
Assessment
This skill is a documentation-style helper and appears safe and coherent for Pine Script work. Before relying on its recommendations in production: (1) test generated code in TradingView's editor and strategy tester across multiple symbols/timeframes, (2) remove any debug-only constructs before publishing, and (3) verify TradingView's live docs if syntax/version-specific behaviors are critical. If you plan to grant any external tooling access (APIs, build systems), treat those separately — this skill itself does not request credentials or installs.

Like a lobster shell, security has layers — review code before you run it.

latestvk974tzz0kn0703xekzt18nr03x84tp0s

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments