mcpbeat

Llmquant Portfolio Lab

llmquant/llmquant-portfolio-lab

Router skill for LLMQuant portfolio-lab workflows. Use when the user needs portfolio exposure maps, what-if simulations, scenario states, or virtual portfolio comparisons.

1k tokens
context cost
the whole folder, loaded on every use
5
files
ships runnable scripts
0
copies elsewhere
how many repositories repackaged it
183
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/LLMQuant/skills --skill llmquant-portfolio-lab

The instruction itself

4 sections, as written by the author

LLMQuant Portfolio Lab

This category routes portfolio virtualization workflows: exposure maps, scenario states, and what-if simulations for real or hypothetical portfolios.

Routing Rules

  • Identify portfolio ID, holdings list, benchmark, scenario, and requested visualization/output.
  • Select the closest workflow below.
  • Open only that workflow and relevant local assets/scripts.
  • Use LLMQuant Data for positions, prices, ETF look-through, factors, scenarios, and risk model outputs.
  • Report as-of dates, model dates, benchmark, missing holdings, and unsupported asset types.

Workflow Index

| User intent | Workflow |

|---|---|

| Map portfolio exposure by holdings, sectors, factors, geography, ETF look-through, and concentration. | workflows/portfolio-exposure-map.md |

| Simulate adds, trims, hedges, shocks, and virtual portfolio states. | workflows/portfolio-what-if-simulator.md |

LLMQuant Data Contract

Prefer LLMQuant Data when available. The workflows may need these data capabilities:

  • Retrieve portfolio holdings, weights, cost basis, asset types, benchmarks, and as-of dates.
  • Retrieve factor exposures, sector/geography exposures, ETF look-through holdings, risk model outputs, and scenario simulation results.
  • Retrieve prices, correlations, drawdowns, volatility, option Greeks, and hedge context when relevant.
  • Compare current, pro forma, and hypothetical portfolio states.

Fallback:

  • If portfolio APIs are unavailable, ask for a holdings table or build a structured portfolio input template.
  • Do not invent weights, holdings, factor exposures, or scenario returns.

How to use it

Copy the folder

Take llmquant/llmquant-portfolio-lab from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.