{"id":"a5b037fc-b4fc-444b-958b-ab5a3ee40ee0","entityType":"agent","slug":"clawhub-zw008-iaiops-process","name":"iaiops-process","canonicalUrl":"https://www.xpersona.co/agent/clawhub-zw008-iaiops-process","canonicalPath":"/agent/clawhub-zw008-iaiops-process","generatedAt":"2026-10-10T07:40:37.684Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-10T03:01:54.687Z","emptyReason":null},"description":"Process-industry edition of iaiops — chemical / pharma / food & beverage / oil & gas plants: HART-IP process instrumentation (transmitters, valve positioners, loop current), OPC-UA (DCS / gateway read), Modbus-TCP/RTU (skids, analyzers), optional MQTT/Sparkplug B UNS, plus the cross-protocol brain (downtime root-cause, data quality, OEE). Use when the task mentions HART, HART-IP, transmitter, 变送器, valve positioner, process instrumentation, PV/SV/TV/QV, loop current, burst mode, DCS tap, or a process plant. Read-first, MOC-gated writes. Skill: iaiops-process Owner: zw008 Summary: Process-industry edition of iaiops — chemical / pharma / food & beverage / oil & gas plants: HART-IP process instrumentation (transmitters, valve positioners, loop current), OPC-UA (DCS / gateway read), Modbus-TCP/RTU (skids, analyzers), optional MQTT/Sparkplug B UNS, plus the cross-protocol brain (downtime root-cause, data quality, OEE). Use when the task mentions HART, HA","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1.8K downloads reported by the source. Last updated 10/10/2026.","installCommand":"clawhub skill install s171xgnmqse0nqvgqvqnaq5f9183kyre:iaiops-process","sourceUrl":"https://clawhub.ai/zw008/iaiops-process","homepage":"https://clawhub.ai/zw008/skills/iaiops-process","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/zw008/iaiops-process","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/zw008/skills/iaiops-process","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":65,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Process-industry edition of iaiops — chemical / pharma / food & beverage / oil & gas plants: HART-IP process instrumentation (transmitters, valve positioners, l"},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-10T03:01:54.687Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-10T03:01:54.687Z","emptyReason":null},"stars":null,"forks":null,"downloads":1750,"packageName":null,"latestVersion":"0.28.0","tractionLabel":"1.8K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-10T03:01:54.687Z","emptyReason":null},"lastUpdatedAt":"2026-10-10T03:01:54.687Z","lastCrawledAt":"2026-10-10T03:01:54.687Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-11T03:01:54.687Z","lastVerifiedAt":null,"highlights":[{"version":"0.28.0","createdAt":"2026-09-16T05:09:12.230Z","changelog":"0.28.0: MQTT/Sparkplug collectable; onboard's two journeys (devices / uns with a B1/B2 namespace fork)","fileCount":3,"zipByteSize":7841},{"version":"0.27.0","createdAt":"2026-09-03T03:20:26.681Z","changelog":"router now routes to the pharma edition · contextual baselines · downtime attribution (D18) · alarm event-type clustering · device advisory matching · GxP crosswalk","fileCount":3,"zipByteSize":7604},{"version":"0.26.0","createdAt":"2026-09-01T12:29:23.481Z","changelog":"verify determinism (executed model-free claim) · PLC program change baseline · pharma edition","fileCount":3,"zipByteSize":6267},{"version":"0.23.1","createdAt":"2026-08-28T05:19:12.960Z","changelog":"iaiops-process 0.23.1 - Expanded documentation in SKILL.md to include: - New meta tools: `site_readiness`, `investigation_readiness`, `investigation_open`, `investigation_show`, `investigation_list` - Production line relationship and mechanism library tools: `line_relation_declare`, `line_relations_list`, `mechanism_library_check`, `mechanism_library_list` - SKILL.md now details the investigation workflow and explains new evidence chain concepts. - Removed skill-card.md from the package.","fileCount":3,"zipByteSize":5569},{"version":"0.23.0","createdAt":"2026-08-25T04:32:15.818Z","changelog":"- Removed redundant skill-card.md file for maintenance. - Updated SKILL.md documentation. - Added mention of uns_publish to the list of \"跨协议脑\" tools.","fileCount":3,"zipByteSize":5070},{"version":"0.22.0","createdAt":"2026-08-02T13:09:27.731Z","changelog":"0.22.0 — asyncua 2.x floor; OPC-UA vs a third-party stack + cert trust; TDengine REST/WS; second MCP implementation; EtherNet/IP program scope","fileCount":3,"zipByteSize":5203},{"version":"0.21.1","createdAt":"2026-08-02T07:25:01.842Z","changelog":"0.21.1 — review round two: RCA window dilution, IoTDB header names, OPC-UA malformed-URL leak","fileCount":3,"zipByteSize":5227},{"version":"0.21.0","createdAt":"2026-08-02T03:07:41.401Z","changelog":"0.21.0 — verification sweep: 5 product fixes (IoTDB tag mislabelling, TDengine coverage, OPC-UA thread leak + interop verdict, PROFINET doc fields)","fileCount":3,"zipByteSize":4975}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s171xgnmqse0nqvgqvqnaq5f9183kyre:iaiops-process","setupComplexity":"low","setupSteps":["Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-zw008-iaiops-process/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-zw008-iaiops-process/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-zw008-iaiops-process/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-zw008-iaiops-process/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-zw008-iaiops-process/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-zw008-iaiops-process/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-10T07:40:37.681Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-zw008-iaiops-process/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-zw008-iaiops-process/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-zw008-iaiops-process/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-zw008-iaiops-process/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-10T03:01:54.687Z","emptyReason":null},"readme":"Skill: iaiops-process\n\nOwner: zw008\n\nSummary: Process-industry edition of iaiops — chemical / pharma / food & beverage / oil & gas plants: HART-IP process instrumentation (transmitters, valve positioners, loop current), OPC-UA (DCS / gateway read), Modbus-TCP/RTU (skids, analyzers), optional MQTT/Sparkplug B UNS, plus the cross-protocol brain (downtime root-cause, data quality, OEE). Use when the task mentions HART, HART-IP, transmitter, 变送器, valve positioner, process instrumentation, PV/SV/TV/QV, loop current, burst mode, DCS tap, or a process plant. Read-first, MOC-gated writes.\n\nTags: latest:0.28.0\n\nVersion history:\n\nv0.28.0 | 2026-09-16T05:09:12.230Z | user\n\n0.28.0: MQTT/Sparkplug collectable; onboard's two journeys (devices / uns with a B1/B2 namespace fork)\n\nv0.27.0 | 2026-09-03T03:20:26.681Z | user\n\nrouter now routes to the pharma edition · contextual baselines · downtime attribution (D18) · alarm event-type clustering · device advisory matching · GxP crosswalk\n\nv0.26.0 | 2026-09-01T12:29:23.481Z | user\n\nverify determinism (executed model-free claim) · PLC program change baseline · pharma edition\n\nv0.23.1 | 2026-08-28T05:19:12.960Z | auto\n\niaiops-process 0.23.1\n\n- Expanded documentation in SKILL.md to include:\n - New meta tools: `site_readiness`, `investigation_readiness`, `investigation_open`, `investigation_show`, `investigation_list`\n - Production line relationship and mechanism library tools: `line_relation_declare`, `line_relations_list`, `mechanism_library_check`, `mechanism_library_list`\n- SKILL.md now details the investigation workflow and explains new evidence chain concepts.\n- Removed skill-card.md from the package.\n\nv0.23.0 | 2026-08-25T04:32:15.818Z | auto\n\n- Removed redundant skill-card.md file for maintenance.\n- Updated SKILL.md documentation.\n- Added mention of uns_publish to the list of \"跨协议脑\" tools.\n\nv0.22.0 | 2026-08-02T13:09:27.731Z | user\n\n0.22.0 — asyncua 2.x floor; OPC-UA vs a third-party stack + cert trust; TDengine REST/WS; second MCP implementation; EtherNet/IP program scope\n\nv0.21.1 | 2026-08-02T07:25:01.842Z | user\n\n0.21.1 — review round two: RCA window dilution, IoTDB header names, OPC-UA malformed-URL leak\n\nv0.21.0 | 2026-08-02T03:07:41.401Z | user\n\n0.21.0 — verification sweep: 5 product fixes (IoTDB tag mislabelling, TDengine coverage, OPC-UA thread leak + interop verdict, PROFINET doc fields)\n\nv0.20.4 | 2026-08-02T00:28:56.822Z | user\n\nNATS egress 120s hang bounded to 5s; BACnet write now reports a read-back instead of claiming applied; MCP interface + egress sinks now driven by real counterparties\n\nv0.20.3 | 2026-08-01T04:32:39.937Z | user\n\naudit status now reflects real outcome; runaway guard sees retried denials; approval-gate contract over the real write surface\n\nv0.20.2 | 2026-07-31T14:46:30.805Z | user\n\ncredential redaction in audit log; retained mqtt_publish undo; pyopenssl resolver guard\n\nv0.20.1 | 2026-07-29T09:38:00.595Z | user\n\niaiops 0.20.1 — MCP tool annotations derived from the governance harness\n\nv0.19.0 | 2026-07-21T14:37:05.372Z | user\n\n0.19.0 — read-only gate removed; audit on both MCP+CLI; effect-based write risk\n\nv0.18.1 | 2026-07-19T17:13:49.522Z | auto\n\n- Removed the file skill-card.md.\n- No functional changes to the skill or documentation content.\n- No new features or bugfixes introduced.\n\nv0.18.0 | 2026-07-19T11:30:26.979Z | auto\n\n- Removed the skill-card.md file.\n- No other changes to functionality or features.\n\nv0.17.0 | 2026-07-19T09:22:42.550Z | auto\n\n- Added `hart_burst_listen` tool for passive listening to HART burst publish (pending gateway verification).\n- Expanded OPC-UA support: added `opcua_alarm_events` for A&C event readout with timestamps.\n- Introduced `rca_corpus_from_maintenance` to the diagnostics toolset.\n- Changed documentation: clarified version matrix as internal only; removed sample `skill-card.md`.\n\nv0.12.0 | 2026-07-13T01:08:47.929Z | user\n\niaiops 0.12.0 edition — aligns ClawHub with the current per-industry edition architecture\n\nArchive index:\n\nArchive v0.28.0: 3 files, 7841 bytes\n\nFiles: skill-card.md (2417b), SKILL.md (10985b), _meta.json (134b)\n\nFile v0.28.0:SKILL.md\n\n---\nname: iaiops-process\ndescription: >-\n Process-industry edition of iaiops — chemical / pharma / food & beverage / oil &\n gas plants: HART-IP process instrumentation (transmitters, valve positioners,\n loop current), OPC-UA (DCS / gateway read), Modbus-TCP/RTU (skids, analyzers),\n optional MQTT/Sparkplug B UNS, plus the cross-protocol brain (downtime\n root-cause, data quality, OEE). Use when the task mentions HART, HART-IP,\n transmitter, 变送器, valve positioner, process instrumentation, PV/SV/TV/QV,\n loop current, burst mode, DCS tap, or a process plant. Read-first, MOC-gated\n writes.\n---\n\n# iaiops-process — 流程工业 edition（HART + Modbus + OPC-UA + 脑）\n\n启动：`IAIOPS_MCP=process` / `iaiops-mcp-process`（= opcua + modbus + hart + 脑）。\n现场有 UNS/Sparkplug 时用 `IAIOPS_MCP=process,sparkplug`（sparkplug 工具清单见\n**iaiops-factory** skill）。HART 需 extra：`pip install iaiops[hart]`。\n\n## 工具\n\n### HART-IP（只读；过程仪表 — 变送器、阀门定位器，经网关）\n`transport` 为 `udp`（默认）或 `tcp`，端口 5094。\n- `hart_device_identity` — 通用设备身份（command 0）\n- `hart_primary_variable` — 主变量 PV（command 1）：值 + 单位码\n- `hart_dynamic_variables` — 动态变量 PV/SV/TV/QV + 回路电流（command 3）\n- `hart_burst_sample` — 主动采样 burst 发布的变量；`hart_burst_listen` — 被动监听非请求 burst publish（待核实 per 网关）\n\n### OPC-UA（只读；DCS/网关旁路读取）\n- `opcua_server_info` / `opcua_browse` / `opcua_read_node` / `opcua_read_many`\n- `opcua_subscribe_sample` `opcua_read_alarms` `opcua_alarm_events`(A&C 带时间戳) `opcua_read_history`(HDA)\n- `opcua_diagnose_connection` — 连接失败归因（证书/策略/认证/网络/配置）\n- `opcua_discover_tags` — 自动发现 + 语义资产建模\n- `opcua_health_summary` — tag vs 阈值分类；`opcua_anomaly_scan` — 有界统计异常扫描\n\n### Modbus-TCP / Modbus-RTU（只读；撬装/分析仪/RTU 从站）\n- `modbus_read_holding` `modbus_read_input` `modbus_read_coils` `modbus_read_discrete`\n- `modbus_detect_byte_order` — 字节/字序自动探测\n- `modbus_list_templates` / `modbus_apply_template` — 厂商寄存器模板 → 命名 tag\n- `modbus_health_summary` — 寄存器 vs 阈值分类\n\n### 流程专属（edition 工具;仅随 process edition 加载,不进全局脑）\n- `control_loop_health` — PID 回路诊断:从一段 PV/SP/OP 采样检出**振荡**(PV 反复穿越 SP)、\n **稳态偏差**(PV 长期偏离 SP)、**输出饱和**(OP 压在 0/100%)。给 verdict(saturated>oscillating>\n offset>ok)。非整定器,只分诊哪些回路要看。纯分析,每项引用数值。\n- `heat_exchanger_fouling` — **换热器结垢检测**:按四路温度算热侧温度效能 ε=(hot_in−hot_out)/\n (hot_in−cold_in),前后半窗对比;效能低于阈值或下降超阈即 fouling(结垢征兆,先于强制清洗)。\n 纯分析,喂 OPC-UA/Modbus/HART 温度点,verdict 引用效能数值。\n\n### 跨协议脑（永远随 server 暴露）\n- 诊断：`diagnose_dataflow` `downtime_root_cause` `downtime_root_cause_live` `downtime_triage`\n `learn_cause_weights` `rca_corpus_from_maintenance` `historian_health` `alarm_bad_actors` `tag_health`\n `subscription_health` `heartbeat_health` `alarm_flood_analysis` `alarm_cascade`\n `alarm_rationalization_worksheet`\n- 告警事件聚类：`alarm_event_clusters` — `alarm_bad_actors` 按**来源**排名,回答的是「哪台仪表最吵」,\n 不是「哪个故障最吵」;一个把同一条件写成十种说法的厂会得到十个 bad actor。这个按事件**说了什么**分组。\n 合并规则是**去掉大小写/标点/数字后的精确相等,不是相似度** —— 故意做笨,所以不需要模型、且可核对;\n 每个簇都列出被合并的原文与来源。**它不主张两条措辞不同的告警是同一个故障**,那由人判断。\n- 数据质量：`data_quality_scorecard` `data_quality_fleet_rollup`（流程工业重点：\n staleness / flatline / bad-quality —— 仪表坏数据绝不静默插值喂 AI）\n- 分析：`oee_compute` `downtime_events` `oee_multidim` `monitor_changes`\n `health_summary` (deprecated) `anomaly_scan` (deprecated)\n- 上下文基线：`baseline_learn_contextual` `baseline_check_in_context` —— 一个位号只学一条带,\n 在它有不止一个「正常」时就是错的(同一台干燥机 recipe A 走 180 °C、B 走 240 °C,一条带横跨两者,\n 于是两个工况都不可能出错)。**上下文由人声明,绝不推断**(D16);某个上下文历史太薄就**拒学**,\n 不借用别的上下文的样本;读数落在没学过的上下文里报 `unknown_context`,**绝不回落到全局带** ——\n 回落等于把「这个工况从没见过」说成「这个工况正常」。\n- 上下游归因：`downtime_attribution` —— RCA 只按**时间**加权,所以一次上游停机会让每台下游设备\n 各自给出一个自信的本地根因。方向来自**声明的**产线顺序(D25:产线上共现是必然,拿它挖边等于\n 制造因果),顺序来自时间戳,**两者都要成立**;没声明关系就报 `not_evaluable` 并给出补法。\n- 资产：`asset_inventory` `cross_protocol_asset_model` `adopt_alias_map` `diff_alias_map`\n- 设备公告对照：`device_advisory_check` —— `scan` 早就在读 vendor/model/firmware,却什么都没做。\n 这条把它接上,并**刻意停在漏洞扫描器会继续往前走的地方**:只报「落在公告声明的版本范围内」,\n **不说「可利用」、不给严重度** —— 可达性与补偿控制决定那件事,而只读扫描看不见它们。\n **不内置任何 CVE 库**(过期却看着像最新的库比没有更糟),由现场挂载文件、离线可用,每条必须带来源。\n 读不出固件报 `version_unknown`,读得出但排不了序报 `version_unparsed` —— 都不算通过;\n 公告没提到的设备**不出现在结果里**,那是「未知」不是「没有」。\n- 基线：`baseline_learn` `baseline_check` `baseline_record_change` `baseline_status`\n （change-log 基线：拒学薄历史、只报持续越带、每次告警必引基线样本 —— 非黑盒异常检测）\n- 合规/信创：`compliance_mapping` `compliance_frameworks` `compliance_dengbao_levels`\n `compliance_report` `compliance_evidence_bundle`\n `historian_push` `export_data` `historian_query` `historian_coverage` `stream_publish` `uns_publish` `stream_publish_event` `rca_narrate` `fleet_status` `fleet_incidents` `pdm_forecast`\n `historian_push` `export_data`\n- 程序解读：`plc_program_outline` `plc_program_xref` `plc_program_section` `plc_program_visibility`（解读导出的 ST/AWL/L5X 程序,只读文件,强制引用行号）\n- 程序变更基线：`plc_program_snapshot` `plc_program_drift` `plc_program_history` — 把「认可的那一版」\n 的结构记下来（文件 SHA-256 + 每个 block 的结构指纹：声明/调用/分支条件/定时器，**不含行号、注释、\n block 顺序**，所以在文件顶上加一行注释不会把整份程序报成变更），之后问某一次导出**动没动**。\n 三个判词咬得很紧：`identical` **只**由 SHA-256 相同得出；`logic_changed` 逐 block 指出哪一类变了；\n `changed_outside_extracted_structure` = 字节变了而结构指纹全同 —— 多半是注释/排版，但这些 parser\n 是结构抽取不是文法，**所以它不叫「仅文档」，也不构成放行**。删历史只在 CLI（`iaiops program forget`）：\n 删变更控制证据不该离 agent 只有一次调用。存的是 block 名 + 哈希 + 计数，**不落声明、源码行和注释**。\n- 自证：`verify_determinism` — 把「拿掉模型、断网、同一份数据重跑、输出逐字节相同」**跑出来**：\n 固定数据集过一遍分析层，规范化后取 SHA-256，在本进程跑两遍、再在两个不同 PYTHONHASHSEED 的\n 全新解释器里各跑一遍（这一臂才抓得到集合/字典迭代顺序渗进结果），全程 socket 抛异常。\n 给 CSV/验证团队的是一条能写进 IQ/OQ 的测试用例，不是一句形容词。\n- 元：`protocols_supported`(产品能做什么)· `site_readiness`(这个站点今天能跑什么、还差什么;零联网)\n · `onboarding_status`(先判定路线：设备直读 / 已在 UNS broker，UNS 再按已存体检分 B1/B2；再给这条路上的下一步;零联网)\n · `onboarding_config_draft`(把已存的 scan 变成 config.yaml 端点草稿 —— **只写连接事实**：\n `value: null` 的字段是扫描没确认的，照抄它的 `caution`，别替人填也别删；`tags` 永远是空的，\n 点位语义只能人来确认 `iaiops tags export|apply`)\n- 调查层（§13，八步证据闭环）：`investigation_readiness` `investigation_open` `investigation_show`\n `investigation_list` — 「真出事时这个站能走到第几步、每个缺口还差什么」，以及对一个**已过去的窗口**\n 逐步走完并留档（不碰设备）。缺口分两种:**你没供**(给命令) 与 **产品供不了**。\n- 产线关系与机制库：`line_relation_declare` `line_relations_list` `mechanism_library_check`\n `mechanism_library_list` — 上下游由**人声明**（D25:线上下游共现是必然，推不出因果）；\n 机制库按 ISO 14224 分 mode/mechanism/cause，**可排除、绝不确认**，\n 库里没有这条原因 → `nothing_known`（不是「无异议」）。\n\n\n## Workflows\n\n1. **Doctor-first**：`protocols_supported` → `iaiops doctor` → HART 先\n `hart_device_identity` 证明网关链路，OPC-UA 先 `opcua_diagnose_connection`。\n2. **Read-first**：仪表读 PV（`hart_primary_variable`）→ 动态变量 → burst；\n 回路异常/告警风暴用 `alarm_bad_actors`（ISA-18.2），\"没数据\"用 `diagnose_dataflow`。\n3. **MOC 写**：本 edition 三个协议的工具全部只读（无写表面）。若叠加 sparkplug，\n `mqtt_publish` 为 **[WRITE][HIGH][MOC]**：默认 `dry_run=True` + 改前状态 undo +\n `iaiops approve` 具名审批双确认。未经授权绝不写生产控制系统。\n\n## 支持版本矩阵（内部 HLD §8，设计文档不随本仓发布；`待核实` 不得当既成事实）\n\n| 协议 | 库(pin) | 规范/版本 | 覆盖 | 传输 | 自测 |\n|---|---|---|---|---|---|\n| HART-IP | `hart-protocol>=2023.6,<2025`（extra） | HART-IP（经网关） | 过程仪表：变送器/阀门定位器 | UDP/TCP 5094 | ⚠️ codec CI 自测；真机网关 待核实 |\n| OPC-UA | `asyncua>=2.0,<3` | OPC UA 1.0x（DA+HA+AC 子集） | 任意合规 Server / DCS 网关 | opc.tcp | ✅ mock+HDA |\n| Modbus-TCP | `pymodbus>=3.5,<4` | App 1.1b3；FC 1/2/3/4/5/6/15/16 | 任意 TCP 从站 | TCP/502 | ✅ |\n| Modbus-RTU | `pymodbus>=3.5,<4` + `pyserial>=3.5` | Modbus serial (RTU) | 串口从站 | RS-485/serial | ✅ socat PTY verified 2026-07-02；物理 RS-485 待核实 |\n\nFile v0.28.0:_meta.json\n\n{\n \"ownerId\": \"kn7b067awq2s97bn3d7p5qfhw5827pxc\",\n \"slug\": \"iaiops-process\",\n \"version\": \"0.28.0\",\n \"publishedAt\": 1789535352230\n}\n\nFile v0.28.0:skill-card.md\n\n## Description:\n\nProcess-industry edition of iaiops for chemical, pharma, food and beverage, and oil and gas plants, helping agents read HART-IP, OPC-UA, Modbus, and optional MQTT/Sparkplug B UNS signals for process instrumentation, downtime root-cause analysis, data quality, and OEE with a read-first, MOC-gated posture.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[zw008](https://clawhub.ai/user/zw008)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and process engineers use this skill to guide agents through process plant data collection and analysis across HART-IP, OPC-UA, Modbus, and optional UNS/Sparkplug workflows. It supports loop health, heat exchanger fouling checks, alarm and data quality analysis, OEE, downtime triage, asset modeling, investigation workflows, and configuration drafting.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: High-impact historian, export, stream publish, or UNS publish operations may affect operational data if enabled without clear approval gates.\n\nMitigation: Confirm the enabled toolset and require explicit human approval before any operation that exports, publishes, or writes operational data.\n\nRisk: Production plant installation may carry elevated operational risk because the scanner classified the release as suspicious.\n\nMitigation: Review the skill before production use and install dependencies only in a contained environment with pinned, verified packages.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/zw008/skills/iaiops-process)\n- [Publisher profile](https://clawhub.ai/user/zw008)\n\n## Skill Output:\n\n**Output Type(s):** [Guidance, Shell commands, Configuration, Markdown, Code]\n\n**Output Format:** [Markdown guidance with tool names, command snippets, configuration drafts, and structured analysis summaries]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May propose historian, export, stream publish, or UNS publish operations; production-impacting actions require review and explicit approval gates.]\n\n## Skill Version(s):\n\n0.28.0 (source: server release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v0.27.0: 3 files, 7604 bytes\n\nFiles: skill-card.md (2395b), SKILL.md (10528b), _meta.json (134b)\n\nFile v0.27.0:SKILL.md\n\n---\nname: iaiops-process\ndescription: >-\n Process-industry edition of iaiops — chemical / pharma / food & beverage / oil &\n gas plants: HART-IP process instrumentation (transmitters, valve positioners,\n loop current), OPC-UA (DCS / gateway read), Modbus-TCP/RTU (skids, analyzers),\n optional MQTT/Sparkplug B UNS, plus the cross-protocol brain (downtime\n root-cause, data quality, OEE). Use when the task mentions HART, HART-IP,\n transmitter, 变送器, valve positioner, process instrumentation, PV/SV/TV/QV,\n loop current, burst mode, DCS tap, or a process plant. Read-first, MOC-gated\n writes.\n---\n\n# iaiops-process — 流程工业 edition（HART + Modbus + OPC-UA + 脑）\n\n启动：`IAIOPS_MCP=process` / `iaiops-mcp-process`（= opcua + modbus + hart + 脑）。\n现场有 UNS/Sparkplug 时用 `IAIOPS_MCP=process,sparkplug`（sparkplug 工具清单见\n**iaiops-factory** skill）。HART 需 extra：`pip install iaiops[hart]`。\n\n## 工具\n\n### HART-IP（只读；过程仪表 — 变送器、阀门定位器，经网关）\n`transport` 为 `udp`（默认）或 `tcp`，端口 5094。\n- `hart_device_identity` — 通用设备身份（command 0）\n- `hart_primary_variable` — 主变量 PV（command 1）：值 + 单位码\n- `hart_dynamic_variables` — 动态变量 PV/SV/TV/QV + 回路电流（command 3）\n- `hart_burst_sample` — 主动采样 burst 发布的变量；`hart_burst_listen` — 被动监听非请求 burst publish（待核实 per 网关）\n\n### OPC-UA（只读；DCS/网关旁路读取）\n- `opcua_server_info` / `opcua_browse` / `opcua_read_node` / `opcua_read_many`\n- `opcua_subscribe_sample` `opcua_read_alarms` `opcua_alarm_events`(A&C 带时间戳) `opcua_read_history`(HDA)\n- `opcua_diagnose_connection` — 连接失败归因（证书/策略/认证/网络/配置）\n- `opcua_discover_tags` — 自动发现 + 语义资产建模\n- `opcua_health_summary` — tag vs 阈值分类；`opcua_anomaly_scan` — 有界统计异常扫描\n\n### Modbus-TCP / Modbus-RTU（只读；撬装/分析仪/RTU 从站）\n- `modbus_read_holding` `modbus_read_input` `modbus_read_coils` `modbus_read_discrete`\n- `modbus_detect_byte_order` — 字节/字序自动探测\n- `modbus_list_templates` / `modbus_apply_template` — 厂商寄存器模板 → 命名 tag\n- `modbus_health_summary` — 寄存器 vs 阈值分类\n\n### 流程专属（edition 工具;仅随 process edition 加载,不进全局脑）\n- `control_loop_health` — PID 回路诊断:从一段 PV/SP/OP 采样检出**振荡**(PV 反复穿越 SP)、\n **稳态偏差**(PV 长期偏离 SP)、**输出饱和**(OP 压在 0/100%)。给 verdict(saturated>oscillating>\n offset>ok)。非整定器,只分诊哪些回路要看。纯分析,每项引用数值。\n- `heat_exchanger_fouling` — **换热器结垢检测**:按四路温度算热侧温度效能 ε=(hot_in−hot_out)/\n (hot_in−cold_in),前后半窗对比;效能低于阈值或下降超阈即 fouling(结垢征兆,先于强制清洗)。\n 纯分析,喂 OPC-UA/Modbus/HART 温度点,verdict 引用效能数值。\n\n### 跨协议脑（永远随 server 暴露）\n- 诊断：`diagnose_dataflow` `downtime_root_cause` `downtime_root_cause_live` `downtime_triage`\n `learn_cause_weights` `rca_corpus_from_maintenance` `historian_health` `alarm_bad_actors` `tag_health`\n `subscription_health` `heartbeat_health` `alarm_flood_analysis` `alarm_cascade`\n `alarm_rationalization_worksheet`\n- 告警事件聚类：`alarm_event_clusters` — `alarm_bad_actors` 按**来源**排名,回答的是「哪台仪表最吵」,\n 不是「哪个故障最吵」;一个把同一条件写成十种说法的厂会得到十个 bad actor。这个按事件**说了什么**分组。\n 合并规则是**去掉大小写/标点/数字后的精确相等,不是相似度** —— 故意做笨,所以不需要模型、且可核对;\n 每个簇都列出被合并的原文与来源。**它不主张两条措辞不同的告警是同一个故障**,那由人判断。\n- 数据质量：`data_quality_scorecard` `data_quality_fleet_rollup`（流程工业重点：\n staleness / flatline / bad-quality —— 仪表坏数据绝不静默插值喂 AI）\n- 分析：`oee_compute` `downtime_events` `oee_multidim` `monitor_changes`\n `health_summary` (deprecated) `anomaly_scan` (deprecated)\n- 上下文基线：`baseline_learn_contextual` `baseline_check_in_context` —— 一个位号只学一条带,\n 在它有不止一个「正常」时就是错的(同一台干燥机 recipe A 走 180 °C、B 走 240 °C,一条带横跨两者,\n 于是两个工况都不可能出错)。**上下文由人声明,绝不推断**(D16);某个上下文历史太薄就**拒学**,\n 不借用别的上下文的样本;读数落在没学过的上下文里报 `unknown_context`,**绝不回落到全局带** ——\n 回落等于把「这个工况从没见过」说成「这个工况正常」。\n- 上下游归因：`downtime_attribution` —— RCA 只按**时间**加权,所以一次上游停机会让每台下游设备\n 各自给出一个自信的本地根因。方向来自**声明的**产线顺序(D25:产线上共现是必然,拿它挖边等于\n 制造因果),顺序来自时间戳,**两者都要成立**;没声明关系就报 `not_evaluable` 并给出补法。\n- 资产：`asset_inventory` `cross_protocol_asset_model` `adopt_alias_map` `diff_alias_map`\n- 设备公告对照：`device_advisory_check` —— `scan` 早就在读 vendor/model/firmware,却什么都没做。\n 这条把它接上,并**刻意停在漏洞扫描器会继续往前走的地方**:只报「落在公告声明的版本范围内」,\n **不说「可利用」、不给严重度** —— 可达性与补偿控制决定那件事,而只读扫描看不见它们。\n **不内置任何 CVE 库**(过期却看着像最新的库比没有更糟),由现场挂载文件、离线可用,每条必须带来源。\n 读不出固件报 `version_unknown`,读得出但排不了序报 `version_unparsed` —— 都不算通过;\n 公告没提到的设备**不出现在结果里**,那是「未知」不是「没有」。\n- 基线：`baseline_learn` `baseline_check` `baseline_record_change` `baseline_status`\n （change-log 基线：拒学薄历史、只报持续越带、每次告警必引基线样本 —— 非黑盒异常检测）\n- 合规/信创：`compliance_mapping` `compliance_frameworks` `compliance_dengbao_levels`\n `compliance_report` `compliance_evidence_bundle`\n `historian_push` `export_data` `historian_query` `historian_coverage` `stream_publish` `uns_publish` `stream_publish_event` `rca_narrate` `fleet_status` `fleet_incidents` `pdm_forecast`\n `historian_push` `export_data`\n- 程序解读：`plc_program_outline` `plc_program_xref` `plc_program_section` `plc_program_visibility`（解读导出的 ST/AWL/L5X 程序,只读文件,强制引用行号）\n- 程序变更基线：`plc_program_snapshot` `plc_program_drift` `plc_program_history` — 把「认可的那一版」\n 的结构记下来（文件 SHA-256 + 每个 block 的结构指纹：声明/调用/分支条件/定时器，**不含行号、注释、\n block 顺序**，所以在文件顶上加一行注释不会把整份程序报成变更），之后问某一次导出**动没动**。\n 三个判词咬得很紧：`identical` **只**由 SHA-256 相同得出；`logic_changed` 逐 block 指出哪一类变了；\n `changed_outside_extracted_structure` = 字节变了而结构指纹全同 —— 多半是注释/排版，但这些 parser\n 是结构抽取不是文法，**所以它不叫「仅文档」，也不构成放行**。删历史只在 CLI（`iaiops program forget`）：\n 删变更控制证据不该离 agent 只有一次调用。存的是 block 名 + 哈希 + 计数，**不落声明、源码行和注释**。\n- 自证：`verify_determinism` — 把「拿掉模型、断网、同一份数据重跑、输出逐字节相同」**跑出来**：\n 固定数据集过一遍分析层，规范化后取 SHA-256，在本进程跑两遍、再在两个不同 PYTHONHASHSEED 的\n 全新解释器里各跑一遍（这一臂才抓得到集合/字典迭代顺序渗进结果），全程 socket 抛异常。\n 给 CSV/验证团队的是一条能写进 IQ/OQ 的测试用例，不是一句形容词。\n- 元：`protocols_supported`(产品能做什么)· `site_readiness`(这个站点今天能跑什么、还差什么;零联网)\n- 调查层（§13，八步证据闭环）：`investigation_readiness` `investigation_open` `investigation_show`\n `investigation_list` — 「真出事时这个站能走到第几步、每个缺口还差什么」，以及对一个**已过去的窗口**\n 逐步走完并留档（不碰设备）。缺口分两种:**你没供**(给命令) 与 **产品供不了**。\n- 产线关系与机制库：`line_relation_declare` `line_relations_list` `mechanism_library_check`\n `mechanism_library_list` — 上下游由**人声明**（D25:线上下游共现是必然，推不出因果）；\n 机制库按 ISO 14224 分 mode/mechanism/cause，**可排除、绝不确认**，\n 库里没有这条原因 → `nothing_known`（不是「无异议」）。\n\n\n## Workflows\n\n1. **Doctor-first**：`protocols_supported` → `iaiops doctor` → HART 先\n `hart_device_identity` 证明网关链路，OPC-UA 先 `opcua_diagnose_connection`。\n2. **Read-first**：仪表读 PV（`hart_primary_variable`）→ 动态变量 → burst；\n 回路异常/告警风暴用 `alarm_bad_actors`（ISA-18.2），\"没数据\"用 `diagnose_dataflow`。\n3. **MOC 写**：本 edition 三个协议的工具全部只读（无写表面）。若叠加 sparkplug，\n `mqtt_publish` 为 **[WRITE][HIGH][MOC]**：默认 `dry_run=True` + 改前状态 undo +\n `iaiops approve` 具名审批双确认。未经授权绝不写生产控制系统。\n\n## 支持版本矩阵（内部 HLD §8，设计文档不随本仓发布；`待核实` 不得当既成事实）\n\n| 协议 | 库(pin) | 规范/版本 | 覆盖 | 传输 | 自测 |\n|---|---|---|---|---|---|\n| HART-IP | `hart-protocol>=2023.6,<2025`（extra） | HART-IP（经网关） | 过程仪表：变送器/阀门定位器 | UDP/TCP 5094 | ⚠️ codec CI 自测；真机网关 待核实 |\n| OPC-UA | `asyncua>=2.0,<3` | OPC UA 1.0x（DA+HA+AC 子集） | 任意合规 Server / DCS 网关 | opc.tcp | ✅ mock+HDA |\n| Modbus-TCP | `pymodbus>=3.5,<4` | App 1.1b3；FC 1/2/3/4/5/6/15/16 | 任意 TCP 从站 | TCP/502 | ✅ |\n| Modbus-RTU | `pymodbus>=3.5,<4` + `pyserial>=3.5` | Modbus serial (RTU) | 串口从站 | RS-485/serial | ✅ socat PTY verified 2026-07-02；物理 RS-485 待核实 |\n\nFile v0.27.0:_meta.json\n\n{\n \"ownerId\": \"kn7b067awq2s97bn3d7p5qfhw5827pxc\",\n \"slug\": \"iaiops-process\",\n \"version\": \"0.27.0\",\n \"publishedAt\": 1788405626681\n}\n\nFile v0.27.0:skill-card.md\n\n## Description:\n\nProcess-industry edition of iaiops for chemical, pharma, food and beverage, and oil and gas plants, covering HART-IP process instrumentation, OPC-UA, Modbus-TCP/RTU, optional MQTT/Sparkplug B UNS, downtime root-cause analysis, data quality, and OEE workflows.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[zw008](https://clawhub.ai/user/zw008)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers, plant engineers, and OT teams use this skill to inspect process-industry telemetry and evidence from HART-IP, OPC-UA, Modbus, historian, alarm, baseline, and investigation workflows. It supports read-first diagnostics for process instrumentation, data quality, downtime attribution, advisory matching, and controlled MOC-gated publishing workflows when optional Sparkplug paths are enabled.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Export, push, publish, historian, UNS, MQTT, or Sparkplug paths could affect OT data flows if enabled without clear approval controls.\n\nMitigation: Review before installing in an OT environment; require disabled-by-default behavior or explicit approval, dry-run/review, scoped credentials, and audit logging for every publish or export path.\n\nRisk: Baselines and evidence bundles may contain operational evidence whose retention, deletion, or export controls are unclear.\n\nMitigation: Confirm where baselines and evidence bundles are stored, who can access them, who can delete them, and how exports are controlled before deployment.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/zw008/skills/iaiops-process)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance, analysis]\n\n**Output Format:** [Markdown with tool names, configuration snippets, and inline shell commands]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Outputs emphasize read-first diagnostics, cited measurements, explicit unknown states, and review before OT deployment.]\n\n## Skill Version(s):\n\n0.27.0 (source: server release metadata, created 2026-09-03)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v0.26.0: 3 files, 6267 bytes\n\nFiles: skill-card.md (2174b), SKILL.md (8306b), _meta.json (134b)\n\nFile v0.26.0:SKILL.md\n\n---\nname: iaiops-process\ndescription: >-\n Process-industry edition of iaiops — chemical / pharma / food & beverage / oil &\n gas plants: HART-IP process instrumentation (transmitters, valve positioners,\n loop current), OPC-UA (DCS / gateway read), Modbus-TCP/RTU (skids, analyzers),\n optional MQTT/Sparkplug B UNS, plus the cross-protocol brain (downtime\n root-cause, data quality, OEE). Use when the task mentions HART, HART-IP,\n transmitter, 变送器, valve positioner, process instrumentation, PV/SV/TV/QV,\n loop current, burst mode, DCS tap, or a process plant. Read-first, MOC-gated\n writes.\n---\n\n# iaiops-process — 流程工业 edition（HART + Modbus + OPC-UA + 脑）\n\n启动：`IAIOPS_MCP=process` / `iaiops-mcp-process`（= opcua + modbus + hart + 脑）。\n现场有 UNS/Sparkplug 时用 `IAIOPS_MCP=process,sparkplug`（sparkplug 工具清单见\n**iaiops-factory** skill）。HART 需 extra：`pip install iaiops[hart]`。\n\n## 工具\n\n### HART-IP（只读；过程仪表 — 变送器、阀门定位器，经网关）\n`transport` 为 `udp`（默认）或 `tcp`，端口 5094。\n- `hart_device_identity` — 通用设备身份（command 0）\n- `hart_primary_variable` — 主变量 PV（command 1）：值 + 单位码\n- `hart_dynamic_variables` — 动态变量 PV/SV/TV/QV + 回路电流（command 3）\n- `hart_burst_sample` — 主动采样 burst 发布的变量；`hart_burst_listen` — 被动监听非请求 burst publish（待核实 per 网关）\n\n### OPC-UA（只读；DCS/网关旁路读取）\n- `opcua_server_info` / `opcua_browse` / `opcua_read_node` / `opcua_read_many`\n- `opcua_subscribe_sample` `opcua_read_alarms` `opcua_alarm_events`(A&C 带时间戳) `opcua_read_history`(HDA)\n- `opcua_diagnose_connection` — 连接失败归因（证书/策略/认证/网络/配置）\n- `opcua_discover_tags` — 自动发现 + 语义资产建模\n- `opcua_health_summary` — tag vs 阈值分类；`opcua_anomaly_scan` — 有界统计异常扫描\n\n### Modbus-TCP / Modbus-RTU（只读；撬装/分析仪/RTU 从站）\n- `modbus_read_holding` `modbus_read_input` `modbus_read_coils` `modbus_read_discrete`\n- `modbus_detect_byte_order` — 字节/字序自动探测\n- `modbus_list_templates` / `modbus_apply_template` — 厂商寄存器模板 → 命名 tag\n- `modbus_health_summary` — 寄存器 vs 阈值分类\n\n### 流程专属（edition 工具;仅随 process edition 加载,不进全局脑）\n- `control_loop_health` — PID 回路诊断:从一段 PV/SP/OP 采样检出**振荡**(PV 反复穿越 SP)、\n **稳态偏差**(PV 长期偏离 SP)、**输出饱和**(OP 压在 0/100%)。给 verdict(saturated>oscillating>\n offset>ok)。非整定器,只分诊哪些回路要看。纯分析,每项引用数值。\n- `heat_exchanger_fouling` — **换热器结垢检测**:按四路温度算热侧温度效能 ε=(hot_in−hot_out)/\n (hot_in−cold_in),前后半窗对比;效能低于阈值或下降超阈即 fouling(结垢征兆,先于强制清洗)。\n 纯分析,喂 OPC-UA/Modbus/HART 温度点,verdict 引用效能数值。\n\n### 跨协议脑（永远随 server 暴露）\n- 诊断：`diagnose_dataflow` `downtime_root_cause` `downtime_root_cause_live` `downtime_triage`\n `learn_cause_weights` `rca_corpus_from_maintenance` `historian_health` `alarm_bad_actors` `tag_health`\n `subscription_health` `heartbeat_health` `alarm_flood_analysis` `alarm_cascade`\n `alarm_rationalization_worksheet`\n- 数据质量：`data_quality_scorecard` `data_quality_fleet_rollup`（流程工业重点：\n staleness / flatline / bad-quality —— 仪表坏数据绝不静默插值喂 AI）\n- 分析：`oee_compute` `downtime_events` `oee_multidim` `monitor_changes`\n `health_summary` (deprecated) `anomaly_scan` (deprecated)\n- 资产：`asset_inventory` `cross_protocol_asset_model` `adopt_alias_map` `diff_alias_map`\n- 基线：`baseline_learn` `baseline_check` `baseline_record_change` `baseline_status`\n （change-log 基线：拒学薄历史、只报持续越带、每次告警必引基线样本 —— 非黑盒异常检测）\n- 合规/信创：`compliance_mapping` `compliance_frameworks` `compliance_dengbao_levels`\n `compliance_report` `compliance_evidence_bundle`\n `historian_push` `export_data` `historian_query` `historian_coverage` `stream_publish` `uns_publish` `stream_publish_event` `rca_narrate` `fleet_status` `fleet_incidents` `pdm_forecast`\n `historian_push` `export_data`\n- 程序解读：`plc_program_outline` `plc_program_xref` `plc_program_section` `plc_program_visibility`（解读导出的 ST/AWL/L5X 程序,只读文件,强制引用行号）\n- 程序变更基线：`plc_program_snapshot` `plc_program_drift` `plc_program_history` — 把「认可的那一版」\n 的结构记下来（文件 SHA-256 + 每个 block 的结构指纹：声明/调用/分支条件/定时器，**不含行号、注释、\n block 顺序**，所以在文件顶上加一行注释不会把整份程序报成变更），之后问某一次导出**动没动**。\n 三个判词咬得很紧：`identical` **只**由 SHA-256 相同得出；`logic_changed` 逐 block 指出哪一类变了；\n `changed_outside_extracted_structure` = 字节变了而结构指纹全同 —— 多半是注释/排版，但这些 parser\n 是结构抽取不是文法，**所以它不叫「仅文档」，也不构成放行**。删历史只在 CLI（`iaiops program forget`）：\n 删变更控制证据不该离 agent 只有一次调用。存的是 block 名 + 哈希 + 计数，**不落声明、源码行和注释**。\n- 自证：`verify_determinism` — 把「拿掉模型、断网、同一份数据重跑、输出逐字节相同」**跑出来**：\n 固定数据集过一遍分析层，规范化后取 SHA-256，在本进程跑两遍、再在两个不同 PYTHONHASHSEED 的\n 全新解释器里各跑一遍（这一臂才抓得到集合/字典迭代顺序渗进结果），全程 socket 抛异常。\n 给 CSV/验证团队的是一条能写进 IQ/OQ 的测试用例，不是一句形容词。\n- 元：`protocols_supported`(产品能做什么)· `site_readiness`(这个站点今天能跑什么、还差什么;零联网)\n- 调查层（§13，八步证据闭环）：`investigation_readiness` `investigation_open` `investigation_show`\n `investigation_list` — 「真出事时这个站能走到第几步、每个缺口还差什么」，以及对一个**已过去的窗口**\n 逐步走完并留档（不碰设备）。缺口分两种:**你没供**(给命令) 与 **产品供不了**。\n- 产线关系与机制库：`line_relation_declare` `line_relations_list` `mechanism_library_check`\n `mechanism_library_list` — 上下游由**人声明**（D25:线上下游共现是必然，推不出因果）；\n 机制库按 ISO 14224 分 mode/mechanism/cause，**可排除、绝不确认**，\n 库里没有这条原因 → `nothing_known`（不是「无异议」）。\n\n\n## Workflows\n\n1. **Doctor-first**：`protocols_supported` → `iaiops doctor` → HART 先\n `hart_device_identity` 证明网关链路，OPC-UA 先 `opcua_diagnose_connection`。\n2. **Read-first**：仪表读 PV（`hart_primary_variable`）→ 动态变量 → burst；\n 回路异常/告警风暴用 `alarm_bad_actors`（ISA-18.2），\"没数据\"用 `diagnose_dataflow`。\n3. **MOC 写**：本 edition 三个协议的工具全部只读（无写表面）。若叠加 sparkplug，\n `mqtt_publish` 为 **[WRITE][HIGH][MOC]**：默认 `dry_run=True` + 改前状态 undo +\n `iaiops approve` 具名审批双确认。未经授权绝不写生产控制系统。\n\n## 支持版本矩阵（内部 HLD §8，设计文档不随本仓发布；`待核实` 不得当既成事实）\n\n| 协议 | 库(pin) | 规范/版本 | 覆盖 | 传输 | 自测 |\n|---|---|---|---|---|---|\n| HART-IP | `hart-protocol>=2023.6,<2025`（extra） | HART-IP（经网关） | 过程仪表：变送器/阀门定位器 | UDP/TCP 5094 | ⚠️ codec CI 自测；真机网关 待核实 |\n| OPC-UA | `asyncua>=2.0,<3` | OPC UA 1.0x（DA+HA+AC 子集） | 任意合规 Server / DCS 网关 | opc.tcp | ✅ mock+HDA |\n| Modbus-TCP | `pymodbus>=3.5,<4` | App 1.1b3；FC 1/2/3/4/5/6/15/16 | 任意 TCP 从站 | TCP/502 | ✅ |\n| Modbus-RTU | `pymodbus>=3.5,<4` + `pyserial>=3.5` | Modbus serial (RTU) | 串口从站 | RS-485/serial | ✅ socat PTY verified 2026-07-02；物理 RS-485 待核实 |\n\nFile v0.26.0:_meta.json\n\n{\n \"ownerId\": \"kn7b067awq2s97bn3d7p5qfhw5827pxc\",\n \"slug\": \"iaiops-process\",\n \"version\": \"0.26.0\",\n \"publishedAt\": 1788265763481\n}\n\nFile v0.26.0:skill-card.md\n\n## Description:\n\niaiops-process helps agents perform read-first process-industry diagnostics across HART-IP instrumentation, OPC-UA, Modbus, and optional MQTT/Sparkplug B workflows for chemical, pharma, food and beverage, and oil and gas plants.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[zw008](https://clawhub.ai/user/zw008)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers, reliability engineers, and process-operations teams use this skill to inspect industrial process data, triage dataflow and downtime issues, assess instrument and control-loop health, and prepare MOC-gated actions for write-capable publishing workflows.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Optional Sparkplug or MQTT publishing workflows can affect operational data handling if used in production environments.\n\nMitigation: Verify the underlying MCP server and integration configuration before production use, keep publishing in dry-run or approval-gated mode, and require site MOC approval before any write-capable workflow.\n\nRisk: Industrial diagnostics can be misleading when source telemetry is stale, flatlined, low quality, or unavailable.\n\nMitigation: Use read-only diagnostics first, cite measured values and baseline samples, and confirm data quality before using results for operational decisions.\n\n## Reference(s):\n\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, Shell commands, Configuration, Guidance]\n\n**Output Format:** [Markdown with diagnostic summaries, cited readings, and inline shell commands or configuration values when relevant]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May include baseline comparisons, process-health findings, readiness gaps, and dry-run or approval steps for write-capable publishing workflows.]\n\n## Skill Version(s):\n\n0.26.0 (source: server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v0.23.1: 3 files, 5569 bytes\n\nFiles: skill-card.md (2381b), SKILL.md (6904b), _meta.json (134b)\n\nFile v0.23.1:SKILL.md\n\n---\nname: iaiops-process\ndescription: >-\n Process-industry edition of iaiops — chemical / pharma / food & beverage / oil &\n gas plants: HART-IP process instrumentation (transmitters, valve positioners,\n loop current), OPC-UA (DCS / gateway read), Modbus-TCP/RTU (skids, analyzers),\n optional MQTT/Sparkplug B UNS, plus the cross-protocol brain (downtime\n root-cause, data quality, OEE). Use when the task mentions HART, HART-IP,\n transmitter, 变送器, valve positioner, process instrumentation, PV/SV/TV/QV,\n loop current, burst mode, DCS tap, or a process plant. Read-first, MOC-gated\n writes.\n---\n\n# iaiops-process — 流程工业 edition（HART + Modbus + OPC-UA + 脑）\n\n启动：`IAIOPS_MCP=process` / `iaiops-mcp-process`（= opcua + modbus + hart + 脑）。\n现场有 UNS/Sparkplug 时用 `IAIOPS_MCP=process,sparkplug`（sparkplug 工具清单见\n**iaiops-factory** skill）。HART 需 extra：`pip install iaiops[hart]`。\n\n## 工具\n\n### HART-IP（只读；过程仪表 — 变送器、阀门定位器，经网关）\n`transport` 为 `udp`（默认）或 `tcp`，端口 5094。\n- `hart_device_identity` — 通用设备身份（command 0）\n- `hart_primary_variable` — 主变量 PV（command 1）：值 + 单位码\n- `hart_dynamic_variables` — 动态变量 PV/SV/TV/QV + 回路电流（command 3）\n- `hart_burst_sample` — 主动采样 burst 发布的变量；`hart_burst_listen` — 被动监听非请求 burst publish（待核实 per 网关）\n\n### OPC-UA（只读；DCS/网关旁路读取）\n- `opcua_server_info` / `opcua_browse` / `opcua_read_node` / `opcua_read_many`\n- `opcua_subscribe_sample` `opcua_read_alarms` `opcua_alarm_events`(A&C 带时间戳) `opcua_read_history`(HDA)\n- `opcua_diagnose_connection` — 连接失败归因（证书/策略/认证/网络/配置）\n- `opcua_discover_tags` — 自动发现 + 语义资产建模\n- `opcua_health_summary` — tag vs 阈值分类；`opcua_anomaly_scan` — 有界统计异常扫描\n\n### Modbus-TCP / Modbus-RTU（只读；撬装/分析仪/RTU 从站）\n- `modbus_read_holding` `modbus_read_input` `modbus_read_coils` `modbus_read_discrete`\n- `modbus_detect_byte_order` — 字节/字序自动探测\n- `modbus_list_templates` / `modbus_apply_template` — 厂商寄存器模板 → 命名 tag\n- `modbus_health_summary` — 寄存器 vs 阈值分类\n\n### 流程专属（edition 工具;仅随 process edition 加载,不进全局脑）\n- `control_loop_health` — PID 回路诊断:从一段 PV/SP/OP 采样检出**振荡**(PV 反复穿越 SP)、\n **稳态偏差**(PV 长期偏离 SP)、**输出饱和**(OP 压在 0/100%)。给 verdict(saturated>oscillating>\n offset>ok)。非整定器,只分诊哪些回路要看。纯分析,每项引用数值。\n- `heat_exchanger_fouling` — **换热器结垢检测**:按四路温度算热侧温度效能 ε=(hot_in−hot_out)/\n (hot_in−cold_in),前后半窗对比;效能低于阈值或下降超阈即 fouling(结垢征兆,先于强制清洗)。\n 纯分析,喂 OPC-UA/Modbus/HART 温度点,verdict 引用效能数值。\n\n### 跨协议脑（永远随 server 暴露）\n- 诊断：`diagnose_dataflow` `downtime_root_cause` `downtime_root_cause_live` `downtime_triage`\n `learn_cause_weights` `rca_corpus_from_maintenance` `historian_health` `alarm_bad_actors` `tag_health`\n `subscription_health` `heartbeat_health` `alarm_flood_analysis` `alarm_cascade`\n `alarm_rationalization_worksheet`\n- 数据质量：`data_quality_scorecard` `data_quality_fleet_rollup`（流程工业重点：\n staleness / flatline / bad-quality —— 仪表坏数据绝不静默插值喂 AI）\n- 分析：`oee_compute` `downtime_events` `oee_multidim` `monitor_changes`\n `health_summary` (deprecated) `anomaly_scan` (deprecated)\n- 资产：`asset_inventory` `cross_protocol_asset_model` `adopt_alias_map` `diff_alias_map`\n- 基线：`baseline_learn` `baseline_check` `baseline_record_change` `baseline_status`\n （change-log 基线：拒学薄历史、只报持续越带、每次告警必引基线样本 —— 非黑盒异常检测）\n- 合规/信创：`compliance_mapping` `compliance_frameworks` `compliance_dengbao_levels`\n `compliance_report` `compliance_evidence_bundle`\n `historian_push` `export_data` `historian_query` `historian_coverage` `stream_publish` `uns_publish` `stream_publish_event` `rca_narrate` `fleet_status` `fleet_incidents` `pdm_forecast`\n `historian_push` `export_data`\n- 程序解读：`plc_program_outline` `plc_program_xref` `plc_program_section` `plc_program_visibility`（解读导出的 ST/AWL/L5X 程序,只读文件,强制引用行号）\n- 元：`protocols_supported`(产品能做什么)· `site_readiness`(这个站点今天能跑什么、还差什么;零联网)\n- 调查层（§13，八步证据闭环）：`investigation_readiness` `investigation_open` `investigation_show`\n `investigation_list` — 「真出事时这个站能走到第几步、每个缺口还差什么」，以及对一个**已过去的窗口**\n 逐步走完并留档（不碰设备）。缺口分两种:**你没供**(给命令) 与 **产品供不了**。\n- 产线关系与机制库：`line_relation_declare` `line_relations_list` `mechanism_library_check`\n `mechanism_library_list` — 上下游由**人声明**（D25:线上下游共现是必然，推不出因果）；\n 机制库按 ISO 14224 分 mode/mechanism/cause，**可排除、绝不确认**，\n 库里没有这条原因 → `nothing_known`（不是「无异议」）。\n\n\n## Workflows\n\n1. **Doctor-first**：`protocols_supported` → `iaiops doctor` → HART 先\n `hart_device_identity` 证明网关链路，OPC-UA 先 `opcua_diagnose_connection`。\n2. **Read-first**：仪表读 PV（`hart_primary_variable`）→ 动态变量 → burst；\n 回路异常/告警风暴用 `alarm_bad_actors`（ISA-18.2），\"没数据\"用 `diagnose_dataflow`。\n3. **MOC 写**：本 edition 三个协议的工具全部只读（无写表面）。若叠加 sparkplug，\n `mqtt_publish` 为 **[WRITE][HIGH][MOC]**：默认 `dry_run=True` + 改前状态 undo +\n `iaiops approve` 具名审批双确认。未经授权绝不写生产控制系统。\n\n## 支持版本矩阵（内部 HLD §8，设计文档不随本仓发布；`待核实` 不得当既成事实）\n\n| 协议 | 库(pin) | 规范/版本 | 覆盖 | 传输 | 自测 |\n|---|---|---|---|---|---|\n| HART-IP | `hart-protocol>=2023.6,<2025`（extra） | HART-IP（经网关） | 过程仪表：变送器/阀门定位器 | UDP/TCP 5094 | ⚠️ codec CI 自测；真机网关 待核实 |\n| OPC-UA | `asyncua>=2.0,<3` | OPC UA 1.0x（DA+HA+AC 子集） | 任意合规 Server / DCS 网关 | opc.tcp | ✅ mock+HDA |\n| Modbus-TCP | `pymodbus>=3.5,<4` | App 1.1b3；FC 1/2/3/4/5/6/15/16 | 任意 TCP 从站 | TCP/502 | ✅ |\n| Modbus-RTU | `pymodbus>=3.5,<4` + `pyserial>=3.5` | Modbus serial (RTU) | 串口从站 | RS-485/serial | ✅ socat PTY verified 2026-07-02；物理 RS-485 待核实 |\n\nFile v0.23.1:_meta.json\n\n{\n \"ownerId\": \"kn7b067awq2s97bn3d7p5qfhw5827pxc\",\n \"slug\": \"iaiops-process\",\n \"version\": \"0.23.1\",\n \"publishedAt\": 1787894352960\n}\n\nFile v0.23.1:skill-card.md\n\n## Description:\n\niaiops-process helps agents support process-industry diagnostics across HART-IP instrumentation, OPC-UA reads, Modbus devices, optional MQTT/Sparkplug UNS workflows, data quality, downtime root-cause analysis, and OEE with read-first and MOC-gated write posture.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[zw008](https://clawhub.ai/user/zw008)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers, engineers, and operations teams use this skill to guide read-first investigation of process plants, including HART-IP instrument checks, OPC-UA or Modbus data access, alarm and downtime triage, data quality review, and evidence-based investigation workflows. Any write-adjacent publishing or export workflow should be reviewed under management-of-change controls before use on live or production-adjacent networks.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Read-only claims conflict with documented write-capable Modbus coverage.\n\nMitigation: Confirm Modbus write function codes are rejected by default before installation or use in any live plant or production-adjacent network.\n\nRisk: Export, historian push, stream publish, UNS, MQTT, or Sparkplug workflows may move plant data or affect connected systems if under-scoped.\n\nMitigation: Require explicit destination allowlists, named approvals, audit logging, and management-of-change review for any publish or export workflow.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/zw008/skills/iaiops-process)\n- [ClawHub publisher profile](https://clawhub.ai/user/zw008)\n\n## Skill Output:\n\n**Output Type(s):** [guidance, shell commands, configuration, markdown, text]\n\n**Output Format:** [Markdown guidance with inline commands and structured operational recommendations]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Outputs should preserve read-first posture, cite supplied plant evidence where applicable, and surface approval requirements for write-adjacent actions.]\n\n## Skill Version(s):\n\n0.23.1 (source: server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v0.23.0: 3 files, 5070 bytes\n\nFiles: skill-card.md (2348b), SKILL.md (6065b), _meta.json (134b)\n\nFile v0.23.0:SKILL.md\n\n---\nname: iaiops-process\ndescription: >-\n Process-industry edition of iaiops — chemical / pharma / food & beverage / oil &\n gas plants: HART-IP process instrumentation (transmitters, valve positioners,\n loop current), OPC-UA (DCS / gateway read), Modbus-TCP/RTU (skids, analyzers),\n optional MQTT/Sparkplug B UNS, plus the cross-protocol brain (downtime\n root-cause, data quality, OEE). Use when the task mentions HART, HART-IP,\n transmitter, 变送器, valve positioner, process instrumentation, PV/SV/TV/QV,\n loop current, burst mode, DCS tap, or a process plant. Read-first, MOC-gated\n writes.\n---\n\n# iaiops-process — 流程工业 edition（HART + Modbus + OPC-UA + 脑）\n\n启动：`IAIOPS_MCP=process` / `iaiops-mcp-process`（= opcua + modbus + hart + 脑）。\n现场有 UNS/Sparkplug 时用 `IAIOPS_MCP=process,sparkplug`（sparkplug 工具清单见\n**iaiops-factory** skill）。HART 需 extra：`pip install iaiops[hart]`。\n\n## 工具\n\n### HART-IP（只读；过程仪表 — 变送器、阀门定位器，经网关）\n`transport` 为 `udp`（默认）或 `tcp`，端口 5094。\n- `hart_device_identity` — 通用设备身份（command 0）\n- `hart_primary_variable` — 主变量 PV（command 1）：值 + 单位码\n- `hart_dynamic_variables` — 动态变量 PV/SV/TV/QV + 回路电流（command 3）\n- `hart_burst_sample` — 主动采样 burst 发布的变量；`hart_burst_listen` — 被动监听非请求 burst publish（待核实 per 网关）\n\n### OPC-UA（只读；DCS/网关旁路读取）\n- `opcua_server_info` / `opcua_browse` / `opcua_read_node` / `opcua_read_many`\n- `opcua_subscribe_sample` `opcua_read_alarms` `opcua_alarm_events`(A&C 带时间戳) `opcua_read_history`(HDA)\n- `opcua_diagnose_connection` — 连接失败归因（证书/策略/认证/网络/配置）\n- `opcua_discover_tags` — 自动发现 + 语义资产建模\n- `opcua_health_summary` — tag vs 阈值分类；`opcua_anomaly_scan` — 有界统计异常扫描\n\n### Modbus-TCP / Modbus-RTU（只读；撬装/分析仪/RTU 从站）\n- `modbus_read_holding` `modbus_read_input` `modbus_read_coils` `modbus_read_discrete`\n- `modbus_detect_byte_order` — 字节/字序自动探测\n- `modbus_list_templates` / `modbus_apply_template` — 厂商寄存器模板 → 命名 tag\n- `modbus_health_summary` — 寄存器 vs 阈值分类\n\n### 流程专属（edition 工具;仅随 process edition 加载,不进全局脑）\n- `control_loop_health` — PID 回路诊断:从一段 PV/SP/OP 采样检出**振荡**(PV 反复穿越 SP)、\n **稳态偏差**(PV 长期偏离 SP)、**输出饱和**(OP 压在 0/100%)。给 verdict(saturated>oscillating>\n offset>ok)。非整定器,只分诊哪些回路要看。纯分析,每项引用数值。\n- `heat_exchanger_fouling` — **换热器结垢检测**:按四路温度算热侧温度效能 ε=(hot_in−hot_out)/\n (hot_in−cold_in),前后半窗对比;效能低于阈值或下降超阈即 fouling(结垢征兆,先于强制清洗)。\n 纯分析,喂 OPC-UA/Modbus/HART 温度点,verdict 引用效能数值。\n\n### 跨协议脑（永远随 server 暴露）\n- 诊断：`diagnose_dataflow` `downtime_root_cause` `downtime_root_cause_live` `downtime_triage`\n `learn_cause_weights` `rca_corpus_from_maintenance` `historian_health` `alarm_bad_actors` `tag_health`\n `subscription_health` `heartbeat_health` `alarm_flood_analysis` `alarm_cascade`\n `alarm_rationalization_worksheet`\n- 数据质量：`data_quality_scorecard` `data_quality_fleet_rollup`（流程工业重点：\n staleness / flatline / bad-quality —— 仪表坏数据绝不静默插值喂 AI）\n- 分析：`oee_compute` `downtime_events` `oee_multidim` `monitor_changes`\n `health_summary` (deprecated) `anomaly_scan` (deprecated)\n- 资产：`asset_inventory` `cross_protocol_asset_model` `adopt_alias_map` `diff_alias_map`\n- 基线：`baseline_learn` `baseline_check` `baseline_record_change` `baseline_status`\n （change-log 基线：拒学薄历史、只报持续越带、每次告警必引基线样本 —— 非黑盒异常检测）\n- 合规/信创：`compliance_mapping` `compliance_frameworks` `compliance_dengbao_levels`\n `compliance_report` `compliance_evidence_bundle`\n `historian_push` `export_data` `historian_query` `historian_coverage` `stream_publish` `uns_publish` `stream_publish_event` `rca_narrate` `fleet_status` `fleet_incidents` `pdm_forecast`\n `historian_push` `export_data`\n- 程序解读：`plc_program_outline` `plc_program_xref` `plc_program_section` `plc_program_visibility`（解读导出的 ST/AWL/L5X 程序,只读文件,强制引用行号）\n- 元：`protocols_supported`\n\n## Workflows\n\n1. **Doctor-first**：`protocols_supported` → `iaiops doctor` → HART 先\n `hart_device_identity` 证明网关链路，OPC-UA 先 `opcua_diagnose_connection`。\n2. **Read-first**：仪表读 PV（`hart_primary_variable`）→ 动态变量 → burst；\n 回路异常/告警风暴用 `alarm_bad_actors`（ISA-18.2），\"没数据\"用 `diagnose_dataflow`。\n3. **MOC 写**：本 edition 三个协议的工具全部只读（无写表面）。若叠加 sparkplug，\n `mqtt_publish` 为 **[WRITE][HIGH][MOC]**：默认 `dry_run=True` + 改前状态 undo +\n `iaiops approve` 具名审批双确认。未经授权绝不写生产控制系统。\n\n## 支持版本矩阵（内部 HLD §8，设计文档不随本仓发布；`待核实` 不得当既成事实）\n\n| 协议 | 库(pin) | 规范/版本 | 覆盖 | 传输 | 自测 |\n|---|---|---|---|---|---|\n| HART-IP | `hart-protocol>=2023.6,<2025`（extra） | HART-IP（经网关） | 过程仪表：变送器/阀门定位器 | UDP/TCP 5094 | ⚠️ codec CI 自测；真机网关 待核实 |\n| OPC-UA | `asyncua>=2.0,<3` | OPC UA 1.0x（DA+HA+AC 子集） | 任意合规 Server / DCS 网关 | opc.tcp | ✅ mock+HDA |\n| Modbus-TCP | `pymodbus>=3.5,<4` | App 1.1b3；FC 1/2/3/4/5/6/15/16 | 任意 TCP 从站 | TCP/502 | ✅ |\n| Modbus-RTU | `pymodbus>=3.5,<4` + `pyserial>=3.5` | Modbus serial (RTU) | 串口从站 | RS-485/serial | ✅ socat PTY verified 2026-07-02；物理 RS-485 待核实 |\n\nFile v0.23.0:_meta.json\n\n{\n \"ownerId\": \"kn7b067awq2s97bn3d7p5qfhw5827pxc\",\n \"slug\": \"iaiops-process\",\n \"version\": \"0.23.0\",\n \"publishedAt\": 1787632335818\n}\n\nFile v0.23.0:skill-card.md\n\n## Description:\n\niaiops-process helps agents support process-industry operations across HART-IP, OPC-UA, Modbus, optional MQTT/Sparkplug B UNS, and cross-protocol diagnostics for instrumentation, downtime root cause, data quality, and OEE.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[zw008](https://clawhub.ai/user/zw008)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and plant engineers use this skill to guide read-first monitoring and diagnosis for chemical, pharmaceutical, food and beverage, and oil and gas process environments spanning HART-IP instruments, OPC-UA/DCS gateways, Modbus devices, and optional UNS/Sparkplug workflows. It is suited to troubleshooting data flow, alarm and downtime causes, tag quality, loop health, and process asset context while requiring review before any write-capable deployment.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Read-only safety framing conflicts with documented write, export, publish, and Modbus write-capable paths.\n\nMitigation: Review before installation in any plant or production-like environment; require explicit approval, dry-run controls, and documented change management for any write-capable action.\n\nRisk: Production control network exposure could occur if historian, export, stream, UNS, or Modbus write paths are enabled before the documentation and tool surface are aligned.\n\nMitigation: Confirm the exposed tool surface before deployment and avoid connecting to production control networks until the enabled capabilities and controls are clear.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/zw008/skills/iaiops-process)\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, Shell commands, Configuration, Guidance]\n\n**Output Format:** [Markdown guidance with inline tool names and shell commands]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May include operational approval and dry-run guidance for write-capable paths.]\n\n## Skill Version(s):\n\n0.23.0 (source: server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v0.22.0: 3 files, 5203 bytes\n\nFiles: skill-card.md (2840b), SKILL.md (6051b), _meta.json (134b)\n\nFile v0.22.0:SKILL.md\n\n---\nname: iaiops-process\ndescription: >-\n Process-industry edition of iaiops — chemical / pharma / food & beverage / oil &\n gas plants: HART-IP process instrumentation (transmitters, valve positioners,\n loop current), OPC-UA (DCS / gateway read), Modbus-TCP/RTU (skids, analyzers),\n optional MQTT/Sparkplug B UNS, plus the cross-protocol brain (downtime\n root-cause, data quality, OEE). Use when the task mentions HART, HART-IP,\n transmitter, 变送器, valve positioner, process instrumentation, PV/SV/TV/QV,\n loop current, burst mode, DCS tap, or a process plant. Read-first, MOC-gated\n writes.\n---\n\n# iaiops-process — 流程工业 edition（HART + Modbus + OPC-UA + 脑）\n\n启动：`IAIOPS_MCP=process` / `iaiops-mcp-process`（= opcua + modbus + hart + 脑）。\n现场有 UNS/Sparkplug 时用 `IAIOPS_MCP=process,sparkplug`（sparkplug 工具清单见\n**iaiops-factory** skill）。HART 需 extra：`pip install iaiops[hart]`。\n\n## 工具\n\n### HART-IP（只读；过程仪表 — 变送器、阀门定位器，经网关）\n`transport` 为 `udp`（默认）或 `tcp`，端口 5094。\n- `hart_device_identity` — 通用设备身份（command 0）\n- `hart_primary_variable` — 主变量 PV（command 1）：值 + 单位码\n- `hart_dynamic_variables` — 动态变量 PV/SV/TV/QV + 回路电流（command 3）\n- `hart_burst_sample` — 主动采样 burst 发布的变量；`hart_burst_listen` — 被动监听非请求 burst publish（待核实 per 网关）\n\n### OPC-UA（只读；DCS/网关旁路读取）\n- `opcua_server_info` / `opcua_browse` / `opcua_read_node` / `opcua_read_many`\n- `opcua_subscribe_sample` `opcua_read_alarms` `opcua_alarm_events`(A&C 带时间戳) `opcua_read_history`(HDA)\n- `opcua_diagnose_connection` — 连接失败归因（证书/策略/认证/网络/配置）\n- `opcua_discover_tags` — 自动发现 + 语义资产建模\n- `opcua_health_summary` — tag vs 阈值分类；`opcua_anomaly_scan` — 有界统计异常扫描\n\n### Modbus-TCP / Modbus-RTU（只读；撬装/分析仪/RTU 从站）\n- `modbus_read_holding` `modbus_read_input` `modbus_read_coils` `modbus_read_discrete`\n- `modbus_detect_byte_order` — 字节/字序自动探测\n- `modbus_list_templates` / `modbus_apply_template` — 厂商寄存器模板 → 命名 tag\n- `modbus_health_summary` — 寄存器 vs 阈值分类\n\n### 流程专属（edition 工具;仅随 process edition 加载,不进全局脑）\n- `control_loop_health` — PID 回路诊断:从一段 PV/SP/OP 采样检出**振荡**(PV 反复穿越 SP)、\n **稳态偏差**(PV 长期偏离 SP)、**输出饱和**(OP 压在 0/100%)。给 verdict(saturated>oscillating>\n offset>ok)。非整定器,只分诊哪些回路要看。纯分析,每项引用数值。\n- `heat_exchanger_fouling` — **换热器结垢检测**:按四路温度算热侧温度效能 ε=(hot_in−hot_out)/\n (hot_in−cold_in),前后半窗对比;效能低于阈值或下降超阈即 fouling(结垢征兆,先于强制清洗)。\n 纯分析,喂 OPC-UA/Modbus/HART 温度点,verdict 引用效能数值。\n\n### 跨协议脑（永远随 server 暴露）\n- 诊断：`diagnose_dataflow` `downtime_root_cause` `downtime_root_cause_live` `downtime_triage`\n `learn_cause_weights` `rca_corpus_from_maintenance` `historian_health` `alarm_bad_actors` `tag_health`\n `subscription_health` `heartbeat_health` `alarm_flood_analysis` `alarm_cascade`\n `alarm_rationalization_worksheet`\n- 数据质量：`data_quality_scorecard` `data_quality_fleet_rollup`（流程工业重点：\n staleness / flatline / bad-quality —— 仪表坏数据绝不静默插值喂 AI）\n- 分析：`oee_compute` `downtime_events` `oee_multidim` `monitor_changes`\n `health_summary` (deprecated) `anomaly_scan` (deprecated)\n- 资产：`asset_inventory` `cross_protocol_asset_model` `adopt_alias_map` `diff_alias_map`\n- 基线：`baseline_learn` `baseline_check` `baseline_record_change` `baseline_status`\n （change-log 基线：拒学薄历史、只报持续越带、每次告警必引基线样本 —— 非黑盒异常检测）\n- 合规/信创：`compliance_mapping` `compliance_frameworks` `compliance_dengbao_levels`\n `compliance_report` `compliance_evidence_bundle`\n `historian_push` `export_data` `historian_query` `historian_coverage` `stream_publish` `stream_publish_event` `rca_narrate` `fleet_status` `fleet_incidents` `pdm_forecast`\n `historian_push` `export_data`\n- 程序解读：`plc_program_outline` `plc_program_xref` `plc_program_section` `plc_program_visibility`（解读导出的 ST/AWL/L5X 程序,只读文件,强制引用行号）\n- 元：`protocols_supported`\n\n## Workflows\n\n1. **Doctor-first**：`protocols_supported` → `iaiops doctor` → HART 先\n `hart_device_identity` 证明网关链路，OPC-UA 先 `opcua_diagnose_connection`。\n2. **Read-first**：仪表读 PV（`hart_primary_variable`）→ 动态变量 → burst；\n 回路异常/告警风暴用 `alarm_bad_actors`（ISA-18.2），\"没数据\"用 `diagnose_dataflow`。\n3. **MOC 写**：本 edition 三个协议的工具全部只读（无写表面）。若叠加 sparkplug，\n `mqtt_publish` 为 **[WRITE][HIGH][MOC]**：默认 `dry_run=True` + 改前状态 undo +\n `iaiops approve` 具名审批双确认。未经授权绝不写生产控制系统。\n\n## 支持版本矩阵（内部 HLD §8，设计文档不随本仓发布；`待核实` 不得当既成事实）\n\n| 协议 | 库(pin) | 规范/版本 | 覆盖 | 传输 | 自测 |\n|---|---|---|---|---|---|\n| HART-IP | `hart-protocol>=2023.6,<2025`（extra） | HART-IP（经网关） | 过程仪表：变送器/阀门定位器 | UDP/TCP 5094 | ⚠️ codec CI 自测；真机网关 待核实 |\n| OPC-UA | `asyncua>=2.0,<3` | OPC UA 1.0x（DA+HA+AC 子集） | 任意合规 Server / DCS 网关 | opc.tcp | ✅ mock+HDA |\n| Modbus-TCP | `pymodbus>=3.5,<4` | App 1.1b3；FC 1/2/3/4/5/6/15/16 | 任意 TCP 从站 | TCP/502 | ✅ |\n| Modbus-RTU | `pymodbus>=3.5,<4` + `pyserial>=3.5` | Modbus serial (RTU) | 串口从站 | RS-485/serial | ✅ socat PTY verified 2026-07-02；物理 RS-485 待核实 |\n\nFile v0.22.0:_meta.json\n\n{\n \"ownerId\": \"kn7b067awq2s97bn3d7p5qfhw5827pxc\",\n \"slug\": \"iaiops-process\",\n \"version\": \"0.22.0\",\n \"publishedAt\": 1785676167731\n}\n\nFile v0.22.0:skill-card.md\n\n## Description:
\nProcess-industry edition of iaiops for chemical, pharma, food and beverage, and oil and gas plants, covering HART-IP process instrumentation, OPC-UA DCS/gateway reads, Modbus-TCP/RTU assets, optional MQTT/Sparkplug B UNS workflows, and cross-protocol diagnostics for root cause, data quality, and OEE.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[zw008](https://clawhub.ai/user/zw008)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers, process engineers, and plant operations teams use this skill to inspect process-instrumentation and plant-data workflows across HART-IP, OPC-UA, Modbus, and optional Sparkplug/UNS paths. It supports read-first diagnostics for dataflow, alarms, historian health, asset modeling, loop health, heat-exchanger fouling, downtime root cause, data quality, and OEE.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The release security summary flags tension between read-only claims and data-publishing or possible write-capable behavior.
\nMitigation: Review the skill before production or plant-connected installation, confirm Modbus writes are disabled, and require explicit approval for historian export, push, or stream publishing.
\nRisk: Plant diagnostics and generated guidance could be incorrect or misleading if used without operational review.
\nMitigation: Use outputs as diagnostic support, review them with qualified plant personnel, and scan the skill before deployment.
\nRisk: Optional MQTT/Sparkplug publishing can affect external systems if enabled without controls.
\nMitigation: Keep publishing workflows dry-run or approval-gated by default, require named authorization, and limit targets to intended non-production or approved production systems.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/zw008/skills/iaiops-process)
\n- [ClawHub publisher profile](https://clawhub.ai/user/zw008)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]
\n**Output Format:** [Markdown guidance with tool names, workflow steps, shell commands, and configuration environment variables]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Read-first process diagnostics; optional publishing or write-like workflows should remain explicitly approved and scoped to intended systems.]
\n\n## Skill Version(s):
\n0.22.0 (source: server release evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v0.21.1: 3 files, 5227 bytes\n\nFiles: skill-card.md (2902b), SKILL.md (6051b), _meta.json (134b)\n\nFile v0.21.1:SKILL.md\n\n---\nname: iaiops-process\ndescription: >-\n Process-industry edition of iaiops — chemical / pharma / food & beverage / oil &\n gas plants: HART-IP process instrumentation (transmitters, valve positioners,\n loop current), OPC-UA (DCS / gateway read), Modbus-TCP/RTU (skids, analyzers),\n optional MQTT/Sparkplug B UNS, plus the cross-protocol brain (downtime\n root-cause, data quality, OEE). Use when the task mentions HART, HART-IP,\n transmitter, 变送器, valve positioner, process instrumentation, PV/SV/TV/QV,\n loop current, burst mode, DCS tap, or a process plant. Read-first, MOC-gated\n writes.\n---\n\n# iaiops-process — 流程工业 edition（HART + Modbus + OPC-UA + 脑）\n\n启动：`IAIOPS_MCP=process` / `iaiops-mcp-process`（= opcua + modbus + hart + 脑）。\n现场有 UNS/Sparkplug 时用 `IAIOPS_MCP=process,sparkplug`（sparkplug 工具清单见\n**iaiops-factory** skill）。HART 需 extra：`pip install iaiops[hart]`。\n\n## 工具\n\n### HART-IP（只读；过程仪表 — 变送器、阀门定位器，经网关）\n`transport` 为 `udp`（默认）或 `tcp`，端口 5094。\n- `hart_device_identity` — 通用设备身份（command 0）\n- `hart_primary_variable` — 主变量 PV（command 1）：值 + 单位码\n- `hart_dynamic_variables` — 动态变量 PV/SV/TV/QV + 回路电流（command 3）\n- `hart_burst_sample` — 主动采样 burst 发布的变量；`hart_burst_listen` — 被动监听非请求 burst publish（待核实 per 网关）\n\n### OPC-UA（只读；DCS/网关旁路读取）\n- `opcua_server_info` / `opcua_browse` / `opcua_read_node` / `opcua_read_many`\n- `opcua_subscribe_sample` `opcua_read_alarms` `opcua_alarm_events`(A&C 带时间戳) `opcua_read_history`(HDA)\n- `opcua_diagnose_connection` — 连接失败归因（证书/策略/认证/网络/配置）\n- `opcua_discover_tags` — 自动发现 + 语义资产建模\n- `opcua_health_summary` — tag vs 阈值分类；`opcua_anomaly_scan` — 有界统计异常扫描\n\n### Modbus-TCP / Modbus-RTU（只读；撬装/分析仪/RTU 从站）\n- `modbus_read_holding` `modbus_read_input` `modbus_read_coils` `modbus_read_discrete`\n- `modbus_detect_byte_order` — 字节/字序自动探测\n- `modbus_list_templates` / `modbus_apply_template` — 厂商寄存器模板 → 命名 tag\n- `modbus_health_summary` — 寄存器 vs 阈值分类\n\n### 流程专属（edition 工具;仅随 process edition 加载,不进全局脑）\n- `control_loop_health` — PID 回路诊断:从一段 PV/SP/OP 采样检出**振荡**(PV 反复穿越 SP)、\n **稳态偏差**(PV 长期偏离 SP)、**输出饱和**(OP 压在 0/100%)。给 verdict(saturated>oscillating>\n offset>ok)。非整定器,只分诊哪些回路要看。纯分析,每项引用数值。\n- `heat_exchanger_fouling` — **换热器结垢检测**:按四路温度算热侧温度效能 ε=(hot_in−hot_out)/\n (hot_in−cold_in),前后半窗对比;效能低于阈值或下降超阈即 fouling(结垢征兆,先于强制清洗)。\n 纯分析,喂 OPC-UA/Modbus/HART 温度点,verdict 引用效能数值。\n\n### 跨协议脑（永远随 server 暴露）\n- 诊断：`diagnose_dataflow` `downtime_root_cause` `downtime_root_cause_live` `downtime_triage`\n `learn_cause_weights` `rca_corpus_from_maintenance` `historian_health` `alarm_bad_actors` `tag_health`\n `subscription_health` `heartbeat_health` `alarm_flood_analysis` `alarm_cascade`\n `alarm_rationalization_worksheet`\n- 数据质量：`data_quality_scorecard` `data_quality_fleet_rollup`（流程工业重点：\n staleness / flatline / bad-quality —— 仪表坏数据绝不静默插值喂 AI）\n- 分析：`oee_compute` `downtime_events` `oee_multidim` `monitor_changes`\n `health_summary` (deprecated) `anomaly_scan` (deprecated)\n- 资产：`asset_inventory` `cross_protocol_asset_model` `adopt_alias_map` `diff_alias_map`\n- 基线：`baseline_learn` `baseline_check` `baseline_record_change` `baseline_status`\n （change-log 基线：拒学薄历史、只报持续越带、每次告警必引基线样本 —— 非黑盒异常检测）\n- 合规/信创：`compliance_mapping` `compliance_frameworks` `compliance_dengbao_levels`\n `compliance_report` `compliance_evidence_bundle`\n `historian_push` `export_data` `historian_query` `historian_coverage` `stream_publish` `stream_publish_event` `rca_narrate` `fleet_status` `fleet_incidents` `pdm_forecast`\n `historian_push` `export_data`\n- 程序解读：`plc_program_outline` `plc_program_xref` `plc_program_section` `plc_program_visibility`（解读导出的 ST/AWL/L5X 程序,只读文件,强制引用行号）\n- 元：`protocols_supported`\n\n## Workflows\n\n1. **Doctor-first**：`protocols_supported` → `iaiops doctor` → HART 先\n `hart_device_identity` 证明网关链路，OPC-UA 先 `opcua_diagnose_connection`。\n2. **Read-first**：仪表读 PV（`hart_primary_variable`）→ 动态变量 → burst；\n 回路异常/告警风暴用 `alarm_bad_actors`（ISA-18.2），\"没数据\"用 `diagnose_dataflow`。\n3. **MOC 写**：本 edition 三个协议的工具全部只读（无写表面）。若叠加 sparkplug，\n `mqtt_publish` 为 **[WRITE][HIGH][MOC]**：默认 `dry_run=True` + 改前状态 undo +\n `iaiops approve` 具名审批双确认。未经授权绝不写生产控制系统。\n\n## 支持版本矩阵（内部 HLD §8，设计文档不随本仓发布；`待核实` 不得当既成事实）\n\n| 协议 | 库(pin) | 规范/版本 | 覆盖 | 传输 | 自测 |\n|---|---|---|---|---|---|\n| HART-IP | `hart-protocol>=2023.6,<2025`（extra） | HART-IP（经网关） | 过程仪表：变送器/阀门定位器 | UDP/TCP 5094 | ⚠️ codec CI 自测；真机网关 待核实 |\n| OPC-UA | `asyncua>=1.0,<2` | OPC UA 1.0x（DA+HA+AC 子集） | 任意合规 Server / DCS 网关 | opc.tcp | ✅ mock+HDA |\n| Modbus-TCP | `pymodbus>=3.5,<4` | App 1.1b3；FC 1/2/3/4/5/6/15/16 | 任意 TCP 从站 | TCP/502 | ✅ |\n| Modbus-RTU | `pymodbus>=3.5,<4` + `pyserial>=3.5` | Modbus serial (RTU) | 串口从站 | RS-485/serial | ✅ socat PTY verified 2026-07-02；物理 RS-485 待核实 |\n\nFile v0.21.1:_meta.json\n\n{\n \"ownerId\": \"kn7b067awq2s97bn3d7p5qfhw5827pxc\",\n \"slug\": \"iaiops-process\",\n \"version\": \"0.21.1\",\n \"publishedAt\": 1785655501842\n}\n\nFile v0.21.1:skill-card.md\n\n## Description:
\nProcess-industry edition of iaiops for chemical, pharmaceutical, food and beverage, and oil and gas plants, covering HART-IP process instrumentation, OPC-UA reads, Modbus-TCP/RTU, optional MQTT/Sparkplug B UNS, and cross-protocol diagnostics for downtime root cause, data quality, and OEE.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[zw008](https://clawhub.ai/user/zw008)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and process engineers use this skill to inspect process-plant telemetry across HART-IP, OPC-UA, Modbus, and optional MQTT/Sparkplug B, then generate diagnostic guidance for loop health, equipment fouling, data quality, downtime root cause, alarms, historian coverage, OEE, and compliance evidence.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: Use near live plant systems may affect historian pushes, stream publishing, exports, baseline updates, alias adoption, or Modbus-capable operations despite the skill's read-oriented framing.
\nMitigation: Require explicit operator approval, scoped configuration boundaries, and change-management review before enabling those operations.
\nRisk: The skill describes MOC-gated write behavior for optional MQTT/Sparkplug use and includes publish/export surfaces that can move data beyond read-only diagnostics.
\nMitigation: Keep dry-run behavior enabled where available, require named approval before production writes or publishes, and verify target endpoints before execution.
\nRisk: Industrial diagnostic outputs may be misleading if based on thin history, stale tags, bad-quality values, or unverified gateway behavior.
\nMitigation: Validate source data quality, quote underlying samples in diagnostic conclusions, and require engineering review before operational decisions.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/zw008/skills/iaiops-process)
\n- [Publisher profile](https://clawhub.ai/user/zw008)
\n\n\n## Skill Output:
\n**Output Type(s):** [Text, Markdown, Shell commands, Configuration, Guidance]
\n**Output Format:** [Markdown and text guidance with inline shell commands and configuration values]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Read-first industrial diagnostics; write-capable publish, export, historian, baseline, alias, and Modbus-related operations require explicit operator approval and configuration boundaries.]
\n\n## Skill Version(s):
\n0.21.1 (source: server release evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v0.21.0: 3 files, 4975 bytes\n\nFiles: skill-card.md (2245b), SKILL.md (6051b), _meta.json (134b)\n\nFile v0.21.0:SKILL.md\n\n---\nname: iaiops-process\ndescription: >-\n Process-industry edition of iaiops — chemical / pharma / food & beverage / oil &\n gas plants: HART-IP process instrumentation (transmitters, valve positioners,\n loop current), OPC-UA (DCS / gateway read), Modbus-TCP/RTU (skids, analyzers),\n optional MQTT/Sparkplug B UNS, plus the cross-protocol brain (downtime\n root-cause, data quality, OEE). Use when the task mentions HART, HART-IP,\n transmitter, 变送器, valve positioner, process instrumentation, PV/SV/TV/QV,\n loop current, burst mode, DCS tap, or a process plant. Read-first, MOC-gated\n writes.\n---\n\n# iaiops-process — 流程工业 edition（HART + Modbus + OPC-UA + 脑）\n\n启动：`IAIOPS_MCP=process` / `iaiops-mcp-process`（= opcua + modbus + hart + 脑）。\n现场有 UNS/Sparkplug 时用 `IAIOPS_MCP=process,sparkplug`（sparkplug 工具清单见\n**iaiops-factory** skill）。HART 需 extra：`pip install iaiops[hart]`。\n\n## 工具\n\n### HART-IP（只读；过程仪表 — 变送器、阀门定位器，经网关）\n`transport` 为 `udp`（默认）或 `tcp`，端口 5094。\n- `hart_device_identity` — 通用设备身份（command 0）\n- `hart_primary_variable` — 主变量 PV（command 1）：值 + 单位码\n- `hart_dynamic_variables` — 动态变量 PV/SV/TV/QV + 回路电流（command 3）\n- `hart_burst_sample` — 主动采样 burst 发布的变量；`hart_burst_listen` — 被动监听非请求 burst publish（待核实 per 网关）\n\n### OPC-UA（只读；DCS/网关旁路读取）\n- `opcua_server_info` / `opcua_browse` / `opcua_read_node` / `opcua_read_many`\n- `opcua_subscribe_sample` `opcua_read_alarms` `opcua_alarm_events`(A&C 带时间戳) `opcua_read_history`(HDA)\n- `opcua_diagnose_connection` — 连接失败归因（证书/策略/认证/网络/配置）\n- `opcua_discover_tags` — 自动发现 + 语义资产建模\n- `opcua_health_summary` — tag vs 阈值分类；`opcua_anomaly_scan` — 有界统计异常扫描\n\n### Modbus-TCP / Modbus-RTU（只读；撬装/分析仪/RTU 从站）\n- `modbus_read_holding` `modbus_read_input` `modbus_read_coils` `modbus_read_discrete`\n- `modbus_detect_byte_order` — 字节/字序自动探测\n- `modbus_list_templates` / `modbus_apply_template` — 厂商寄存器模板 → 命名 tag\n- `modbus_health_summary` — 寄存器 vs 阈值分类\n\n### 流程专属（edition 工具;仅随 process edition 加载,不进全局脑）\n- `control_loop_health` — PID 回路诊断:从一段 PV/SP/OP 采样检出**振荡**(PV 反复穿越 SP)、\n **稳态偏差**(PV 长期偏离 SP)、**输出饱和**(OP 压在 0/100%)。给 verdict(saturated>oscillating>\n offset>ok)。非整定器,只分诊哪些回路要看。纯分析,每项引用数值。\n- `heat_exchanger_fouling` — **换热器结垢检测**:按四路温度算热侧温度效能 ε=(hot_in−hot_out)/\n (hot_in−cold_in),前后半窗对比;效能低于阈值或下降超阈即 fouling(结垢征兆,先于强制清洗)。\n 纯分析,喂 OPC-UA/Modbus/HART 温度点,verdict 引用效能数值。\n\n### 跨协议脑（永远随 server 暴露）\n- 诊断：`diagnose_dataflow` `downtime_root_cause` `downtime_root_cause_live` `downtime_triage`\n `learn_cause_weights` `rca_corpus_from_maintenance` `historian_health` `alarm_bad_actors` `tag_health`\n `subscription_health` `heartbeat_health` `alarm_flood_analysis` `alarm_cascade`\n `alarm_rationalization_worksheet`\n- 数据质量：`data_quality_scorecard` `data_quality_fleet_rollup`（流程工业重点：\n staleness / flatline / bad-quality —— 仪表坏数据绝不静默插值喂 AI）\n- 分析：`oee_compute` `downtime_events` `oee_multidim` `monitor_changes`\n `health_summary` (deprecated) `anomaly_scan` (deprecated)\n- 资产：`asset_inventory` `cross_protocol_asset_model` `adopt_alias_map` `diff_alias_map`\n- 基线：`baseline_learn` `baseline_check` `baseline_record_change` `baseline_status`\n （change-log 基线：拒学薄历史、只报持续越带、每次告警必引基线样本 —— 非黑盒异常检测）\n- 合规/信创：`compliance_mapping` `compliance_frameworks` `compliance_dengbao_levels`\n `compliance_report` `compliance_evidence_bundle`\n `historian_push` `export_data` `historian_query` `historian_coverage` `stream_publish` `stream_publish_event` `rca_narrate` `fleet_status` `fleet_incidents` `pdm_forecast`\n `historian_push` `export_data`\n- 程序解读：`plc_program_outline` `plc_program_xref` `plc_program_section` `plc_program_visibility`（解读导出的 ST/AWL/L5X 程序,只读文件,强制引用行号）\n- 元：`protocols_supported`\n\n## Workflows\n\n1. **Doctor-first**：`protocols_supported` → `iaiops doctor` → HART 先\n `hart_device_identity` 证明网关链路，OPC-UA 先 `opcua_diagnose_connection`。\n2. **Read-first**：仪表读 PV（`hart_primary_variable`）→ 动态变量 → burst；\n 回路异常/告警风暴用 `alarm_bad_actors`（ISA-18.2），\"没数据\"用 `diagnose_dataflow`。\n3. **MOC 写**：本 edition 三个协议的工具全部只读（无写表面）。若叠加 sparkplug，\n `mqtt_publish` 为 **[WRITE][HIGH][MOC]**：默认 `dry_run=True` + 改前状态 undo +\n `iaiops approve` 具名审批双确认。未经授权绝不写生产控制系统。\n\n## 支持版本矩阵（内部 HLD §8，设计文档不随本仓发布；`待核实` 不得当既成事实）\n\n| 协议 | 库(pin) | 规范/版本 | 覆盖 | 传输 | 自测 |\n|---|---|---|---|---|---|\n| HART-IP | `hart-protocol>=2023.6,<2025`（extra） | HART-IP（经网关） | 过程仪表：变送器/阀门定位器 | UDP/TCP 5094 | ⚠️ codec CI 自测；真机网关 待核实 |\n| OPC-UA | `asyncua>=1.0,<2` | OPC UA 1.0x（DA+HA+AC 子集） | 任意合规 Server / DCS 网关 | opc.tcp | ✅ mock+HDA |\n| Modbus-TCP | `pymodbus>=3.5,<4` | App 1.1b3；FC 1/2/3/4/5/6/15/16 | 任意 TCP 从站 | TCP/502 | ✅ |\n| Modbus-RTU | `pymodbus>=3.5,<4` + `pyserial>=3.5` | Modbus serial (RTU) | 串口从站 | RS-485/serial | ✅ socat PTY verified 2026-07-02；物理 RS-485 待核实 |\n\nFile v0.21.0:_meta.json\n\n{\n \"ownerId\": \"kn7b067awq2s97bn3d7p5qfhw5827pxc\",\n \"slug\": \"iaiops-process\",\n \"version\": \"0.21.0\",\n \"publishedAt\": 1785640061401\n}\n\nFile v0.21.0:skill-card.md\n\n## Description:
\nProcess-industry edition of iaiops for chemical, pharma, food and beverage, and oil and gas plants, covering HART-IP process instrumentation, OPC-UA DCS or gateway reads, Modbus-TCP/RTU devices, optional MQTT/Sparkplug B UNS workflows, and cross-protocol downtime, data-quality, and OEE analysis with read-first, MOC-gated writes.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[zw008](https://clawhub.ai/user/zw008)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and process-industry engineers use this skill to inspect HART-IP, OPC-UA, and Modbus plant data, triage dataflow and downtime issues, assess loop and exchanger health, and prepare controlled data publishing or historian workflows when appropriate.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill advertises data publishing and potentially write-capable operations in process-plant or connected OT environments.
\nMitigation: Review before installing in live plant environments; require explicit approval, dry-run behavior, and audit controls for historian push, export, stream publishing, MQTT, or other write-capable operations.
\nRisk: Modbus write function codes or other control writes could affect production systems if exposed by the runtime environment.
\nMitigation: Confirm Modbus write function codes are disabled or unavailable before deployment.
\n\n\n## Reference(s):
\n\n\n## Skill Output:
\n**Output Type(s):** [Analysis, Guidance, Shell commands, Configuration]
\n**Output Format:** [Markdown with inline commands and structured tool guidance]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Read-first operational guidance; write-capable publishing workflows require approval, dry-run, and audit controls.]
\n\n## Skill Version(s):
\n0.21.0 (source: server release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v0.20.4: 3 files, 5003 bytes\n\nFiles: skill-card.md (2303b), SKILL.md (6051b), _meta.json (134b)\n\nFile v0.20.4:SKILL.md\n\n---\nname: iaiops-process\ndescription: >-\n Process-industry edition of iaiops — chemical / pharma / food & beverage / oil &\n gas plants: HART-IP process instrumentation (transmitters, valve positioners,\n loop current), OPC-UA (DCS / gateway read), Modbus-TCP/RTU (skids, analyzers),\n optional MQTT/Sparkplug B UNS, plus the cross-protocol brain (downtime\n root-cause, data quality, OEE). Use when the task mentions HART, HART-IP,\n transmitter, 变送器, valve positioner, process instrumentation, PV/SV/TV/QV,\n loop current, burst mode, DCS tap, or a process plant. Read-first, MOC-gated\n writes.\n---\n\n# iaiops-process — 流程工业 edition（HART + Modbus + OPC-UA + 脑）\n\n启动：`IAIOPS_MCP=process` / `iaiops-mcp-process`（= opcua + modbus + hart + 脑）。\n现场有 UNS/Sparkplug 时用 `IAIOPS_MCP=process,sparkplug`（sparkplug 工具清单见\n**iaiops-factory** skill）。HART 需 extra：`pip install iaiops[hart]`。\n\n## 工具\n\n### HART-IP（只读；过程仪表 — 变送器、阀门定位器，经网关）\n`transport` 为 `udp`（默认）或 `tcp`，端口 5094。\n- `hart_device_identity` — 通用设备身份（command 0）\n- `hart_primary_variable` — 主变量 PV（command 1）：值 + 单位码\n- `hart_dynamic_variables` — 动态变量 PV/SV/TV/QV + 回路电流（command 3）\n- `hart_burst_sample` — 主动采样 burst 发布的变量；`hart_burst_listen` — 被动监听非请求 burst publish（待核实 per 网关）\n\n### OPC-UA（只读；DCS/网关旁路读取）\n- `opcua_server_info` / `opcua_browse` / `opcua_read_node` / `opcua_read_many`\n- `opcua_subscribe_sample` `opcua_read_alarms` `opcua_alarm_events`(A&C 带时间戳) `opcua_read_history`(HDA)\n- `opcua_diagnose_connection` — 连接失败归因（证书/策略/认证/网络/配置）\n- `opcua_discover_tags` — 自动发现 + 语义资产建模\n- `opcua_health_summary` — tag vs 阈值分类；`opcua_anomaly_scan` — 有界统计异常扫描\n\n### Modbus-TCP / Modbus-RTU（只读；撬装/分析仪/RTU 从站）\n- `modbus_read_holding` `modbus_read_input` `modbus_read_coils` `modbus_read_discrete`\n- `modbus_detect_byte_order` — 字节/字序自动探测\n- `modbus_list_templates` / `modbus_apply_template` — 厂商寄存器模板 → 命名 tag\n- `modbus_health_summary` — 寄存器 vs 阈值分类\n\n### 流程专属（edition 工具;仅随 process edition 加载,不进全局脑）\n- `control_loop_health` — PID 回路诊断:从一段 PV/SP/OP 采样检出**振荡**(PV 反复穿越 SP)、\n **稳态偏差**(PV 长期偏离 SP)、**输出饱和**(OP 压在 0/100%)。给 verdict(saturated>oscillating>\n offset>ok)。非整定器,只分诊哪些回路要看。纯分析,每项引用数值。\n- `heat_exchanger_fouling` — **换热器结垢检测**:按四路温度算热侧温度效能 ε=(hot_in−hot_out)/\n (hot_in−cold_in),前后半窗对比;效能低于阈值或下降超阈即 fouling(结垢征兆,先于强制清洗)。\n 纯分析,喂 OPC-UA/Modbus/HART 温度点,verdict 引用效能数值。\n\n### 跨协议脑（永远随 server 暴露）\n- 诊断：`diagnose_dataflow` `downtime_root_cause` `downtime_root_cause_live` `downtime_triage`\n `learn_cause_weights` `rca_corpus_from_maintenance` `historian_health` `alarm_bad_actors` `tag_health`\n `subscription_health` `heartbeat_health` `alarm_flood_analysis` `alarm_cascade`\n `alarm_rationalization_worksheet`\n- 数据质量：`data_quality_scorecard` `data_quality_fleet_rollup`（流程工业重点：\n staleness / flatline / bad-quality —— 仪表坏数据绝不静默插值喂 AI）\n- 分析：`oee_compute` `downtime_events` `oee_multidim` `monitor_changes`\n `health_summary` (deprecated) `anomaly_scan` (deprecated)\n- 资产：`asset_inventory` `cross_protocol_asset_model` `adopt_alias_map` `diff_alias_map`\n- 基线：`baseline_learn` `baseline_check` `baseline_record_change` `baseline_status`\n （change-log 基线：拒学薄历史、只报持续越带、每次告警必引基线样本 —— 非黑盒异常检测）\n- 合规/信创：`compliance_mapping` `compliance_frameworks` `compliance_dengbao_levels`\n `compliance_report` `compliance_evidence_bundle`\n `historian_push` `export_data` `historian_query` `historian_coverage` `stream_publish` `stream_publish_event` `rca_narrate` `fleet_status` `fleet_incidents` `pdm_forecast`\n `historian_push` `export_data`\n- 程序解读：`plc_program_outline` `plc_program_xref` `plc_program_section` `plc_program_visibility`（解读导出的 ST/AWL/L5X 程序,只读文件,强制引用行号）\n- 元：`protocols_supported`\n\n## Workflows\n\n1. **Doctor-first**：`protocols_supported` → `iaiops doctor` → HART 先\n `hart_device_identity` 证明网关链路，OPC-UA 先 `opcua_diagnose_connection`。\n2. **Read-first**：仪表读 PV（`hart_primary_variable`）→ 动态变量 → burst；\n 回路异常/告警风暴用 `alarm_bad_actors`（ISA-18.2），\"没数据\"用 `diagnose_dataflow`。\n3. **MOC 写**：本 edition 三个协议的工具全部只读（无写表面）。若叠加 sparkplug，\n `mqtt_publish` 为 **[WRITE][HIGH][MOC]**：默认 `dry_run=True` + 改前状态 undo +\n `iaiops approve` 具名审批双确认。未经授权绝不写生产控制系统。\n\n## 支持版本矩阵（内部 HLD §8，设计文档不随本仓发布；`待核实` 不得当既成事实）\n\n| 协议 | 库(pin) | 规范/版本 | 覆盖 | 传输 | 自测 |\n|---|---|---|---|---|---|\n| HART-IP | `hart-protocol>=2023.6,<2025`（extra） | HART-IP（经网关） | 过程仪表：变送器/阀门定位器 | UDP/TCP 5094 | ⚠️ codec CI 自测；真机网关 待核实 |\n| OPC-UA | `asyncua>=1.0,<2` | OPC UA 1.0x（DA+HA+AC 子集） | 任意合规 Server / DCS 网关 | opc.tcp | ✅ mock+HDA |\n| Modbus-TCP | `pymodbus>=3.5,<4` | App 1.1b3；FC 1/2/3/4/5/6/15/16 | 任意 TCP 从站 | TCP/502 | ✅ |\n| Modbus-RTU | `pymodbus>=3.5,<4` + `pyserial>=3.5` | Modbus serial (RTU) | 串口从站 | RS-485/serial | ✅ socat PTY verified 2026-07-02；物理 RS-485 待核实 |\n\nFile v0.20.4:_meta.json\n\n{\n \"ownerId\": \"kn7b067awq2s97bn3d7p5qfhw5827pxc\",\n \"slug\": \"iaiops-process\",\n \"version\": \"0.20.4\",\n \"publishedAt\": 1785630536822\n}\n\nFile v0.20.4:skill-card.md\n\n## Description:
\nProcess-industry edition of iaiops that guides agents through read-first HART-IP, OPC-UA, Modbus, optional Sparkplug UNS, and cross-protocol diagnostics for root cause, data quality, OEE, and process-equipment health.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[zw008](https://clawhub.ai/user/zw008)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers, plant engineers, and operations teams use this skill to guide read-first diagnostics across process-instrumentation protocols and process-plant workflows. It helps agents choose HART-IP, OPC-UA, Modbus, Sparkplug, data-quality, downtime, OEE, control-loop, and heat-exchanger diagnostic paths while preserving MOC-gated controls for writes.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: Write, publish, export, historian-write, and Modbus write-capability boundaries are unclear for an OT environment.
\nMitigation: Before live deployment, confirm that Modbus write function codes are not exposed and require explicit approval, dry-run behavior, environment scoping, and rollback controls for every push, export, publish, or historian write path.
\nRisk: Use in a live process environment could affect operational decisions if read-first and MOC-gated controls are bypassed.
\nMitigation: Keep process-control interactions read-first by default, restrict any write-capable extension to scoped environments, and require documented MOC approval before production use.
\n\n\n## Reference(s):
\n\n\n## Skill Output:
\n**Output Type(s):** [Guidance, Shell commands, Configuration, Analysis]
\n**Output Format:** [Markdown with inline tool names and shell commands]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Read-first operational guidance with MOC-gated write cautions for live process environments.]
\n\n## Skill Version(s):
\n0.20.4 (source: server release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v0.20.3: 3 files, 5060 bytes\n\nFiles: skill-card.md (2465b), SKILL.md (6051b), _meta.json (134b)\n\nFile v0.20.3:SKILL.md\n\n---\nname: iaiops-process\ndescription: >-\n Process-industry edition of iaiops — chemical / pharma / food & beverage / oil &\n gas plants: HART-IP process instrumentation (transmitters, valve positioners,\n loop current), OPC-UA (DCS / gateway read), Modbus-TCP/RTU (skids, analyzers),\n optional MQTT/Sparkplug B UNS, plus the cross-protocol brain (downtime\n root-cause, data quality, OEE). Use when the task mentions HART, HART-IP,\n transmitter, 变送器, valve positioner, process instrumentation, PV/SV/TV/QV,\n loop current, burst mode, DCS tap, or a process plant. Read-first, MOC-gated\n writes.\n---\n\n# iaiops-process — 流程工业 edition（HART + Modbus + OPC-UA + 脑）\n\n启动：`IAIOPS_MCP=process` / `iaiops-mcp-process`（= opcua + modbus + hart + 脑）。\n现场有 UNS/Sparkplug 时用 `IAIOPS_MCP=process,sparkplug`（sparkplug 工具清单见\n**iaiops-factory** skill）。HART 需 extra：`pip install iaiops[hart]`。\n\n## 工具\n\n### HART-IP（只读；过程仪表 — 变送器、阀门定位器，经网关）\n`transport` 为 `udp`（默认）或 `tcp`，端口 5094。\n- `hart_device_identity` — 通用设备身份（command 0）\n- `hart_primary_variable` — 主变量 PV（command 1）：值 + 单位码\n- `hart_dynamic_variables` — 动态变量 PV/SV/TV/QV + 回路电流（command 3）\n- `hart_burst_sample` — 主动采样 burst 发布的变量；`hart_burst_listen` — 被动监听非请求 burst publish（待核实 per 网关）\n\n### OPC-UA（只读；DCS/网关旁路读取）\n- `opcua_server_info` / `opcua_browse` / `opcua_read_node` / `opcua_read_many`\n- `opcua_subscribe_sample` `opcua_read_alarms` `opcua_alarm_events`(A&C 带时间戳) `opcua_read_history`(HDA)\n- `opcua_diagnose_connection` — 连接失败归因（证书/策略/认证/网络/配置）\n- `opcua_discover_tags` — 自动发现 + 语义资产建模\n- `opcua_health_summary` — tag vs 阈值分类；`opcua_anomaly_scan` — 有界统计异常扫描\n\n### Modbus-TCP / Modbus-RTU（只读；撬装/分析仪/RTU 从站）\n- `modbus_read_holding` `modbus_read_input` `modbus_read_coils` `modbus_read_discrete`\n- `modbus_detect_byte_order` — 字节/字序自动探测\n- `modbus_list_templates` / `modbus_apply_template` — 厂商寄存器模板 → 命名 tag\n- `modbus_health_summary` — 寄存器 vs 阈值分类\n\n### 流程专属（edition 工具;仅随 process edition 加载,不进全局脑）\n- `control_loop_health` — PID 回路诊断:从一段 PV/SP/OP 采样检出**振荡**(PV 反复穿越 SP)、\n **稳态偏差**(PV 长期偏离 SP)、**输出饱和**(OP 压在 0/100%)。给 verdict(saturated>oscillating>\n offset>ok)。非整定器,只分诊哪些回路要看。纯分析,每项引用数值。\n- `heat_exchanger_fouling` — **换热器结垢检测**:按四路温度算热侧温度效能 ε=(hot_in−hot_out)/\n (hot_in−cold_in),前后半窗对比;效能低于阈值或下降超阈即 fouling(结垢征兆,先于强制清洗)。\n 纯分析,喂 OPC-UA/Modbus/HART 温度点,verdict 引用效能数值。\n\n### 跨协议脑（永远随 server 暴露）\n- 诊断：`diagnose_dataflow` `downtime_root_cause` `downtime_root_cause_live` `downtime_triage`\n `learn_cause_weights` `rca_corpus_from_maintenance` `historian_health` `alarm_bad_actors` `tag_health`\n `subscription_health` `heartbeat_health` `alarm_flood_analysis` `alarm_cascade`\n `alarm_rationalization_worksheet`\n- 数据质量：`data_quality_scorecard` `data_quality_fleet_rollup`（流程工业重点：\n staleness / flatline / bad-quality —— 仪表坏数据绝不静默插值喂 AI）\n- 分析：`oee_compute` `downtime_events` `oee_multidim` `monitor_changes`\n `health_summary` (deprecated) `anomaly_scan` (deprecated)\n- 资产：`asset_inventory` `cross_protocol_asset_model` `adopt_alias_map` `diff_alias_map`\n- 基线：`baseline_learn` `baseline_check` `baseline_record_change` `baseline_status`\n （change-log 基线：拒学薄历史、只报持续越带、每次告警必引基线样本 —— 非黑盒异常检测）\n- 合规/信创：`compliance_mapping` `compliance_frameworks` `compliance_dengbao_levels`\n `compliance_report` `compliance_evidence_bundle`\n `historian_push` `export_data` `historian_query` `historian_coverage` `stream_publish` `stream_publish_event` `rca_narrate` `fleet_status` `fleet_incidents` `pdm_forecast`\n `historian_push` `export_data`\n- 程序解读：`plc_program_outline` `plc_program_xref` `plc_program_section` `plc_program_visibility`（解读导出的 ST/AWL/L5X 程序,只读文件,强制引用行号）\n- 元：`protocols_supported`\n\n## Workflows\n\n1. **Doctor-first**：`protocols_supported` → `iaiops doctor` → HART 先\n `hart_device_identity` 证明网关链路，OPC-UA 先 `opcua_diagnose_connection`。\n2. **Read-first**：仪表读 PV（`hart_primary_variable`）→ 动态变量 → burst；\n 回路异常/告警风暴用 `alarm_bad_actors`（ISA-18.2），\"没数据\"用 `diagnose_dataflow`。\n3. **MOC 写**：本 edition 三个协议的工具全部只读（无写表面）。若叠加 sparkplug，\n `mqtt_publish` 为 **[WRITE][HIGH][MOC]**：默认 `dry_run=True` + 改前状态 undo +\n `iaiops approve` 具名审批双确认。未经授权绝不写生产控制系统。\n\n## 支持版本矩阵（内部 HLD §8，设计文档不随本仓发布；`待核实` 不得当既成事实）\n\n| 协议 | 库(pin) | 规范/版本 | 覆盖 | 传输 | 自测 |\n|---|---|---|---|---|---|\n| HART-IP | `hart-protocol>=2023.6,<2025`（extra） | HART-IP（经网关） | 过程仪表：变送器/阀门定位器 | UDP/TCP 5094 | ⚠️ codec CI 自测；真机网关 待核实 |\n| OPC-UA | `asyncua>=1.0,<2` | OPC UA 1.0x（DA+HA+AC 子集） | 任意合规 Server / DCS 网关 | opc.tcp | ✅ mock+HDA |\n| Modbus-TCP | `pymodbus>=3.5,<4` | App 1.1b3；FC 1/2/3/4/5/6/15/16 | 任意 TCP 从站 | TCP/502 | ✅ |\n| Modbus-RTU | `pymodbus>=3.5,<4` + `pyserial>=3.5` | Modbus serial (RTU) | 串口从站 | RS-485/serial | ✅ socat PTY verified 2026-07-02；物理 RS-485 待核实 |\n\nFile v0.20.3:_meta.json\n\n{\n \"ownerId\": \"kn7b067awq2s97bn3d7p5qfhw5827pxc\",\n \"slug\": \"iaiops-process\",\n \"version\": \"0.20.3\",\n \"publishedAt\": 1785558759937\n}\n\nFile v0.20.3:skill-card.md\n\n## Description:
\nProcess-industry edition of iaiops for chemical, pharma, food and beverage, and oil and gas plants; it guides agents through read-first diagnostics across HART-IP instruments, OPC-UA, Modbus TCP/RTU, optional MQTT/Sparkplug B, downtime root-cause analysis, data quality, and OEE.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[zw008](https://clawhub.ai/user/zw008)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers, process engineers, and plant operations teams use this skill to guide read-first diagnostics for process instrumentation, control-loop health, data quality, downtime root cause, historian coverage, and compliance evidence workflows. It is intended for process plants using HART-IP, OPC-UA, Modbus TCP/RTU, and optionally MQTT/Sparkplug B.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: Export and publishing tools may move plant data or publish events without sufficiently explicit scoping.
\nMitigation: Require destination allowlists, explicit approvals, and audit logging before enabling historian_push, export_data, stream_publish, or stream_publish_event near real plant data.
\nRisk: Use in production or sensitive plant environments may exceed the security posture described by the release evidence.
\nMitigation: Review the skill before installation and enforce read-first operation plus management-of-change controls for any write-capable integration.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/zw008/skills/iaiops-process)
\n- [Publisher profile](https://clawhub.ai/user/zw008)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]
\n**Output Format:** [Markdown and structured guidance with inline commands and tool names]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Guidance emphasizes read-first diagnostics, cited values, approval gates for write-capable integrations, and plant-data export restrictions.]
\n\n## Skill Version(s):
\n0.20.3 (source: server release evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
","readmeExcerpt":"Skill: iaiops-process Owner: zw008 Summary: Process-industry edition of iaiops — chemical / pharma / food & beverage / oil & gas plants: HART-IP process instrumentation (transmitters, valve positioners, loop current), OPC-UA (DCS / gateway read), Modbus-TCP/RTU (skids, analyzers), optional MQTT/Sparkplug B UNS, plus the cross-protocol brain (downtime root-cause, data quality, OEE). Use when the task mentions HART, HA","codeSnippets":[],"executableExamples":[],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: iaiops-process\ndescription: >-\n Process-industry edition of iaiops — chemical / pharma / food & beverage / oil &\n gas plants: HART-IP process instrumentation (transmitters, valve positioners,\n loop current), OPC-UA (DCS / gateway read), Modbus-TCP/RTU (skids, analyzers),\n optional MQTT/Sparkplug B UNS, plus the cross-protocol brain (downtime\n root-cause, data quality, OEE). Use when the task mentions HART, HART-IP,\n transmitter, 变送器, valve positioner, process instrumentation, PV/SV/TV/QV,\n loop current, burst mode, DCS tap, or a process plant. Read-first, MOC-gated\n writes.\n---\n\n# iaiops-process — 流程工业 edition（HART + Modbus + OPC-UA + 脑）\n\n启动：`IAIOPS_MCP=process` / `iaiops-mcp-process`（= opcua + modbus + hart + 脑）。\n现场有 UNS/Sparkplug 时用 `IAIOPS_MCP=process,sparkplug`（sparkplug 工具清单见\n**iaiops-factory** skill）。HART 需 extra：`pip install iaiops[hart]`。\n\n## 工具\n\n### HART-IP（只读；过程仪表 — 变送器、阀门定位器，经网关）\n`transport` 为 `udp`（默认）或 `tcp`，端口 5094。\n- `hart_device_identity` — 通用设备身份（command 0）\n- `hart_primary_variable` — 主变量 PV（command 1）：值 + 单位码\n- `hart_dynamic_variables` — 动态变量 PV/SV/TV/QV + 回路电流（command 3）\n- `hart_burst_sample` — 主动采样 burst 发布的变量；`hart_burst_listen` — 被动监听非请求 burst publish（待核实 per 网关）\n\n### OPC-UA（只读；DCS/网关旁路读取）\n- `opcua_server_info` / `opcua_browse` / `opcua_read_node` / `opcua_read_many`\n- `opcua_subscribe_sample` `opcua_read_alarms` `opcua_alarm_events`(A&C 带时间戳) `opcua_read_history`(HDA)\n- `opcua_diagnose_connection` — 连接失败归因（证书/策略/认证/网络/配置）\n- `opcua_discover_tags` — 自动发现 + 语义资产建模\n- `opcua_health_summary` — tag vs 阈值分类；`opcua_anomaly_scan` — 有界统计异常扫描\n\n### Modbus-TCP / Modbus-RTU（只读；撬装/分析仪/RTU 从站）\n- `modbus_read_holding` `modbus_read_input` `modbus_read_coils` `modbus_read_discrete`\n- `modbus_detect_byte_order` — 字节/字序自动探测\n- `modbus_list_templates` / `modbus_apply_template` — 厂商寄存器模板 → 命名 tag\n- `modbus_health_summary` — 寄存器 vs 阈值分类\n\n### 流程专属（edition 工具;仅随 process edition 加载,不进全局脑）\n- `control_loop_health` — PID 回路诊断:从一段 PV/SP/OP 采样检出**振荡**(PV 反复穿越 SP)、\n **稳态偏差**(PV 长期偏离 SP)、**输出饱和**(OP 压在 0/100%)。给 verdict(saturated>oscillating>\n offset>ok)。非整定器,只分诊哪些回路要看。纯分析,每项引用数值。\n- `heat_exchanger_fouling` — **换热器结垢检测**:按四路温度算热侧温度效能 ε=(hot_in−hot_out)/\n (hot_in−cold_in),前后半窗对比;效能低于阈值或下降超阈即 fouling(结垢征兆,先于强制清洗)。\n 纯分析,喂 OPC-UA/Modbus/HART 温度点,verdict 引用效能数值。\n\n### 跨协议脑（永远随 server 暴露）\n- 诊断：`diagnose_dataflow` `downtime_root_cause` `downtime_root_cause_live` `downtime_triage`\n `learn_cause_weights` `rca_corpus_from_maintenance` `historian_health` `alarm_bad_actors` `tag_health`\n `subscription_health` `heartbeat_health` `alarm_flood_analysis` `alarm_cascade`\n `alarm_rationalization_worksheet`\n- 告警事件聚类：`alarm_event_clusters` — `alarm_bad_actors` 按**来源**排名,回答的是「哪台仪表最吵」,\n 不是「哪个故障最吵」;一个把同一条件写成十种说法的厂会得到十个 bad actor。这个按事件**说了什么**分组。\n 合并规则是**去掉大小写/标点/数字后的精确相等,不是相似度** —— 故意做笨,所以不需要模型、且可核对;\n 每个簇都列出被合并的原文与来源。**它不主张两条措辞不同的告警是同一个故障**,那由人判断。\n- 数据质量：`data_quality_scorecard` `data_quality_fleet_rollup`（流程工业重点：\n staleness / flatline / bad-quality —— 仪"},{"path":"_meta.json","content":"{\n \"ownerId\": \"kn7b067awq2s97bn3d7p5qfhw5827pxc\",\n \"slug\": \"iaiops-process\",\n \"version\": \"0.28.0\",\n \"publishedAt\": 1789535352230\n}"},{"path":"skill-card.md","content":"## Description:\n\nProcess-industry edition of iaiops for chemical, pharma, food and beverage, and oil and gas plants, helping agents read HART-IP, OPC-UA, Modbus, and optional MQTT/Sparkplug B UNS signals for process instrumentation, downtime root-cause analysis, data quality, and OEE with a read-first, MOC-gated posture.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[zw008](https://clawhub.ai/user/zw008)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and process engineers use this skill to guide agents through process plant data collection and analysis across HART-IP, OPC-UA, Modbus, and optional UNS/Sparkplug workflows. It supports loop health, heat exchanger fouling checks, alarm and data quality analysis, OEE, downtime triage, asset modeling, investigation workflows, and configuration drafting.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: High-impact historian, export, stream publish, or UNS publish operations may affect operational data if enabled without clear approval gates.\n\nMitigation: Confirm the enabled toolset and require explicit human approval before any operation that exports, publishes, or writes operational data.\n\nRisk: Production plant installation may carry elevated operational risk because the scanner classified the release as suspicious.\n\nMitigation: Review the skill before production use and install dependencies only in a contained environment with pinned, verified packages.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/zw008/skills/iaiops-process)\n- [Publisher profile](https://clawhub.ai/user/zw008)\n\n## Skill Output:\n\n**Output Type(s):** [Guidance, Shell commands, Configuration, Markdown, Code]\n\n**Output Format:** [Markdown guidance with tool names, command snippets, configuration drafts, and structured analysis summaries]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May propose historian, export, stream publish, or UNS publish operations; production-impacting actions require review and explicit approval gates.]\n\n## Skill Version(s):\n\n0.28.0 (source: server release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"Process-industry edition of iaiops — chemical / pharma / food & beverage / oil & gas plants: HART-IP process instrumentation (transmitters, valve positioners, loop current), OPC-UA (DCS / gateway read), Modbus-TCP/RTU (skids, analyzers), optional MQTT/Sparkplug B UNS, plus the cross-protocol brain (downtime root-cause, data quality, OEE). Use when the task mentions HART, HART-IP, transmitter, 变送器, valve positioner, process instrumentation, PV/SV/TV/QV, loop current, burst mode, DCS tap, or a process plant. Read-first, MOC-gated writes. Skill: iaiops-process Owner: zw008 Summary: Process-industry edition of iaiops — chemical / pharma / food & beverage / oil & gas plants: HART-IP process instrumentation (transmitters, valve positioners, loop current), OPC-UA (DCS / gateway read), Modbus-TCP/RTU (skids, analyzers), optional MQTT/Sparkplug B UNS, plus the cross-protocol brain (downtime root-cause, data quality, OEE). Use when the task mentions HART, HA","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":1266,"uniquenessScore":51,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-10T03:01:54.687Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-10T03:01:54.687Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-10T07:40:37.684Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}