whylabs-monitor
WhyLabs integration skill for ML observability, profile logging, and anomaly detection.
Best use case
whylabs-monitor is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
WhyLabs integration skill for ML observability, profile logging, and anomaly detection.
Teams using whylabs-monitor should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/whylabs-monitor/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How whylabs-monitor Compares
| Feature / Agent | whylabs-monitor | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
WhyLabs integration skill for ML observability, profile logging, and anomaly detection.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# whylabs-monitor
## Overview
WhyLabs integration skill for ML observability, data profile logging, and anomaly detection in production ML systems.
## Capabilities
- Data profile generation (whylogs)
- Profile upload to WhyLabs platform
- Anomaly detection and alerts
- Segment analysis for data subsets
- Performance monitoring dashboards
- Integration with ML pipelines
- Historical profile comparison
- Custom constraint validation
## Target Processes
- Model Performance Monitoring and Drift Detection
- ML System Observability and Incident Response
## Tools and Libraries
- whylogs
- WhyLabs Platform
- pandas
## Input Schema
```json
{
"type": "object",
"required": ["action"],
"properties": {
"action": {
"type": "string",
"enum": ["profile", "upload", "compare", "validate", "alert-config"],
"description": "WhyLabs action to perform"
},
"profileConfig": {
"type": "object",
"properties": {
"dataPath": { "type": "string" },
"datasetId": { "type": "string" },
"segments": { "type": "array", "items": { "type": "string" } },
"timestamp": { "type": "string" }
}
},
"uploadConfig": {
"type": "object",
"properties": {
"orgId": { "type": "string" },
"modelId": { "type": "string" },
"profilePath": { "type": "string" }
}
},
"compareConfig": {
"type": "object",
"properties": {
"baselineProfile": { "type": "string" },
"targetProfile": { "type": "string" },
"metrics": { "type": "array", "items": { "type": "string" } }
}
},
"validationConfig": {
"type": "object",
"properties": {
"constraints": {
"type": "array",
"items": {
"type": "object",
"properties": {
"column": { "type": "string" },
"constraint": { "type": "string" },
"value": { "type": "number" }
}
}
}
}
}
}
}
```
## Output Schema
```json
{
"type": "object",
"required": ["status", "action"],
"properties": {
"status": {
"type": "string",
"enum": ["success", "error", "warning"]
},
"action": {
"type": "string"
},
"profilePath": {
"type": "string"
},
"uploadId": {
"type": "string"
},
"dashboardUrl": {
"type": "string"
},
"comparison": {
"type": "object",
"properties": {
"driftScore": { "type": "number" },
"driftedFeatures": { "type": "array", "items": { "type": "string" } },
"alerts": { "type": "array" }
}
},
"validation": {
"type": "object",
"properties": {
"passed": { "type": "boolean" },
"failures": { "type": "array" }
}
}
}
}
```
## Usage Example
```javascript
{
kind: 'skill',
title: 'Profile and upload production data',
skill: {
name: 'whylabs-monitor',
context: {
action: 'profile',
profileConfig: {
dataPath: 'data/production_batch.parquet',
datasetId: 'fraud-detection',
segments: ['region', 'customer_type'],
timestamp: '2024-01-15T00:00:00Z'
},
uploadConfig: {
orgId: 'org-123',
modelId: 'model-fraud-v2'
}
}
}
}
```Related Skills
vendor-risk-monitor
Continuous vendor security monitoring for security ratings, breach notifications, and risk change detection
early-warning-monitor
Continuous supplier and supply chain risk monitoring with automated alerts
media-monitoring
Deep integration with media monitoring platforms for coverage tracking, sentiment analysis, and reporting
debt-covenant-monitor
Automated covenant compliance monitoring and calculation skill with early warning alerts
power-management-monitor
Monitor system power state including battery, AC, sleep, and wake events
patrol-monitoring
Continuous monitoring using Deacon/Witness patterns for agent health checks, stuck detection, and automated recovery.
process-builder
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
babysitter
Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)
yolo
Run Babysitter autonomously with minimal manual interruption.
user-install
Install the user-level Babysitter Codex setup.
team-install
Install the team-pinned Babysitter Codex workspace setup.
retrospect
Summarize or retrospect on a completed Babysitter run.