model:pr-submit

Validates model PR metadata against ModelSpec schema and writes approved entries to shared blackboard.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It standardizes how quantitative model pull requests are reviewed, validated, and handed off, ensuring every shared model entry carries real metadata, passes contract validation, and is written with explicit version-controlled approval. ## Core Features & Use Cases - PR Metadata Extraction: Reads authorized GitHub PRs and commits to collect training data timestamps, model type, hyperparameters, feature dependencies, and risk metadata without fabricating defaults. - ModelSpec Contract Validation: Runs candidate metadata through the published generate_model_spec tool for real schemas.model.ModelSpec validation rather than trusting model-generated content. - Versioned Shared Handoff: Reads the current shared.model_entries blackboard version and proposes writes with expected_version so merges require explicit user approval. - Use Case: A quant researcher finishes a factor model PR and needs it registered for the risk team; this Skill validates the ModelSpec, freezes the task plan, and completes the shared handoff only after the user approves the exact merge. ## Quick Start Ask the agent to process an authorized model PR, validate its ModelSpec metadata, and submit it to the shared model entries blackboard for approval.

Frequently Asked Questions about model:pr-submit

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

FAQPage Schema
How do I submit a model PR for shared handoff?

Provide the real PR or commit reference plus training data timestamps, model type, hyperparameters, and risk metadata. The Skill reads the PR, validates a ModelSpec via generate_model_spec, then proposes a versioned blackboard write that you must explicitly approve.

What metadata is required for ModelSpec validation?

You need the real PR or commit reference, training data time point, model type, hyperparameters, feature and operator dependencies, and risk metadata. Missing fields must be filled with real values; default dates or placeholder factors are rejected.

Does the shared blackboard write happen automatically?

No. The Skill reads the current version of shared.model_entries.<entry_id> and proposes a write with expected_version, but the exact merge requires explicit user approval. The tool cannot confirm on the user's behalf.

What happens if the shared write service is not configured?

The Skill stops at a reviewable contract and evidence stage and does not claim the handoff succeeded. It will not fall back to legacy queue writes or retry with guessed versions when the result is unclear.

Can this Skill switch groups or expose credentials?

No. Identity and GitHub visibility come from the host session, parameters cannot switch groups, and secrets never enter task text, the blackboard, or artifacts.