Strategy Translator

Translate trading strategies between different frameworks and languages. Use when converting Pine Script to Python, porting strategies to NautilusTrader, or...

Security Scan

The skill is an instruction-only translator for trading strategies whose requested actions and artifacts align with its stated purpose and it does not request unrelated credentials or installs.

Purpose & Capability

The name/description (translating trading strategies between languages/frameworks) matches the SKILL.md: it asks for objectives, data, constraints and promises code/docs output. There are no unexpected binaries, env vars, or config paths required. The package metadata notes an external source URL but absence of upstream code is explained in references/SOURCE.md.

Instruction Scope

Runtime instructions are focused on eliciting task inputs, producing a plan and repo-ready deliverables (code, docs, run command) and on validation gates. The SKILL.md does not instruct the agent to read system files, secrets, or to contact external endpoints beyond the cited source link; it stays within the stated scope.

Install Mechanism

There is no install specification and no code files to execute — this is instruction-only, which minimizes installation risk. The asset/reference README files are static documentation only.

Credentials

The skill requests no environment variables, credentials, or config paths. While practical usage (e.g., running backtests or accessing market data) may require external API keys or data access, those are not requested by the skill itself and therefore there is no disproportionate credential request in the package.

Persistence & Privilege

The skill does not request persistent presence (always:false) and does not modify other skills or system-wide settings. Model/autonomous invocation is allowed by default (disable-model-invocation:false), which is normal for skills — nothing in the package tries to escalate privilege or persist.

Assessment

This skill is instruction-only and internally consistent with its stated purpose. Before using: 1) Review any generated code before running it — trading/backtest code can cause financial loss and may contain bugs. 2) Be cautious about supplying real API keys or production data to the agent; the skill does not request credentials but real-world translation + testing may require them, so provide secrets only in controlled environments. 3) If you do not want the agent to invoke this skill autonomously, disable autonomous invocation in your agent settings. 4) Verify any external source links (the package references an MCPMarket page and says some upstream links are missing) before relying on external artifacts.

Source: https://mcpmarket.com/tools/skills/strategy-translator

Use When

• You need to apply this capability as part of trading research workflows (data, features, backtests, ML, reporting).
• You want a reproducible output that can be committed to this repo (code, configs, docs).

Inputs To Ask For

• Objective: what success looks like (metric, constraints, time horizon).
• Data: symbols, timeframe, sampling, data sources, and leakage risks.
• Constraints: compute budget, latency, interpretability, and deployment requirements.

Outputs

• A concrete plan (steps + checks).
• A minimal implementation sketch (files to create/change) and verification steps.
• If applicable: a risk checklist (leakage, overfitting, evaluation pitfalls).

Workflow

1. Restate the task in measurable terms.
2. Enumerate required artifacts (datasets, features, configs, scripts, reports).
3. Propose a default approach and 1-2 alternatives.
4. Add validation gates (walk-forward, Monte Carlo, sanity checks).
5. Produce repo-ready deliverables (code + docs) and a run command.