Use when the user asks to compare data and research teams, mature shadow scores or the event/quality/sector contest recipes.
75%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.agents/skills/quant-contest-trade/SKILL.mdUse 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.
egs/skills_examples/quant-contest-trade.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.skill: quant-contest-trade. Credentials belong in project environment configuration, never in the YAML or prompt. Use the project's existing Python environment.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.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.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.
charliedream1/ai_quant_trade
f209fb3
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.