CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

quant-backtest-review

Use when the user asks analyst, risk, reviewer and chair agents to review an existing backtest with cited evidence.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/quant-backtest-review/SKILL.md
SKILL.md
Quality
Evals
Security

四角色回测复核

Use the existing platform workflow, not an independent LLM simulation. Locate the project root containing egs/skills.py and work there. See the shared execution guide for provider limits, data fields and research gates.

  1. Read egs/skills_examples/quant-backtest-review.yaml. Resolve the user's actual dataset/backtest ID, date, symbols, provider and budget. Example IDs are placeholders, not existing data. Ask only for information that cannot be found in the project or user request.
  2. Create the task YAML inside the project; keep skill: quant-backtest-review. Credentials belong in project environment configuration, never in the YAML or prompt. Use the project's existing Python environment.
  3. Run python egs/skills.py preview --config <task.yaml>. Use providers --probe when backend availability is uncertain. An installed CLI can still lack authentication or strict role eligibility; do not silently switch provider or relax permissions.
  4. Run python egs/skills.py run --config <task.yaml> --format jsonl once. This is a foreground process. Preserve the returned run ID and actual events; use show, events, files or cancel with that ID. Do not launch recursive Skills from a model-provider subprocess.
  5. Present the actual terminal status and HTML path. Distinguish protocol fixtures, real model calls and financial effectiveness. Do not fabricate AR/IC/drawdown, skip missing PIT evidence, treat unknown usage as zero, or claim research approval permits live trading.

Keep the existing economic/technical review and shared cost/risk ledger. When evidence is missing, report the missing fields and retain failed-run evidence instead of repeating paid calls.

Repository

charliedream1/ai_quant_trade

Path

.agents/skills/quant-backtest-review/SKILL.md

Last updated
First committed

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.