Q-agent: Skill for Claude Code

Run Local Research Notebook

Use this skill for QuantConnect research notebooks in this workspace. Follow ~/Documents/Q-agent/AGENTS.md first. The key rule is: do not guess from the raw .ipynb file alone when a local LEAN research container already exists.

When To Use

• The user asks to run a notebook under MyProjects/*/research/*.ipynb
• The user wants to debug notebook execution in local LEAN research
• The user wants a plot, table, or notebook output interpreted

Inputs

$ARGUMENTS should be a notebook path such as:

MyProjects/60_40 Test/research/plots.ipynb

If the user gives only a notebook name or a partial path, resolve it before running anything.

Workflow

1. Resolve the notebook and project

• Confirm the notebook exists in the workspace.
• Derive:
  • project_name: parent directory above research/
  • notebook_name: basename, for example plots.ipynb
  • notebook_stem: basename without .ipynb

Read any project-level AGENTS.md, claude.md, or docs/ files if they exist. If they do not exist, continue with the workspace-level AGENTS.md.

2. Prefer an existing research container

List active research containers:

docker ps --format 'table {{.ID}}\t{{.Image}}\t{{.Names}}\t{{.Status}}'

Find the container that has the notebook mounted at /LeanCLI/research/<notebook_name>:

docker exec <container_id> sh -lc 'test -f "/LeanCLI/research/<notebook_name>" && echo NOTEBOOK_PRESENT || echo NOTEBOOK_MISSING'

Use the matching container. This matches the notebook-debugging workflow in AGENTS.md.

3. If no matching container exists

Do not run the notebook with plain local Python.

Ask before launching a new research session because lean research is interactive:

cd ~/Documents/Q-agent
source venv/bin/activate
cd MyProjects
lean research "<ProjectName>"

After the session starts, repeat container discovery and continue inside the container.

4. Execute the notebook headlessly in the container