Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问许可证需确认审计通过

mfg-oee-analysis制造商 OEE 分析

Agent Skill

mfg-oee-analysis 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

367

周安装

15

GitHub Stars

125

下载量

119
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:mfg-oee-analysis(制造商 OEE 分析)
来源仓库:https://github.com/asgard-ai-platform/skills
仓库路径:skills/mfg-oee-analysis
安装命令:
npx skills add https://github.com/asgard-ai-platform/skills --skill mfg-oee-analysis
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/asgard-ai-platform/skills --skill mfg-oee-analysis

简介

mfg-oee-analysis 用于查找、检索和筛选相关信息。

  • 适合在 Codex、Claude、Cursor、Gemini CLI 中根据任务场景快速定位候选结果。
  • 通过 npx skills add 命令从指定仓库安装,需确认权限范围和维护状态。
  • 使用前建议核实是否会触发联网、命令执行或文件读写操作。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

OEE Analysis

Framework

IRON LAW: OEE = Availability × Performance × Quality

OEE is a MULTIPLICATIVE metric. 90% × 90% × 90% = 72.9%, not 90%.
Each factor compounds the loss. World-class OEE is 85%+. Most plants
operate at 60-65%. Knowing the TOTAL is useless — you must decompose
to find which factor is dragging performance down.

The Three Factors

FactorFormulaMeasuresLoss Categories
AvailabilityRun Time / Planned Production TimeUptime vs downtimeEquipment failures, changeovers, material shortages
Performance(Ideal Cycle Time × Total Count) / Run TimeActual speed vs design speedMinor stops, slow running, idling
QualityGood Count / Total CountYield, first-pass qualityDefects, rework, scrap, startup rejects

Six Big Losses (mapped to OEE factors)

LossOEE FactorExample
1. Equipment failureAvailabilityMachine breakdown, unplanned repair
2. Setup & changeoverAvailabilityProduct changeover, die change, cleaning
3. Idling & minor stopsPerformanceSensor blockage, jam clearing, small adjustments
4. Reduced speedPerformanceRunning below rated speed due to wear or material
5. Process defectsQualityIn-process rejects, rework
6. Startup rejectsQualityScrap during warm-up, first-article failures

Calculation Example

Planned Production Time: 480 min (8-hour shift)
Downtime (breakdowns + changeover): 60 min
Run Time: 420 min

Ideal Cycle Time: 1 min/unit
Total Units Produced: 380

Good Units: 360
Defective Units: 20

Availability = 420 / 480 = 87.5%
Performance = (1 × 380) / 420 = 90.5%
Quality = 360 / 380 = 94.7%

OEE = 87.5% × 90.5% × 94.7% = 75.0%

Diagnosis Steps

Phase 1: Calculate OEE for each production line/machine Phase 2: Identify the weakest factor (Availability, Performance, or Quality) Phase 3: Pareto the losses within that factor (which specific loss is biggest?) Phase 4: Root cause analysis on the top loss (5 Whys, fishbone) Phase 5: Improve and remeasure

Benchmarks

OEE LevelRatingTypical
> 85%World-classTop manufacturers
60-85%TypicalRoom for improvement
40-60%LowSignificant losses, urgent action needed
< 40%CriticalEquipment or process fundamentally broken

Output Format

# OEE Report: {Production Line}

## OEE Summary
| Factor | Value | Benchmark | Status |
|--------|-------|-----------|--------|
| Availability | {%} | >90% | 🟢/🟡/🔴 |
| Performance | {%} | >95% | 🟢/🟡/🔴 |
| Quality | {%} | >99% | 🟢/🟡/🔴 |
| **OEE** | **{%}** | **>85%** | 🟢/🟡/🔴 |

## Loss Breakdown
| Loss | Minutes Lost | % of Total Loss | Priority |
|------|-------------|----------------|---------|
| {loss type} | {min} | {%} | 1/2/3 |

## Root Cause (Top Loss)
{5 Whys or fishbone analysis}

## Improvement Plan
| Action | Target Impact | Timeline | Owner |
|--------|-------------|----------|-------|
| {action} | +{X%} OEE | {weeks} | {who} |

Gotchas

  • OEE is per machine, not per plant: Plant-level OEE averages hide that one machine at 95% and another at 45% average to 70%. Analyze individually.
  • Planned downtime is excluded: OEE measures losses against PLANNED production time. Scheduled maintenance, no-production shifts, and planned shutdowns are excluded from the denominator.
  • 100% OEE is not the goal: It would mean zero changeovers, zero defects, running at max speed 100% of the time. Pursuing 100% can increase costs (e.g., never doing preventive maintenance). Target 85%+ for critical lines.
  • Data collection is the real challenge: Manual OEE tracking is inaccurate. Invest in automated data collection (sensors, MES integration) for reliable measurement.

References

  • For TPM (Total Productive Maintenance) methodology, see references/tpm.md
  • For automated OEE data collection, see references/oee-automation.md

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

38.16%
按下载量换算45

Claude

27.24%
按下载量换算32

Cursor

18.99%
按下载量换算23

Gemini CLI

9.73%
按下载量换算12

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills