risk

Generates RiskProfile reports and CI artifacts from ModelSpec inputs using canonical risk components.

Updated Jun 27, 2026
One-click install
npx skills add https://github.com/HKUST-QUANT-SOCIETY/quantcode --skill risk-hkust-quant-society
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: risk
Source: https://github.com/HKUST-QUANT-SOCIETY/quantcode/tree/main/.opencode/groups/risk/skills/risk
Command: npx skills add https://github.com/HKUST-QUANT-SOCIETY/quantcode --skill risk-hkust-quant-society

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Quantitative research teams need a consistent, auditable way to evaluate model risk before results are accepted. This Skill standardizes risk assessment by converting a ModelSpec into a validated RiskProfile with CI reports and recorded artifacts, so risk verdicts follow one canonical pipeline instead of ad-hoc judgment. ## Core Features & Use Cases - Canonical Risk Pipeline: Runs the risk-ci flow from ModelSpec or ArtifactRef through calc_risk, generate_risk_profile, and risk_verdict to produce a CI report and Artifact. - Contract and Schema Validation: Checks inputs against schemas.model.ModelSpec and outputs schemas.risk_profile.RiskProfile, returning fail or warning verdicts with explicit reasons when limits are breached. - Governed Collaboration: Records reuse decisions with organization_reuse, proposes frozen solutions via organization_solution, and uses permission and merge gates for cross-group reads and shared writes. - Use Case: A strategy group submits a new factor model; the risk group Agent validates the ModelSpec, computes risk metrics, emits a RiskProfile artifact, and returns a warning verdict listing breached thresholds for review. ## Quick Start Ask the risk group Agent to run the risk-ci flow on your ModelSpec and return the RiskProfile artifact with its verdict and reasons.

Frequently Asked Questions about risk

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a RiskProfile from a ModelSpec?

Submit a ModelSpec or ArtifactRef to the risk-ci flow, which runs calc_risk, generate_risk_profile, and risk_verdict in sequence. The output is a RiskProfile conforming to schemas.risk_profile.RiskProfile plus a CI report and recorded artifact.

What happens when risk limits are exceeded?

The risk_verdict step returns a fail or warning status and lists the specific reasons for the breach. It does not trigger a HumanGate, so the verdict and reasons are delivered directly in the CI report.

Can the risk Agent access resources from other groups?

Restricted cross-group reads go through the permission gate, and real writes to shared assets use the merge gate. Adapters not published in the actual tool catalog cannot be called to bypass these limits.

How are stub or mock data handled in risk results?

Any stub, mock, proxy, or staging data must be explicitly labeled in the output. Such results cannot be presented as production risk outcomes, keeping CI artifacts auditable and honest.

What input format does the risk pipeline require?

The pipeline accepts a ModelSpec defined by schemas.model.ModelSpec, or an ArtifactRef pointing to an existing artifact. Inputs are checked against the data contract before the canonical risk component runs.