Define performance monitoring metrics and thresholds for production ML deployments.
npx skills add https://github.com/gtylee/CodexGAS --skill opm-tailoring
Please help me install this Agent Skill. Skill: OPM Tailoring Source: https://github.com/gtylee/CodexGAS/tree/main/modelgas/skills/opm Command: npx skills add https://github.com/gtylee/CodexGAS --skill opm-tailoring
This Skill defines ongoing performance monitoring metrics and thresholds, enabling proactive detection of production-model degradation and stability issues.
Provide risk tier context and observed metrics to generate a tailored OPM monitoring plan. Use the generated templates to implement metrics collection and alerting in your production environment.
High-intent search queries and answers about installing and using this skill.
Ongoing performance monitoring for production ML models continuously tracks degradation and stability using defined metrics and threshold bands. It detects drift, latency issues, and reliability drops to enable proactive incident response and escalation.
You set thresholds for model drift detection by defining threshold bands with clear breach and escalation logic. This process tailors monitoring metrics to specific risk tiers and usage patterns, generating notification-ready outputs for dashboards.
Yes, you can monitor models across different risk tiers. The system selects production monitoring metrics specifically aligned to your defined risk tier and usage patterns, ensuring threshold bands match the model's operational context.
To track model performance in production, you need metrics covering drift detection, latency targets, and reliability. You must provide observable production data and risk tier context to generate a tailored monitoring plan with standard error thresholds and rerun stability.
To generate alerting templates for production model degradation, provide observed metrics and risk tier context. The system outputs schema-conforming findings with breach and escalation logic, suitable for implementing metrics collection and alerting in your environment.
A key limitation is the requirement for observable production data; the system cannot generate monitoring plans without it. Additionally, outputs are structured around specific findings like standard error thresholds and rerun stability, requiring compatible dashboard integration.
sunLeeeDefine monitoring and alerting conventions for production systems.
girijashankarjConfigure metrics, logs, traces, dashboards, and runbooks for microservice monitoring.
camoneartDesign and deploy Grafana dashboards for real-time system and application metrics.
pluginagentmarketplaceDetect data and model drift in production ML deployments.
