一键导入
fmsr-sensor-failure-mapping
Retrieves sensors and failure modes for one explicit asset and maps which sensors can monitor or detect those failures.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Retrieves sensors and failure modes for one explicit asset and maps which sensors can monitor or detect those failures.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Gathers live sensors, failure modes, and maps their relevance for diagnostics and root-cause insights.
Verifies IoT observability and maintenance history, then applies a basic safety clearance check.
Retrieves known failure modes for one explicit asset type or asset name.
Lists available IoT sites and assets for a specified site.
Retrieves historical IoT observations for one explicit asset over an explicit time point or time window.
Retrieves monitored sensors or metrics for one explicit asset at one explicit IoT site.
| id | fmsr_sensor_failure_mapping |
| name | FMSR Sensor Failure Mapping |
| version | 1.0.0 |
| description | Retrieves sensors and failure modes for one explicit asset and maps which sensors can monitor or detect those failures. |
| required_servers | ["iot","fmsr"] |
| asset_types | ["chiller","ahu","equipment"] |
| keywords | ["failure mode","sensor mapping","detect","monitor","temporal behavior"] |
| default_enabled | true |
| inputs | {"site_name":{"type":"string","required":true},"asset_id":{"type":"string","required":true},"asset_name":{"type":"string","required":true}} |
| execution | {"type":"declarative"} |
Use this skill for simple questions that ask which sensors can monitor or detect failures, which failures can be detected by available sensors, or what sensor behavior is relevant to a named failure for one asset.
Do not use this skill for broad root-cause analysis, ML recipe generation, work-order decisions, or queries that require several independent filters. The FMSR mapping step may call an LLM for each failure-mode and sensor pair, so this skill should only be selected for focused mapping requests.
The final answer should state:
For Chiller scenarios, failure-mode names should come from the curated FMSR Chiller list.
{
"steps": [
{
"name": "iot_sensors",
"server": "iot",
"tool": "sensors",
"arguments": {
"site_name": "$site_name",
"asset_id": "$asset_id"
}
},
{
"name": "failure_modes",
"server": "fmsr",
"tool": "get_failure_modes",
"arguments": {
"asset_name": "$asset_name"
}
},
{
"name": "sensor_failure_mapping",
"server": "fmsr",
"tool": "get_failure_mode_sensor_mapping",
"arguments": {
"asset_name": "$asset_name",
"failure_modes": "$failure_modes.failure_modes",
"sensors": "$iot_sensors.sensors"
}
}
]
}