Search the docs, videos, blog, apps, teams, skills and release notes.
At a glance
What it is
Migrate Pine Script v4 / v5 source to v6, analyze, apply migration rules, compile-check, iterate until clean.
A skill is a written procedure a bot loads when a job calls for it. This one is a single file, SKILL.md, and the whole file is on this page.
The whole file, exactly as it downloads. Read it before you rely on it.
SKILL.md
108 lines · 764 words
You are migrating an older Pine Script to v6. Work iteratively: analyze → rewrite → compile → fix.
Power-toolkit shortcut:
pine_checkdoes a server-side compile without touching the chart — use it between rewrite passes to fail fast on syntax errors before doing a fullpine_smart_compileround.pine_analyze(offline) covers v4/v5 deprecation flags.
Migrate Pine Script v4 / v5 source to v6, analyze, apply migration rules, compile-check, iterate until clean.
Nothing. It ships with Murage, which is open source. Your bots run on the AI plan you already have.
Yes. Open it in Settings → Skills to read, edit or duplicate it. Skill Guard scans it again after every edit.
Download the app, connect the AI you already pay for, and tell your Chief of Staff what needs doing. Plan on about ten minutes from install to a working team.
No account needed · Runs on the AI plan you already pay for
Paste it into your agent's instructions (CLAUDE.md, AGENTS.md or a custom GPT), or add it to a bot in Murage.
Ask Ember for the bot, then switch the skill on in its settings.
Step 1
Send your Chief of Staff this message. It proposes the bot and its role first, and creates it when you say go.
Send this to Ember
“Create a bot that uses the Porting Pine v4 / v5 → v6 skill, and show me the plan first.”
You're done when your Chief proposes the bot and its role, and the bot appears in your sidebar once you say go.
Step 2
You're done when you see the bot’s skills and the library.
Step 3
You're done when the skill shows as on for that bot.
Step 4
You're done when the bot takes the job and opens the skill when it needs it.
Prefer to do it yourself? Choose + in the sidebar, then New Bot.Read the full guide to skills and Skill Guard
What it teaches a bot, what it covers, and the whole file to read.
The principle
You are migrating an older Pine Script to v6. Work iteratively: analyze → rewrite → compile → fix.
What it covers
Step 1: Pull + Identify the Version
Step 2: Apply Migration Rules
Step 3: Rewrite Locally
Step 4: Compile-Check Server-Side
Step 5: Iterate Until Clean
Step 6: Push + Verify
Step 7: Report
Error Notes
pine_get_source — read the current source (skip if the user pasted it in chat)
pine_analyze — the analyzer flags v<6 scripts explicitly; also surfaces deprecated calls
Look at the first non-comment line:
//@version=4 → v4
//@version=5 → v5
missing / //@version=6 → nothing to do
Update the version header first: //@version=6. Then apply these rewrites.
| v4 | v6 |
|---|---|
study("Name", overlay=true) | indicator("Name", overlay=true) |
security(...) | request.security(...) |
sma(x, n) | ta.sma(x, n) |
ema(x, n) | ta.ema(x, n) |
rsi(x, n) | ta.rsi(x, n) |
crossover(a, b) | ta.crossover(a, b) |
crossunder(a, b) | ta.crossunder(a, b) |
highest(x, n) | ta.highest(x, n) |
lowest(x, n) | ta.lowest(x, n) |
atr(n) | ta.atr(n) |
tostring(x) | str.tostring(x) |
tonumber(x) | str.tonumber(x) |
nz(x) | nz(x) (unchanged) |
input(..., type=input.integer) | input.int(...) |
input(..., type=input.float) | input.float(...) |
input(..., type=input.bool) | input.bool(...) |
iff(cond, a, b) | ternary cond ? a : b |
valuewhen(cond, src, n) | ta.valuewhen(cond, src, n) |
Most ta.*, str.*, math.*, array.*, input.* namespaces already exist in v5. Main v6 changes:
//@version=5 → //@version=6
Some drawing/style constants renamed — trust the compiler errors to guide you
plot.style_* constants: verify they still exist; the compiler will flag drops
Strict type inference — add explicit types (float, int, bool) on var declarations where the compiler now requires them
request.security lookahead param default tightened; be explicit: lookahead=barmerge.lookahead_off
4-space indentation (never braces)
Every script declares exactly one of indicator(), strategy(), or library()
Series vs simple typing is stricter in v6 — if compiler complains, often you need input.int(..., defval=14) instead of raw int assignments
Edit the source as a single coherent pass — don't piecemeal if the script is short. For long scripts (500+ lines), port function-by-function and re-check after each.
pine_check — server-side compile of the rewritten source. Cheaper than a full pine_set_source + pine_smart_compile cycle because it doesn't mutate the live editor.
Read errors. Common post-migration breakage:
Could not find function 'xxx' → likely still a v4 bareword; prefix with ta. / str. / math.
Cannot call 'input' with arguments... → switch to the typed variants input.int / input.float / input.bool / input.string
Syntax error at input 'study' → rename to indicator
Series type required → explicit cast, e.g., float src = close
Loop:
Fix the next error in the local source
pine_check again
Stop when error count is 0 and warnings are acceptable
Don't push to the editor until pine_check is clean — saves round-trips.
pine_set_source — inject the clean v6 source
pine_smart_compile — final in-editor compile (catches anything pine_check missed)
pine_get_errors — confirm zero
capture_screenshot — visual sanity check that plots still render as expected
If it's a strategy: data_get_strategy_results — compare metrics vs the v4/v5 baseline the user recorded previously (regressions here usually indicate a subtle porting bug like lookahead semantics)
Version bumped: v4 → v6 (or v5 → v6)
Rewrites applied: count of study→indicator, security→request.security, ta.* prefix adds, input.* typed conversions, etc.
Behavioral deltas to watch: flag any lookahead, barmerge, or math.round_to_mintick changes that could shift backtest numbers
Final compile status and screenshot path
PINE_COMPILE_ERROR — iterate; don't declare done
If pine_get_source returns a huge blob, work in the local file and avoid re-reading unless needed (see CLAUDE.md rule 4 on context)
SKILL.md
108 lines · 764 words
The text of SKILL.md is shown as it downloads, under the Apache-2.0 license, by Ferrox Labs. The license is the one in the file's own frontmatter.
Your new bot
Porting Pine v4 / v5 → v6 bot
Waiting in your sidebar once you say go.
No account needed · Runs on the AI plan you already pay for