帮助团队搭建可复现、可部署、可监控的生产级机器学习工程流程
该技能材料显示其为纯提示词型的机器学习工程工作流说明,不要求密钥、未声明远程端点,也未体现本地执行或数据外发能力。结合 GitHub 开源和较高社区采用度,整体风险较低,主要仅需常规关注来源维护与仓库内容是否持续可审计。
材料明确标注“需要的密钥/环境变量:无”,README 也未见要求 API key、云凭证或令牌的说明;未发现凭证收集、存储或滥用迹象。
系统检查项显示无远程端点,材料中也未声明向外部服务发送数据的机制;作为 prompt-only 技能,未见用户数据外发到第三方的事实依据。
该对象被判定为 prompt-only,当前材料仅描述工作流方法论与适用场景,未体现本机起进程、执行脚本、调用系统命令或申请额外执行权限。
README 讨论的是生产 ML 流程设计,并未声明可读取或写入本地文件、仓库、数据库或其他用户资源;未见超出文档/提示词范围的数据访问能力。
来源为 GitHub 开源仓库,且社区采用度很高(约 210.5k stars),这些都是显著的降风险因素;虽许可证未声明、维护状态未知,仍未见闭源外发、来源可疑或明显注入等高风险红旗。
复制安装指令,让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "mle-workflow" 技能: 1. 下载 https://raw.githubusercontent.com/affaan-m/ECC/main/skills/mle-workflow/SKILL.md 2. 保存为 ~/.claude/skills/mle-workflow/SKILL.md 3. 装好后重载技能,告诉我可以用了
请为一个用于用户流失预测的机器学习系统设计生产级工程流程,覆盖数据契约、特征处理、可复现训练、模型评估、部署、监控与回滚策略,并给出各阶段的责任分工与关键检查点。
一份结构化的ML工程流程方案,说明阶段、职责、质量门禁与上线保障措施。
请审查我们当前的模型上线流程:数据来自多个表,训练靠手动脚本,评估只看AUC,没有漂移监控,也缺少回滚预案。请指出风险,并给出生产化改进建议和优先级路线图。
一份流程审查报告,包含主要风险、缺口分析和按优先级排序的改进建议。
请为一个已部署的推荐模型制定监控与回滚方案,包含输入数据质量、特征漂移、预测分布、线上效果指标、告警阈值、触发条件,以及自动回滚和人工介入流程。
一套可执行的监控与回滚机制,便于运维和算法团队稳定维护线上模型。
Use this skill to turn model work into a production ML system with clear data contracts, repeatable training, measurable quality gates, deployable artifacts, and operational monitoring.
Use only the lanes that fit the system in front of you. This skill is useful for ranking, search, recommendations, classifiers, forecasting, embeddings, LLM workflows, anomaly detection, and batch analytics, but it should not force one architecture onto all of them.
python-patterns and python-testing for Python implementation and pytest coveragepytorch-patterns for deep learning models, data loaders, device handling, and training loopseval-harness and ai-regression-testing for promotion gates and agent-assisted regression checksdatabase-migrations, postgres-patterns, and clickhouse-io for data storage and analytics surfacesdeployment-patterns, docker-patterns, and security-review for serving, secrets, containers, and production hardeningDo not treat MLE as separate from software engineering. Most ECC SWE workflows apply directly to ML systems, often with stricter failure modes:
The recommended minimal --with capability:machine-learning install keeps the core agent surface available alongside this skill. For skill-only or agent-limited harnesses, pair skill:mle-workflow with agent:mle-reviewer where the target supports agents.
| SWE surface | MLE use |
|---|---|
product-capability / architecture-decision-records | Turn model work into explicit product contracts and record irreversible data, model, and rollout choices |
repo-scan / codebase-onboarding / code-tour | Find existing training, feature, serving, eval, and monitoring paths before introducing a parallel ML stack |
plan / feature-dev | Scope model changes as product capabilities with data, eval, serving, and rollback phases |
tdd-workflow / python-testing | Test feature transforms, split logic, metric calculations, artifact loading, and inference schemas before implementation |
code-reviewer / mle-reviewer | Review code quality plus ML-specific leakage, reproducibility, promotion, and monitoring risks |
build-fix / pr-test-analyzer | Diagnose broken CI, flaky evals, missing fixtures, and environment-specific model or dependency failures |
quality-gate / test-coverage | Require automated evidence for transforms, metrics, inference contracts, promotion gates, and rollback behavior |
eval-harness / verification-loop | Turn offline metrics, slice checks, latency budgets, and rollback drills into repeatable gates |
…
为 Quarkus 项目执行发布前验证闭环,涵盖构建、测试、扫描与差异审查。
将多个 MCP 工具编排为带条件逻辑的数据处理自动化工作流。