SkillsAdd

smithery/ajoslin

pinescript

Use when creating or reviewing TradingView Pine Script v6 indicators/strategies/libraries, applying non-repainting best practices, generating Pine Script from other languages, or running Pine Script linting.

Installation

$ npx skills add smithery/ajoslin --skill pinescript
View on skills.sh ↗ Website ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

pinescript Similar name
iliaal/ai-skills

>- Pine Script v6: syntax, performance, error diagnosis, backtesting, visualization. Use when w…

169 installs

Also in this package

Other skills from smithery/ajoslin.

npx skills add smithery/ajoslin
tracer-dev 0 session-export 0

Browse all from smithery/ajoslin

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,681 B
  • docs SUMMARY.md 225 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Pine Script

Overview

Provide Pine Script v6 guidance for indicators, strategies, and libraries. Apply non-repainting and performance best practices. Support generating Pine Script via other languages (TypeScript, Python, etc.) by keeping generated output compliant with v6 guidance. Run linting with the bundled script wrapper around pinescript-lint.

Workflow

  1. Determine script type and version

- Add //@version=6 and choose indicator(), strategy(), or library().

  1. Apply execution model and repainting safeguards

- Use barstate.isconfirmed, historical offsets, and request.security() lookahead guidance.

  1. Optimize performance and state

- Prefer var/varip for state, limit loops, precompute constants, avoid redundant security calls.

  1. Generate Pine Script from other languages when needed

- Emit Pine Script v6-compliant output and validate by inspection or TradingView editor diagnostics.

  1. Lint before delivery (manual Pine Script only)

- Run node scripts/pinescript_lint.mjs <path> to check formatting and basic issues.

References

  • Pine Script v6 concepts and best practices: references/pinescript_v6.md
  • Linting workflow and linter configuration: references/linting.md

Scripts

  • Lint Pine Script files: scripts/pinescript_lint.mjs
  • Lint script tests: scripts/pinescript_lint.test.mjs