pine-develop — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited pine-develop (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
You are developing a Pine Script indicator or strategy in TradingView. Follow this loop precisely.
If not already clear, ask the user:
If modifying an existing script:
node scripts/pine_pull.jsThen read scripts/current.pine to understand what's there.
If creating new: start from scratch.
Write the complete script to scripts/current.pine. Every script MUST include:
//@version=6 headerindicator() or strategy() declarationinput.*() functions and groupsFor strategies, include:
strategy.entry() and strategy.exit() callsstrategy() declarationnode scripts/pine_push.jsThis injects the code into TradingView's Pine Editor, clicks compile, and reports any errors.
If errors are reported:
scripts/current.pine locally — fix the specific linesnode scripts/pine_push.jsCommon Pine Script errors:
After clean compilation:
capture_screenshot — take a screenshot to verify it looks rightdata_get_strategy_results — if it's a strategy, check performanceIf the user wants changes:
node scripts/pine_pull.js (in case TV modified anything)IMPORTANT: Always compile after every change. Never claim "done" without a clean compile.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.