jeremylongshore/tons-of-skills-marketplace / plugins/ai-ml/model-versioning-tracker/skills/tracking-model-versions
tracking-model-versions
VerifiedBuild this skill enables AI assistant to track and manage ai/ml model versions using the model-versioning-tracker plugin. it should be used when the user asks to manage model versions, track model lineage, log model performance, or implement version control f... Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.2 KB |
| assets/README.md | markdown | 362 B |
| assets/example_mlflow_workflow.yaml | config | 3.3 KB |
| assets/model_card_template.md | markdown | 6.3 KB |
| assets/versioning-diagram-brief.md | markdown | 730 B |
| references/README.md | markdown | 67 B |
| scripts/README.md | markdown | 490 B |
| scripts/version_control.pyexecutable | script | 2.8 KB |
assets/example_mlflow_workflow.yaml
View on GitHub# This is an example MLflow workflow configuration file for the model-versioning-tracker plugin.
# It defines the stages of the MLflow workflow, the models to be tracked, and the metrics to be monitored.
# General configuration
workflow_name: "Example MLflow Workflow" # Name of the workflow
description: "An example workflow for tracking model versions and performance using MLflow." # Description of the workflow
environment: "production" # Environment (e.g., development, staging, production)
mlflow_tracking_uri: "http://localhost:5000" # MLflow tracking server URI (update if using a remote server)
artifact_location: "s3://mlflow-artifacts-prod/experiments" # Location to store artifacts (models, data, etc.) - update with your S3 bucket
# Model configuration
model:
name: "MyAwesomeModel" # Name of the model to track
model_uri: "models:/MyAwesomeModel/Production" # URI of the model in MLflow Model Registry
flavor: "sklearn" # Model flavor (e.g., sklearn, tensorflow, pytorch) - important for loading the model correctly
# Data configuration
data:
dataset_name: "iris" # Name of the dataset used for training
dataset_location: "data/iris.csv" # Location of the dataset (can be a local path or a cloud storage URI) - ADJUST PATH IF NEEDED
target_variable: "species" # Name of the target variable
features: ["sepal_length", "sepal_width", "petal_length", "petal_width"] # List of feature variables
# Training configuration
training:
experiment_name: "MyAwesomeModelTraining" # Name of the MLflow experiment
entrypoint: "train.py" # Python script to run for training (relative to the plugin directory)
parameters: # Training parameters
learning_rate: 0.01
epochs: 100
random_state: 42
environment: "conda.yaml" # Conda environment file for training (optional)
# Evaluation configuration
evaluation:
entrypoint: "evaluate.py" # Python script to run for evaluation (relative to the plugin directory)
metrics: # Metrics to track during evaluation
accuracy:
threshold: 0.8 # Minimum acceptable accuracy (optional)
f1_score:
threshold: 0.7 # Minimum acceptable F1 score (optional)
validation_dataset: "data/validation.csv" # Location of the validation dataset (optional) - ADJUST PATH IF NEEDED
# Deployment configuration
deployment:
target_platform: "AWS SageMaker" # Target platform for deployment (e.g., AWS SageMaker, Azure ML, GCP Vertex AI)
deployment_script: "deploy.py" # Python script to run for deployment (relative to the plugin directory)
model_endpoint: "https://runtime.sagemaker.us-east-1.amazonaws.com/endpoints/my-model-endpoint" # Endpoint where the model will be deployed
instance_type: "ml.m5.large" # Instance type for deployment (e.g., ml.m5.large)
# Versioning configuration
versioning:
model_registry_name: "MyAwesomeModelRegistry" # Name of the model registry in MLflow (optional)
transition_stage: "Production" # Stage to transition the model to after successful evaluation (e.g., Staging, Production)
description: "Initial model version" # Description for the model version
# Alerting configuration
alerting:
email_notifications: # Email notifications configuration
enabled: false # Enable/disable email notifications
recipients: ["ml-ops-team@example.com"] # List of email recipients for alerts
on_failure: true # Send email on workflow failure
on_success: false # Send email on workflow successRelated skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |