pine-script

Export backtest strategies to indicator/strategy code for major trading platforms — TradingView, 通达信, 同花顺, 东方财富, MT5.

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./agent/src/skills/pine-script/SKILL.md

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with complete, copy-paste-ready templates and mapping tables for all three platforms, and its workflows are clearly sequenced with a verification checklist. Its main weaknesses are that the large per-platform reference material is inlined in one file rather than split into reference files, and validation is a final checklist rather than an integrated feedback loop.

Suggestions

Move the per-platform reference blocks (Pine/TDX/MQL5 mapping tables and templates) into separate reference files (e.g. references/pine.md, references/tdx.md, references/mql5.md) and keep SKILL.md as an overview with one-level-deep links.

Add an inline validation checkpoint inside the export workflow — e.g. after translating, verify entry/exit conditions match the Python signal logic across all platforms before write_file — with a fix-and-retry loop.

Trim the symbol-format and limitations tables or move them into a reference file to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is dense reference material (mapping tables, templates, syntax rules) with almost no padding of concepts Claude already knows, though it is long and carries some redundancy (symbol-format and limitations tables). Matches anchor 4 (efficient; minor instances that could be trimmed); not 5 because the inlined bulk and minor redundancy mean not every token is maximally earned.	4 / 5
Actionability	It provides copy-paste-ready templates for all three platforms (Pine `//@version=6` strategy header, TDX formula with assignment/color syntax, MQL5 OnInit/OnCalculate with SetIndexBuffer) plus complete Python→target function mapping tables with exact names. Matches anchor 5 (fully executable; copy-paste ready; common cases covered); the placeholder markers are appropriate scaffolding, not pseudocode.	5 / 5
Workflow Clarity	Two clearly numbered workflows (export-from-backtest, generate-from-description) are given with read_file/write_file commands, and a Quality Checklist provides verification, but validation is a detached final gate rather than inline checkpoints with feedback loops. Matches anchor 4 (clear sequence with most checkpoints; minor validation gaps); not 5 because there is no integrated validate→fix→retry loop within the workflow steps.	4 / 5
Progressive Disclosure	No bundle files exist, so all ~300 lines of per-platform mapping tables and templates are inlined in a single SKILL.md well over 50 lines, which the simple-skill exception does not cover. Matches anchor 3 (some structure but content that should be separate is inline); the section headers are well organized, which keeps it from 2, but the bulk reference belongs in separate files to reach 4-5.	3 / 5
	Total	16 / 20 Passed

Description

53%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly states what the skill does and names concrete target platforms, giving it a distinct niche, but it omits any "Use when..." trigger guidance and the language-level synonyms (Pine Script, MQL5, TDX) that users most naturally say. These gaps cap completeness and trigger-term quality at the midpoint.

Suggestions

Add an explicit trigger clause, e.g. "Use when exporting a Vibe-Trading backtest to TradingView (Pine Script), 通达信/同花顺/东方财富 (TDX), or MT5 (MQL5)."

Include the natural language-level synonyms users say — "Pine Script", "MQL5", "TDX formula" — alongside the platform names.

Optionally enumerate a second concrete action (e.g. "generate indicators from a plain-language description") to lift specificity toward 4-5.

Dimension	Reasoning	Score
Specificity	Names the domain and one concrete action ("Export backtest strategies to indicator/strategy code") plus a platform list, but lists only a single action rather than several. Matches anchor 3 (domain + 1-2 concrete actions, not comprehensive); not 4 because it does not enumerate several specific actions.	3 / 5
Completeness	The description gives a clear "what" (export backtest strategies to indicator/strategy code) but includes no "Use when..." trigger guidance, which caps completeness at 3 per the judging guidelines. Matches anchor 3 (clear what, when missing); not 4 because there is no explicit when clause at all.	3 / 5
Trigger Term Quality	Platform names (TradingView, 通达信, 同花顺, 东方财富, MT5) are natural user terms, but common language synonyms users actually say ("Pine Script", "MQL5", "TDX formula") are absent. Matches anchor 3 (some relevant keywords but missing common variations or synonyms); not 4 because the most natural language-level triggers are missing.	3 / 5
Distinctiveness Conflict Risk	The niche (exporting backtest strategies to specific named trading platforms) is clear and distinct with low conflict risk, though it could overlap slightly with general Pine Script or trading skills. Matches anchor 4 (mostly distinct; minor overlap risk); not 5 because it lacks the explicit trigger phrasing of the anchor-5 example.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: HKUDS/Vibe-Trading
Path: agent/src/skills/pine-script/SKILL.md
Commit: f9cb061

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.