model

Orchestrates quantitative model research tasks with ModelSpec contracts and risk handoff.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Quantitative model research involves literature review, model specification, training component integration, and risk handoff, all of which must follow organizational authorization and traceability rules. This Skill defines the model group's task workflow so that every step uses verified capabilities, shared memory, and authoritative training components instead of unverified assumptions. ## Core Features & Use Cases - Capability-First Execution: Queries list_capabilities and search_memory before acting, verifying the real integration status of models, features, labels, and training components. - ModelSpec Contract Output: Produces schemas.model.ModelSpec with fields like model_name, model_type, training data ranges, hyperparameters, feature dependencies, and risk metadata, explicitly flagging missing values instead of using mock data. - Governed Human Gates: Uses organization_reuse and organization_solution for coverage decisions and plan approval, with exact merge/permission approval for shared writes. - Use Case: A model group member starts a task to define a new factor model; the Skill guides them to check component availability, load the model-lit-review sub-skill for literature work, call authoritative training and OOS components, and deliver a traceable ModelSpec for risk team review. ## Quick Start Start a new model group task and ask the agent to verify available training components, review relevant literature, and produce a ModelSpec for the proposed model.

Frequently Asked Questions about model

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

FAQPage Schema
How do I run a model research task in the model group workflow?

Start by querying list_capabilities and search_memory to verify real component status, then use organization_solution to propose goals and file scope. After user confirmation, load model-lit-review or model-pr-submit sub-skills and call authoritative training components for execution.

What fields does the ModelSpec schema require?

ModelSpec requires model_name, model_type, code_path, training_data_start, training_data_end, as_of_date, hyperparameters, feature_dependencies, operator_dependencies, and risk_metadata. Missing real values must be explicitly listed rather than filled with UNKNOWN or mock data.

Does the model skill handle risk approval for production deployment?

No, risk determination is owned by the dedicated risk component. The model group delivers ModelSpec contracts and traceable results but does not claim final risk clearance or production deployment success.

What happens when a required training component is unavailable?

The workflow preserves UNAVAILABLE, PARTIAL, or STAGING status markers instead of fabricating results. The user decides next steps through the task interface, and capability shortfalls cannot be overridden by Skill text or model assertions.

Can the model skill delegate tasks to an external Python agent?

No, all work runs in the current native QuantCode task using the host-provided model configuration. Parallel work uses the engine's native subtask tools, which inherit the parent task's identity, directories, budget, and plan.