Llmquant Risk

llmquant/llmquant-risk

Router skill for LLMQuant risk workflows. Use when the user needs fear scoring, VIX regime, hedge design, or research health checks.

2k tokens

context cost

the whole folder, loaded on every use

files

ships runnable scripts

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-risk

4 sections, as written by the author

This category routes risk regime, hedging, panic scoring, and research-quality workflows.

Identify the asset, portfolio, risk horizon, drawdown tolerance, and required decision.
Select the closest workflow below.
Open only the selected workflow.
Use LLMQuant Data for prices, volatility, options, macro, portfolio positions, alerts, profiles, and watchlists.
Report timestamps, data windows, stale notices, assumptions, and missing inputs.

| User intent | Workflow |

|---|---|

| Build a per-ticker panic score. | workflows/fear-score.md |

| Translate VIX into an options-risk regime. | workflows/vix-status.md |

| Design protective puts, collars, and put-spread hedges. | workflows/hedge-advisor.md |

| Audit stale profiles, thesis drift, orphan themes, and outdated evidence. | workflows/research-health-check.md |

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

Retrieve price history, volatility, drawdowns, correlations, market regime, VIX context, and macro risk indicators.
Retrieve option chains, implied volatility history, Greeks, hedge candidates, and liquidity context.
Retrieve portfolio positions, watchlists, alerts, research profiles, thesis records, and stale evidence.
Measure hedge cost, risk reduction, concentration, and unresolved data gaps.

Fallback:

If portfolio or option data is unavailable, name the missing input and produce a data-limited risk note.

Copy the folder

Take llmquant/llmquant-risk 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.