jeremylongshore/tons-of-skills-marketplace / plugins/ai-ml/model-explainability-tool/skills/explaining-machine-learning-models
explaining-machine-learning-models
VerifiedBuild this skill enables AI assistant to provide interpretability and explainability for machine learning models. it is triggered when the user requests explanations for model predictions, insights into feature importance, or help understanding model behavior... Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.1 KB |
| assets/README.md | markdown | 362 B |
| assets/example_explanation.json | config | 3.5 KB |
| assets/explanation_template.html | other | 3.8 KB |
| assets/visualization_styles.css | other | 2.5 KB |
| references/README.md | markdown | 68 B |
| scripts/README.md | markdown | 407 B |
assets/visualization_styles.css
View on GitHub/*
visualization_styles.css - CSS file for styling visualizations of feature importance and model predictions.
This file provides the styling for visualizations generated by the model-explainability-tool plugin.
It includes styles for feature importance charts, prediction breakdowns, and other interpretability
visualizations.
Feel free to customize these styles to match your application's design.
Table of Contents:
1. General Styles
2. Feature Importance Chart Styles
3. Prediction Breakdown Styles
4. [Add more sections as needed]
*/
/* 1. General Styles */
body {
font-family: sans-serif;
margin: 0;
padding: 0;
}
.visualization-container {
margin: 20px;
padding: 20px;
border: 1px solid #ccc;
border-radius: 5px;
}
.visualization-title {
font-size: 1.5em;
font-weight: bold;
margin-bottom: 10px;
}
.visualization-description {
font-size: 1em;
color: #555;
margin-bottom: 20px;
}
/* 2. Feature Importance Chart Styles */
.feature-importance-chart {
/* Styles for the chart container */
width: 100%;
height: 400px; /* Adjust as needed */
}
.feature-importance-bar {
/* Styles for individual bars in the chart */
background-color: #4CAF50; /* Green */
color: white;
padding: 5px;
margin-bottom: 2px;
text-align: right;
}
.feature-name {
/* Styles for feature names displayed in the chart */
float: left;
}
.feature-importance-value {
/* Styles for feature importance values */
float: right;
}
/* 3. Prediction Breakdown Styles */
.prediction-breakdown {
/* Styles for the overall prediction breakdown container */
}
.prediction-breakdown-item {
/* Styles for individual items in the breakdown */
margin-bottom: 5px;
}
.prediction-breakdown-label {
/* Styles for labels in the breakdown */
font-weight: bold;
}
.prediction-breakdown-value {
/* Styles for values in the breakdown */
color: #007bff; /* Blue */
}
/* 4. [Add more sections as needed. Example: Styles for specific model types] */
/* Example: Styles for tree-based models */
.tree-node {
/* Styles for nodes in a decision tree visualization */
border: 1px solid #ddd;
padding: 5px;
margin: 2px;
border-radius: 3px;
}
/* Placeholders for future customization */
/* Example: Add styles for different color palettes */
/* .color-palette-1 { ... } */
/* Add responsive styles for different screen sizes */
@media (max-width: 768px) {
.visualization-container {
margin: 10px;
padding: 10px;
}
.feature-importance-chart {
height: 300px; /* Adjust height for smaller screens */
}
}Related 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 | Unverified | 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: 322k | 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: 322k | 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: 322k | Updated | Claude CodeCodex | Verified | Install |