Quant Experiment Runtime

What it does

When your agent uses it

• : a research proposal is ready and you need to actually run the proposed factor/method on real data and get quantitative metrics
• : designing which experiments to run (use experiment-pipeline / paper-planning)
• Debugging a single failed experiment (use experiment-craft)
• Searching papers (use local-paper-navigator)

Example prompts

• “s code-repo, build a panel, run a Research Artifact”
• “/quant-experiment-runtime”

Requirements

• Python 3
• Docker
• Pre-approved tools (allowed-tools): write_file, edit_file, read_file, think_tool, execute

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

1. 1Run discover_data.py --code-repo code-repo → a JSON catalog of every
2. 2Inspect the catalog, pick a dataset, and pass its root to
3. 3data-root / --panel are required, with no default — the dataset name

What it can do on your machine

Read from SKILL.md and the folder at commit ac1c4b8. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves these tools, so the agent can use them without asking each time:

  • write_file
  • edit_file
  • read_file
  • think_tool
  • execute

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Ships 6 files in scripts/ (Python), which the agent can run.

  Shell commands in SKILL.md call:

  • python
  • docker

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md. Its commands use docker, which can reach the network depending on how they are called.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Quant Experiment Runtime loads about 2.5k tokens when it runs, and up to ~5.9k if it reads all its reference files. Until then it costs about 229 tokens; SKILL.md has 795 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~229

When it runs · the whole SKILL.md, loaded when a task matches

~2.5k

With references · SKILL.md plus every file in references/, read only if the agent opens them

~5.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from CamusGIT/EvoQuant at commit ac1c4b8, republished under its Apache-2.0 licence (© CamusGIT). 795 words, ~2,510 tokens.

name

quant-experiment-runtime

description

Quant research experiment executor: discover an offline source database under the workdir's code-repo, build a panel, run a Research Artifact's entry point to compute research-object values, and evaluate IC/ICIR/RANKIC/coverage metrics. Runtime = Experiment Executor; it runs a Research Artifact via a Python-native Entry Point and is agnostic to research-object type and expression form. Self-contained: panel building and IC metrics are implemented inside this skill. The dataset is identified at runtime by discover_data.py (never hard-coded). Use when: a research proposal is ready and you need to actually run the proposed factor/method on real data and get quantitative metrics. Do NOT use for: designing which experiments to run (use experiment-pipeline / paper-planning), debugging a single failed experiment (use experiment-craft), or searching papers (use local-paper-navigator).

allowed-tools

write_file, edit_file, read_file, think_tool, execute

metadata.author

quant-research-team

metadata.version

1.0.0

metadata.tags

core, experimentation, quant, runtime, executor, data, metrics

Workflow (experiment-pipeline)   ── owns when/whether to run
        │
        ▼
Experiment Runtime               ── owns how to run one experiment
        │
        ▼
Research Artifact                ── a runnable research product (py file / package / future workspace|docker|notebook)
        │
        ▼
Entry Point                      ── Python-native callable, e.g. "path/to/code.py::run" or "pkg.mod:run"
        │
        ▼
Results                          ── Runtime does NOT interpret; Metric does
        │
        ▼
Metric (registry, extensible)    ── evaluates; does NOT realign
        │
        ▼
ExperimentResult (+ artifacts/) ── Reflection / downstream Workflow depend only on this

# 1. discover usable datasets under the code-repo (autonomous, no hard-coded names)
python /skills/quant-experiment-runtime/scripts/discover_data.py --code-repo code-repo --out catalog.json

# 2. from catalog.json pick datasets[i].root, then build the panel offline
python /skills/quant-experiment-runtime/scripts/build_panel.py \
  --data-root <selected-dataset-root> \
  --out experiments/<project>/panel_1d.parquet

# 3. run an experiment (single or batch Candidate JSON -> ExperimentResult JSON)
python /skills/quant-experiment-runtime/scripts/run_experiment.py \
  --panel experiments/<project>/panel_1d.parquet \
  --candidate /skills/quant-experiment-runtime/assets/candidate-template.json \
  --label-col label_1d_close_to_close --splits train val \
  --artifacts-dir experiments/<project>/artifacts --out experiments/<project>/result.json

© CamusGIT, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 15 other files (scripts, references, assets) in EvoQuant/skills/quant-experiment-runtime of CamusGIT/EvoQuant.

• SKILL.md
• assets/candidate-template.json
• assets/discover-output-example.json
• assets/experiment-result-schema.json
• assets/research-artifact-example/factor.py
• assets/split-config.example.json
• references/metrics-extension.md
• references/research-code-convention.md
• references/runtime-interface.md
• references/split-policy.md
• scripts/_metrics.py
• scripts/_panel.py
• scripts/build_panel.py
• scripts/discover_data.py
• scripts/experiment_runtime.py
• scripts/run_experiment.py

Open the folder on GitHubat commit ac1c4b8