model-deployment

Mitigate security vulnerabilities in ML model deployment workflows.

17|1|Updated Jun 8, 2025
One-click install
npx skills add https://github.com/williamzujkowski/standards --skill model-deployment-williamzujkowski
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: model-deployment
Source: https://github.com/williamzujkowski/standards/tree/main/skills/ml-ai/model-deployment
Command: npx skills add https://github.com/williamzujkowski/standards --skill model-deployment-williamzujkowski

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Model deployment standards cover best practices for deploying ML models with reliability, monitoring, and governance.

Core Features & Use Cases

  • Deployment Patterns: Batch, real-time, and streaming inference strategies.
  • Serving & Monitoring: Model serving configurations and drift/quality monitoring.
  • Governance: Model versioning and governance practices.

Quick Start

Deploy a simple model to a serving endpoint and monitor performance with baseline metrics.

Frequently Asked Questions about model-deployment

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

FAQPage Schema
How do I deploy ML models securely to production?

Secure model deployment integrates security linters, SAST/DAST tools, and dependency management into CI/CD pipelines to mitigate vulnerabilities across development workflows, serving infrastructure, and monitoring systems while maintaining compliance with security guidelines.

What are the best practices for model versioning and governance?

Model versioning establishes governance practices that track model lineage, enable reproducibility, and support rollback across batch, real-time, and streaming inference strategies, ensuring auditability and compliance in production ML systems.

How do I monitor ML models for drift and quality issues in production?

Model serving monitoring establishes baseline metrics and continuous quality checks to detect data drift and performance degradation, triggering incident response workflows to maintain reliability across production inference endpoints.

What deployment patterns work for different inference workloads?

Deployment patterns span batch processing for offline predictions, real-time serving for synchronous requests, and streaming inference for continuous data flows, each with distinct serving configurations and monitoring requirements.

Do I need separate infrastructure for different model serving strategies?

Model serving strategies share common governance and monitoring foundations but require different deployment configurations—batch systems use scheduled workflows, real-time endpoints use API serving infrastructure, and streaming uses event processing pipelines.