{"id":"be606283-9152-4a2b-9264-3c0d78b18653","entityType":"agent","slug":"clawhub-zw008-iaiops-plcnext","name":"iaiops-plcnext","canonicalUrl":"https://www.xpersona.co/agent/clawhub-zw008-iaiops-plcnext","canonicalPath":"/agent/clawhub-zw008-iaiops-plcnext","generatedAt":"2026-10-10T07:42:13.313Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-10T03:06:09.496Z","emptyReason":null},"description":"PLCnext / virtualized-PLC edition of iaiops — Phoenix Contact PLCnext Control and vPLC (虚拟化 PLC) reached over its built-in OPC-UA server (opc.tcp 4840) and Modbus-TCP process-data server, plus the cross-protocol brain (dataflow diagnosis, downtime root cause, PdM, OEE, alarm, baseline). A packaging edition — no new connector, no PLCnext-vendor SDK: it routes to the standard OPC-UA and Modbus tools already shipped. Use when the task mentions PLCnext / PLCnext Control / AXC F / vPLC / virtual PLC / 虚拟 PLC / Phoenix Contact controller over OPC-UA or Modbus. Read-first; this edition's tool surface is read-only. Skill: iaiops-plcnext Owner: zw008 Summary: PLCnext / virtualized-PLC edition of iaiops — Phoenix Contact PLCnext Control and vPLC (虚拟化 PLC) reached over its built-in OPC-UA server (opc.tcp 4840) and Modbus-TCP process-data server, plus the cross-protocol brain (dataflow diagnosis, downtime root cause, PdM, OEE, alarm, baseline). A packaging edition — no new connector, no PLCnext-vendor SDK: it routes to the standard","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1.7K downloads reported by the source. Last updated 10/10/2026.","installCommand":"clawhub skill install s171xgnmqse0nqvgqvqnaq5f9183kyre:iaiops-plcnext","sourceUrl":"https://clawhub.ai/zw008/iaiops-plcnext","homepage":"https://clawhub.ai/zw008/skills/iaiops-plcnext","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/zw008/iaiops-plcnext","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/zw008/skills/iaiops-plcnext","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":65,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"PLCnext / virtualized-PLC edition of iaiops — Phoenix Contact PLCnext Control and vPLC (虚拟化 PLC) reached over its built-in OPC-UA server (opc.tcp 4840) and Modb"},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-10T03:06:09.496Z","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:06:09.496Z","emptyReason":null},"stars":null,"forks":null,"downloads":1748,"packageName":null,"latestVersion":"0.28.0","tractionLabel":"1.7K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-10T03:06:09.326Z","emptyReason":null},"lastUpdatedAt":"2026-10-10T03:06:09.496Z","lastCrawledAt":"2026-10-10T03:06:09.326Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-11T03:06:09.326Z","lastVerifiedAt":null,"highlights":[{"version":"0.28.0","createdAt":"2026-09-16T05:10:04.966Z","changelog":"0.28.0: MQTT/Sparkplug collectable; onboard's two journeys (devices / uns with a B1/B2 namespace fork)","fileCount":3,"zipByteSize":6848},{"version":"0.27.0","createdAt":"2026-09-03T03:20:17.359Z","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":6560},{"version":"0.26.0","createdAt":"2026-09-01T12:29:16.587Z","changelog":"verify determinism (executed model-free claim) · PLC program change baseline · pharma edition","fileCount":3,"zipByteSize":5283},{"version":"0.23.1","createdAt":"2026-08-28T05:19:05.940Z","changelog":"- Expanded the \"跨协议脑\" (cross-protocol brain) tooling to include new meta and investigation features, as well as production line relationship and mechanism library functions. - Added tools: `site_readiness`, `investigation_readiness`, `investigation_open`, `investigation_show`, `investigation_list`, `line_relation_declare`, `line_relations_list`, `mechanism_library_check`, and `mechanism_library_list`. - Enhanced documentation with clarification on the new investigation and production line mechanisms, highlighting workflow and reasoning scope. - Removed the skill-card.md file.","fileCount":3,"zipByteSize":4413},{"version":"0.23.0","createdAt":"2026-08-25T04:33:23.420Z","changelog":"iaiops-plcnext v0.23.0 - Added `uns_publish` to the toolset for cross-protocol workflows. - Removed the redundant skill-card.md file. - SKILL.md updated to reflect toolset changes.","fileCount":3,"zipByteSize":3775},{"version":"0.22.0","createdAt":"2026-08-02T13:09:19.183Z","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":3998},{"version":"0.21.1","createdAt":"2026-08-02T07:24:54.255Z","changelog":"0.21.1 — review round two: RCA window dilution, IoTDB header names, OPC-UA malformed-URL leak","fileCount":3,"zipByteSize":3909},{"version":"0.21.0","createdAt":"2026-08-02T03:07:35.059Z","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":3793}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s171xgnmqse0nqvgqvqnaq5f9183kyre:iaiops-plcnext","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-plcnext/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-zw008-iaiops-plcnext/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-zw008-iaiops-plcnext/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-zw008-iaiops-plcnext/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-zw008-iaiops-plcnext/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-zw008-iaiops-plcnext/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:42:13.312Z"}},"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-plcnext/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-zw008-iaiops-plcnext/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-zw008-iaiops-plcnext/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-zw008-iaiops-plcnext/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:06:09.496Z","emptyReason":null},"readme":"Skill: iaiops-plcnext\n\nOwner: zw008\n\nSummary: PLCnext / virtualized-PLC edition of iaiops — Phoenix Contact PLCnext Control and vPLC (虚拟化 PLC) reached over its built-in OPC-UA server (opc.tcp 4840) and Modbus-TCP process-data server, plus the cross-protocol brain (dataflow diagnosis, downtime root cause, PdM, OEE, alarm, baseline). A packaging edition — no new connector, no PLCnext-vendor SDK: it routes to the standard OPC-UA and Modbus tools already shipped. Use when the task mentions PLCnext / PLCnext Control / AXC F / vPLC / virtual PLC / 虚拟 PLC / Phoenix Contact controller over OPC-UA or Modbus. Read-first; this edition's tool surface is read-only.\n\nTags: latest:0.28.0\n\nVersion history:\n\nv0.28.0 | 2026-09-16T05:10:04.966Z | 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:17.359Z | 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:16.587Z | user\n\nverify determinism (executed model-free claim) · PLC program change baseline · pharma edition\n\nv0.23.1 | 2026-08-28T05:19:05.940Z | auto\n\n- Expanded the \"跨协议脑\" (cross-protocol brain) tooling to include new meta and investigation features, as well as production line relationship and mechanism library functions.\n- Added tools: `site_readiness`, `investigation_readiness`, `investigation_open`, `investigation_show`, `investigation_list`, `line_relation_declare`, `line_relations_list`, `mechanism_library_check`, and `mechanism_library_list`.\n- Enhanced documentation with clarification on the new investigation and production line mechanisms, highlighting workflow and reasoning scope.\n- Removed the skill-card.md file.\n\nv0.23.0 | 2026-08-25T04:33:23.420Z | auto\n\niaiops-plcnext v0.23.0\n\n- Added `uns_publish` to the toolset for cross-protocol workflows.\n- Removed the redundant skill-card.md file.\n- SKILL.md updated to reflect toolset changes.\n\nv0.22.0 | 2026-08-02T13:09:19.183Z | 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:24:54.255Z | 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:35.059Z | 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:50.203Z | 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:29.797Z | 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:21.532Z | user\n\ncredential redaction in audit log; retained mqtt_publish undo; pyopenssl resolver guard\n\nv0.20.1 | 2026-07-29T09:37:53.447Z | user\n\niaiops 0.20.1 — MCP tool annotations derived from the governance harness\n\nv0.19.0 | 2026-07-21T14:36:58.015Z | 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:14:39.754Z | auto\n\n- Removed the skill-card.md file.  \n- No other functional or user-facing changes in this version.\n\nv0.18.0 | 2026-07-19T11:31:07.289Z | auto\n\n- Removed the file: skill-card.md.\n- No other user facing changes.\n\nv0.17.0 | 2026-07-19T09:23:18.509Z | auto\n\niaiops-plcnext 0.17.0\n\n- Added `opcua_alarm_events` (A&C 带时间戳) to OPC-UA tools.\n- Added `rca_corpus_from_maintenance` to diagnostic tools.\n- Revised protocol/version support matrix note to clarify that design docs are not published in this repository.\n- Removed deprecated documentation file `skill-card.md`.\n- Made minor clarifications and cleanups in tool and workflow documentation.\n\nv0.12.0 | 2026-07-13T01:09:27.109Z | 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, 6848 bytes\n\nFiles: skill-card.md (2497b), SKILL.md (9289b), _meta.json (134b)\n\nFile v0.28.0:SKILL.md\n\n---\nname: iaiops-plcnext\ndescription: >-\n  PLCnext / virtualized-PLC edition of iaiops — Phoenix Contact PLCnext Control\n  and vPLC (虚拟化 PLC) reached over its built-in OPC-UA server (opc.tcp 4840) and\n  Modbus-TCP process-data server, plus the cross-protocol brain (dataflow\n  diagnosis, downtime root cause, PdM, OEE, alarm, baseline). A packaging edition\n  — no new connector, no PLCnext-vendor SDK: it routes to the standard OPC-UA and\n  Modbus tools already shipped. Use when the task mentions PLCnext / PLCnext\n  Control / AXC F / vPLC / virtual PLC / 虚拟 PLC / Phoenix Contact controller over\n  OPC-UA or Modbus. Read-first; this edition's tool surface is read-only.\n---\n\n# iaiops-plcnext — PLCnext / vPLC edition（OPC-UA + Modbus + 脑）\n\n启动：`IAIOPS_MCP=plcnext` / `iaiops-mcp-plcnext`（= opcua + modbus + 脑;等价\n`IAIOPS_MCP=opcua,modbus`）。**打包型 edition**:PLCnext Control / vPLC 通过其**内置\nOPC-UA server**(opc.tcp 4840)与 **Modbus-TCP 过程数据 server** 读取 —— 不新增 connector、\n不依赖 PLCnext 厂商 SDK,直接复用已发布的标准 OPC-UA / Modbus 工具 + 跨协议脑。\n\n## 工具\n\n### OPC-UA（只读;PLCnext 内置 OPC-UA server,opc.tcp 4840）\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` — 自动发现 + 语义资产建模;`opcua_health_summary` 阈值分类;\n  `opcua_anomaly_scan` 有界统计异常扫描\n\n### Modbus-TCP（只读;PLCnext 过程数据 server）\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### 跨协议脑（永远随 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- 预测维护：`pdm_forecast`\n- 告警事件聚类：`alarm_event_clusters` — `alarm_bad_actors` 按**来源**排名,回答的是「哪台仪表最吵」,\n  不是「哪个故障最吵」;一个把同一条件写成十种说法的厂会得到十个 bad actor。这个按事件**说了什么**分组。\n  合并规则是**去掉大小写/标点/数字后的精确相等,不是相似度** —— 故意做笨,所以不需要模型、且可核对;\n  每个簇都列出被合并的原文与来源。**它不主张两条措辞不同的告警是同一个故障**,那由人判断。\n- 数据质量：`data_quality_scorecard` `data_quality_fleet_rollup`\n- 分析：`oee_compute` `downtime_events` `oee_multidim` `monitor_changes`\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- 合规/信创：`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`\n  `stream_publish_event` `rca_narrate` `fleet_status` `fleet_incidents`\n- 程序解读：`plc_program_outline` `plc_program_xref` `plc_program_section` `plc_program_visibility`\n  （解读导出的 ST/AWL/L5X;PLCnext 工程可导出 IEC 61131 ST 文本后离线解读）\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` → `opcua_diagnose_connection`\n   (先确认 PLCnext 内置 OPC-UA server 4840 可达、证书/策略匹配)。\n2. **Read-first**：过程量走 OPC-UA `opcua_read_many` / Modbus `modbus_read_holding`;\n   \"没数据\"用 `diagnose_dataflow`,停机用 `downtime_triage` / `downtime_root_cause_live`。\n3. **只读**:本 edition 工具表面全只读。若需写(输出/设定值),切到含写工具的 profile 并走统一\n   MOC:`risk=HIGH` + 默认 `dry_run=True` + 改前值 undo + `iaiops approve` 具名审批双确认。\n\n## 支持版本矩阵（内部 HLD §8，设计文档不随本仓发布;`待核实` 不得当既成事实）\n\n| 协议 | 库(pin) | 规范/版本 | 覆盖 | 传输 | 自测 |\n|---|---|---|---|---|---|\n| OPC-UA | `asyncua>=2.0,<3` | OPC UA 1.0x（DA+HA+AC 子集） | PLCnext 内置 OPC-UA server | opc.tcp/4840 | ✅ mock+HDA;真 PLCnext 待核实 |\n| Modbus-TCP | `pymodbus>=3.5,<4` | App 1.1b3;FC 1/2/3/4/5/6/15/16 | PLCnext 过程数据 server | TCP/502 | ✅;真 PLCnext 待核实 |\n\nFile v0.28.0:_meta.json\n\n{\n  \"ownerId\": \"kn7b067awq2s97bn3d7p5qfhw5827pxc\",\n  \"slug\": \"iaiops-plcnext\",\n  \"version\": \"0.28.0\",\n  \"publishedAt\": 1789535404966\n}\n\nFile v0.28.0:skill-card.md\n\n## Description:\n\niaiops-plcnext helps agents operate a read-first PLCnext and vPLC monitoring workflow over OPC-UA and Modbus-TCP, with diagnostics, downtime root-cause analysis, PdM, OEE, alarms, baselines, data quality, onboarding, and investigation guidance.\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 industrial engineers use this skill to diagnose, monitor, and analyze Phoenix Contact PLCnext Control and vPLC environments through OPC-UA and Modbus-TCP without adding a PLCnext-specific connector. It supports read-first OT observability, onboarding, root-cause analysis, data-quality, compliance-evidence, and baseline workflows.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill is framed as read-only, but the evidence security summary notes documented export, publish, historian-push, UNS, baseline-persistence, and history functions.\n\nMitigation: Review before production OT installation and require explicit approval, verified destinations, least-privilege credentials, and data-classification checks before using export, publish, historian-push, UNS, baseline, or history functions.\n\nRisk: Using the skill in production OT environments can affect sensitive process data flows even when PLC process access is read-only.\n\nMitigation: Treat PLC process access as read-only, verify all external data destinations, and apply site change-control and approval processes for any workflow that persists, exports, publishes, or pushes data.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/zw008/skills/iaiops-plcnext)\n- [Artifact SKILL.md](artifact/SKILL.md)\n\n## Skill Output:\n\n**Output Type(s):** [guidance, markdown, shell commands, configuration, analysis]\n\n**Output Format:** [Markdown guidance with inline commands, tool names, and configuration snippets]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May produce reports, scorecards, evidence bundles, and configuration drafts for read-first PLCnext/vPLC workflows over OPC-UA and Modbus-TCP.]\n\n## Skill Version(s):\n\n0.28.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.27.0: 3 files, 6560 bytes\n\nFiles: skill-card.md (2406b), SKILL.md (8832b), _meta.json (134b)\n\nFile v0.27.0:SKILL.md\n\n---\nname: iaiops-plcnext\ndescription: >-\n  PLCnext / virtualized-PLC edition of iaiops — Phoenix Contact PLCnext Control\n  and vPLC (虚拟化 PLC) reached over its built-in OPC-UA server (opc.tcp 4840) and\n  Modbus-TCP process-data server, plus the cross-protocol brain (dataflow\n  diagnosis, downtime root cause, PdM, OEE, alarm, baseline). A packaging edition\n  — no new connector, no PLCnext-vendor SDK: it routes to the standard OPC-UA and\n  Modbus tools already shipped. Use when the task mentions PLCnext / PLCnext\n  Control / AXC F / vPLC / virtual PLC / 虚拟 PLC / Phoenix Contact controller over\n  OPC-UA or Modbus. Read-first; this edition's tool surface is read-only.\n---\n\n# iaiops-plcnext — PLCnext / vPLC edition（OPC-UA + Modbus + 脑）\n\n启动：`IAIOPS_MCP=plcnext` / `iaiops-mcp-plcnext`（= opcua + modbus + 脑;等价\n`IAIOPS_MCP=opcua,modbus`）。**打包型 edition**:PLCnext Control / vPLC 通过其**内置\nOPC-UA server**(opc.tcp 4840)与 **Modbus-TCP 过程数据 server** 读取 —— 不新增 connector、\n不依赖 PLCnext 厂商 SDK,直接复用已发布的标准 OPC-UA / Modbus 工具 + 跨协议脑。\n\n## 工具\n\n### OPC-UA（只读;PLCnext 内置 OPC-UA server,opc.tcp 4840）\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` — 自动发现 + 语义资产建模;`opcua_health_summary` 阈值分类;\n  `opcua_anomaly_scan` 有界统计异常扫描\n\n### Modbus-TCP（只读;PLCnext 过程数据 server）\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### 跨协议脑（永远随 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- 预测维护：`pdm_forecast`\n- 告警事件聚类：`alarm_event_clusters` — `alarm_bad_actors` 按**来源**排名,回答的是「哪台仪表最吵」,\n  不是「哪个故障最吵」;一个把同一条件写成十种说法的厂会得到十个 bad actor。这个按事件**说了什么**分组。\n  合并规则是**去掉大小写/标点/数字后的精确相等,不是相似度** —— 故意做笨,所以不需要模型、且可核对;\n  每个簇都列出被合并的原文与来源。**它不主张两条措辞不同的告警是同一个故障**,那由人判断。\n- 数据质量：`data_quality_scorecard` `data_quality_fleet_rollup`\n- 分析：`oee_compute` `downtime_events` `oee_multidim` `monitor_changes`\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- 合规/信创：`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`\n  `stream_publish_event` `rca_narrate` `fleet_status` `fleet_incidents`\n- 程序解读：`plc_program_outline` `plc_program_xref` `plc_program_section` `plc_program_visibility`\n  （解读导出的 ST/AWL/L5X;PLCnext 工程可导出 IEC 61131 ST 文本后离线解读）\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` → `opcua_diagnose_connection`\n   (先确认 PLCnext 内置 OPC-UA server 4840 可达、证书/策略匹配)。\n2. **Read-first**：过程量走 OPC-UA `opcua_read_many` / Modbus `modbus_read_holding`;\n   \"没数据\"用 `diagnose_dataflow`,停机用 `downtime_triage` / `downtime_root_cause_live`。\n3. **只读**:本 edition 工具表面全只读。若需写(输出/设定值),切到含写工具的 profile 并走统一\n   MOC:`risk=HIGH` + 默认 `dry_run=True` + 改前值 undo + `iaiops approve` 具名审批双确认。\n\n## 支持版本矩阵（内部 HLD §8，设计文档不随本仓发布;`待核实` 不得当既成事实）\n\n| 协议 | 库(pin) | 规范/版本 | 覆盖 | 传输 | 自测 |\n|---|---|---|---|---|---|\n| OPC-UA | `asyncua>=2.0,<3` | OPC UA 1.0x（DA+HA+AC 子集） | PLCnext 内置 OPC-UA server | opc.tcp/4840 | ✅ mock+HDA;真 PLCnext 待核实 |\n| Modbus-TCP | `pymodbus>=3.5,<4` | App 1.1b3;FC 1/2/3/4/5/6/15/16 | PLCnext 过程数据 server | TCP/502 | ✅;真 PLCnext 待核实 |\n\nFile v0.27.0:_meta.json\n\n{\n  \"ownerId\": \"kn7b067awq2s97bn3d7p5qfhw5827pxc\",\n  \"slug\": \"iaiops-plcnext\",\n  \"version\": \"0.27.0\",\n  \"publishedAt\": 1788405617359\n}\n\nFile v0.27.0:skill-card.md\n\n## Description:\n\nPLCnext/vPLC packaging edition of iaiops for reading PLCnext Control data over built-in OPC-UA and Modbus-TCP servers and routing it into existing diagnostic, downtime, predictive-maintenance, OEE, alarm, baseline, compliance, and program-analysis 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 and plant engineers use this skill to route PLCnext Control or virtual PLC tasks through existing OPC-UA and Modbus read, diagnostic, alarm, downtime, OEE, baseline, compliance, and program-analysis workflows.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The claimed read-only scope conflicts with listed export, stream publish, UNS publish, and historian-push capabilities that may move operational data.\n\nMitigation: Verify which underlying iaiops tools are enabled before deployment, and restrict export, publish, and historian paths unless destinations and data-handling rules are approved.\n\nRisk: Use against unauthorized PLCnext or virtual PLC systems could expose plant data or operational context.\n\nMitigation: Use the skill only with authorized PLCnext/vPLC systems and approved OPC-UA or Modbus endpoints.\n\nRisk: Operational instructions are primarily in Chinese, which can lead to review or configuration mistakes for teams that cannot read them accurately.\n\nMitigation: Require an accurate translation or a qualified Chinese-language reviewer before installation and plant use.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/zw008/skills/iaiops-plcnext)\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:** [Outputs may include operational diagnostics, data-quality findings, baseline checks, advisory matches, program-analysis summaries, and configuration guidance.]\n\n## Skill Version(s):\n\n0.27.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.26.0: 3 files, 5283 bytes\n\nFiles: skill-card.md (2202b), SKILL.md (6610b), _meta.json (134b)\n\nFile v0.26.0:SKILL.md\n\n---\nname: iaiops-plcnext\ndescription: >-\n  PLCnext / virtualized-PLC edition of iaiops — Phoenix Contact PLCnext Control\n  and vPLC (虚拟化 PLC) reached over its built-in OPC-UA server (opc.tcp 4840) and\n  Modbus-TCP process-data server, plus the cross-protocol brain (dataflow\n  diagnosis, downtime root cause, PdM, OEE, alarm, baseline). A packaging edition\n  — no new connector, no PLCnext-vendor SDK: it routes to the standard OPC-UA and\n  Modbus tools already shipped. Use when the task mentions PLCnext / PLCnext\n  Control / AXC F / vPLC / virtual PLC / 虚拟 PLC / Phoenix Contact controller over\n  OPC-UA or Modbus. Read-first; this edition's tool surface is read-only.\n---\n\n# iaiops-plcnext — PLCnext / vPLC edition（OPC-UA + Modbus + 脑）\n\n启动：`IAIOPS_MCP=plcnext` / `iaiops-mcp-plcnext`（= opcua + modbus + 脑;等价\n`IAIOPS_MCP=opcua,modbus`）。**打包型 edition**:PLCnext Control / vPLC 通过其**内置\nOPC-UA server**(opc.tcp 4840)与 **Modbus-TCP 过程数据 server** 读取 —— 不新增 connector、\n不依赖 PLCnext 厂商 SDK,直接复用已发布的标准 OPC-UA / Modbus 工具 + 跨协议脑。\n\n## 工具\n\n### OPC-UA（只读;PLCnext 内置 OPC-UA server,opc.tcp 4840）\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` — 自动发现 + 语义资产建模;`opcua_health_summary` 阈值分类;\n  `opcua_anomaly_scan` 有界统计异常扫描\n\n### Modbus-TCP（只读;PLCnext 过程数据 server）\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### 跨协议脑（永远随 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- 预测维护：`pdm_forecast`\n- 数据质量：`data_quality_scorecard` `data_quality_fleet_rollup`\n- 分析：`oee_compute` `downtime_events` `oee_multidim` `monitor_changes`\n- 资产：`asset_inventory` `cross_protocol_asset_model` `adopt_alias_map` `diff_alias_map`\n- 基线：`baseline_learn` `baseline_check` `baseline_record_change` `baseline_status`\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`\n  `stream_publish_event` `rca_narrate` `fleet_status` `fleet_incidents`\n- 程序解读：`plc_program_outline` `plc_program_xref` `plc_program_section` `plc_program_visibility`\n  （解读导出的 ST/AWL/L5X;PLCnext 工程可导出 IEC 61131 ST 文本后离线解读）\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` → `opcua_diagnose_connection`\n   (先确认 PLCnext 内置 OPC-UA server 4840 可达、证书/策略匹配)。\n2. **Read-first**：过程量走 OPC-UA `opcua_read_many` / Modbus `modbus_read_holding`;\n   \"没数据\"用 `diagnose_dataflow`,停机用 `downtime_triage` / `downtime_root_cause_live`。\n3. **只读**:本 edition 工具表面全只读。若需写(输出/设定值),切到含写工具的 profile 并走统一\n   MOC:`risk=HIGH` + 默认 `dry_run=True` + 改前值 undo + `iaiops approve` 具名审批双确认。\n\n## 支持版本矩阵（内部 HLD §8，设计文档不随本仓发布;`待核实` 不得当既成事实）\n\n| 协议 | 库(pin) | 规范/版本 | 覆盖 | 传输 | 自测 |\n|---|---|---|---|---|---|\n| OPC-UA | `asyncua>=2.0,<3` | OPC UA 1.0x（DA+HA+AC 子集） | PLCnext 内置 OPC-UA server | opc.tcp/4840 | ✅ mock+HDA;真 PLCnext 待核实 |\n| Modbus-TCP | `pymodbus>=3.5,<4` | App 1.1b3;FC 1/2/3/4/5/6/15/16 | PLCnext 过程数据 server | TCP/502 | ✅;真 PLCnext 待核实 |\n\nFile v0.26.0:_meta.json\n\n{\n  \"ownerId\": \"kn7b067awq2s97bn3d7p5qfhw5827pxc\",\n  \"slug\": \"iaiops-plcnext\",\n  \"version\": \"0.26.0\",\n  \"publishedAt\": 1788265756587\n}\n\nFile v0.26.0:skill-card.md\n\n## Description:\n\niaiops-plcnext helps agents read PLCnext Control and virtual PLC operational data through built-in OPC-UA and Modbus-TCP services, then diagnose dataflow, downtime, predictive maintenance, OEE, alarms, and baselines with iaiops cross-protocol analysis tools.\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 industrial automation engineers use this skill when an agent needs to inspect PLCnext or virtualized PLC data over OPC-UA or Modbus-TCP, triage operational issues, and summarize industrial data quality, alarms, downtime, and baseline changes.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill is framed as read-only for PLC writes, but listed export, publish, historian push, UNS publish, and compliance evidence bundle workflows could move sensitive operational data.\n\nMitigation: Require explicit destination approval, local site policy review, and authorized operator confirmation before using any workflow that exports or publishes plant data.\n\nRisk: Agents may use the skill around PLCnext operational data where incorrect summaries or recommendations could affect incident response decisions.\n\nMitigation: Use outputs as decision support only; review findings against site telemetry, maintenance records, and approved operating procedures before acting.\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 or text with inline commands and structured analysis summaries]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Read-first skill posture; security evidence notes that export and publish tools may move sensitive plant data outside the environment.]\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, 4413 bytes\n\nFiles: skill-card.md (2096b), SKILL.md (5208b), _meta.json (134b)\n\nFile v0.23.1:SKILL.md\n\n---\nname: iaiops-plcnext\ndescription: >-\n  PLCnext / virtualized-PLC edition of iaiops — Phoenix Contact PLCnext Control\n  and vPLC (虚拟化 PLC) reached over its built-in OPC-UA server (opc.tcp 4840) and\n  Modbus-TCP process-data server, plus the cross-protocol brain (dataflow\n  diagnosis, downtime root cause, PdM, OEE, alarm, baseline). A packaging edition\n  — no new connector, no PLCnext-vendor SDK: it routes to the standard OPC-UA and\n  Modbus tools already shipped. Use when the task mentions PLCnext / PLCnext\n  Control / AXC F / vPLC / virtual PLC / 虚拟 PLC / Phoenix Contact controller over\n  OPC-UA or Modbus. Read-first; this edition's tool surface is read-only.\n---\n\n# iaiops-plcnext — PLCnext / vPLC edition（OPC-UA + Modbus + 脑）\n\n启动：`IAIOPS_MCP=plcnext` / `iaiops-mcp-plcnext`（= opcua + modbus + 脑;等价\n`IAIOPS_MCP=opcua,modbus`）。**打包型 edition**:PLCnext Control / vPLC 通过其**内置\nOPC-UA server**(opc.tcp 4840)与 **Modbus-TCP 过程数据 server** 读取 —— 不新增 connector、\n不依赖 PLCnext 厂商 SDK,直接复用已发布的标准 OPC-UA / Modbus 工具 + 跨协议脑。\n\n## 工具\n\n### OPC-UA（只读;PLCnext 内置 OPC-UA server,opc.tcp 4840）\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` — 自动发现 + 语义资产建模;`opcua_health_summary` 阈值分类;\n  `opcua_anomaly_scan` 有界统计异常扫描\n\n### Modbus-TCP（只读;PLCnext 过程数据 server）\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### 跨协议脑（永远随 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- 预测维护：`pdm_forecast`\n- 数据质量：`data_quality_scorecard` `data_quality_fleet_rollup`\n- 分析：`oee_compute` `downtime_events` `oee_multidim` `monitor_changes`\n- 资产：`asset_inventory` `cross_protocol_asset_model` `adopt_alias_map` `diff_alias_map`\n- 基线：`baseline_learn` `baseline_check` `baseline_record_change` `baseline_status`\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`\n  `stream_publish_event` `rca_narrate` `fleet_status` `fleet_incidents`\n- 程序解读：`plc_program_outline` `plc_program_xref` `plc_program_section` `plc_program_visibility`\n  （解读导出的 ST/AWL/L5X;PLCnext 工程可导出 IEC 61131 ST 文本后离线解读）\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` → `opcua_diagnose_connection`\n   (先确认 PLCnext 内置 OPC-UA server 4840 可达、证书/策略匹配)。\n2. **Read-first**：过程量走 OPC-UA `opcua_read_many` / Modbus `modbus_read_holding`;\n   \"没数据\"用 `diagnose_dataflow`,停机用 `downtime_triage` / `downtime_root_cause_live`。\n3. **只读**:本 edition 工具表面全只读。若需写(输出/设定值),切到含写工具的 profile 并走统一\n   MOC:`risk=HIGH` + 默认 `dry_run=True` + 改前值 undo + `iaiops approve` 具名审批双确认。\n\n## 支持版本矩阵（内部 HLD §8，设计文档不随本仓发布;`待核实` 不得当既成事实）\n\n| 协议 | 库(pin) | 规范/版本 | 覆盖 | 传输 | 自测 |\n|---|---|---|---|---|---|\n| OPC-UA | `asyncua>=2.0,<3` | OPC UA 1.0x（DA+HA+AC 子集） | PLCnext 内置 OPC-UA server | opc.tcp/4840 | ✅ mock+HDA;真 PLCnext 待核实 |\n| Modbus-TCP | `pymodbus>=3.5,<4` | App 1.1b3;FC 1/2/3/4/5/6/15/16 | PLCnext 过程数据 server | TCP/502 | ✅;真 PLCnext 待核实 |\n\nFile v0.23.1:_meta.json\n\n{\n  \"ownerId\": \"kn7b067awq2s97bn3d7p5qfhw5827pxc\",\n  \"slug\": \"iaiops-plcnext\",\n  \"version\": \"0.23.1\",\n  \"publishedAt\": 1787894345940\n}\n\nFile v0.23.1:skill-card.md\n\n## Description:\n\nPLCnext and virtualized-PLC edition of iaiops for reading Phoenix Contact PLCnext Control and vPLC data over built-in OPC-UA and Modbus-TCP services, with cross-protocol diagnostics for dataflow, downtime root cause, predictive maintenance, OEE, alarms, and baselines.\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 industrial engineers use this skill to route PLCnext and virtualized PLC tasks to existing OPC-UA and Modbus tools for read-first diagnostics, health checks, alarm analysis, downtime triage, and operational reporting.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill presents itself as read-only, but the security summary notes tools that can export data, publish events, push historian data, or create investigation records.\n\nMitigation: Review enabled backend tools before installation and disable or approval-gate any non-read-only actions.\n\nRisk: Device-read diagnostics can expose operational data from PLCnext or virtualized PLC environments.\n\nMitigation: Install only in environments where data access is authorized and where approvals, network controls, and logging are enforced.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/zw008/skills/iaiops-plcnext)\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, shell commands, and configuration values]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Read-first PLCnext profile guidance for OPC-UA, Modbus-TCP, diagnostics, and operational analysis workflows]\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, 3775 bytes\n\nFiles: skill-card.md (1926b), SKILL.md (4369b), _meta.json (134b)\n\nFile v0.23.0:SKILL.md\n\n---\nname: iaiops-plcnext\ndescription: >-\n  PLCnext / virtualized-PLC edition of iaiops — Phoenix Contact PLCnext Control\n  and vPLC (虚拟化 PLC) reached over its built-in OPC-UA server (opc.tcp 4840) and\n  Modbus-TCP process-data server, plus the cross-protocol brain (dataflow\n  diagnosis, downtime root cause, PdM, OEE, alarm, baseline). A packaging edition\n  — no new connector, no PLCnext-vendor SDK: it routes to the standard OPC-UA and\n  Modbus tools already shipped. Use when the task mentions PLCnext / PLCnext\n  Control / AXC F / vPLC / virtual PLC / 虚拟 PLC / Phoenix Contact controller over\n  OPC-UA or Modbus. Read-first; this edition's tool surface is read-only.\n---\n\n# iaiops-plcnext — PLCnext / vPLC edition（OPC-UA + Modbus + 脑）\n\n启动：`IAIOPS_MCP=plcnext` / `iaiops-mcp-plcnext`（= opcua + modbus + 脑;等价\n`IAIOPS_MCP=opcua,modbus`）。**打包型 edition**:PLCnext Control / vPLC 通过其**内置\nOPC-UA server**(opc.tcp 4840)与 **Modbus-TCP 过程数据 server** 读取 —— 不新增 connector、\n不依赖 PLCnext 厂商 SDK,直接复用已发布的标准 OPC-UA / Modbus 工具 + 跨协议脑。\n\n## 工具\n\n### OPC-UA（只读;PLCnext 内置 OPC-UA server,opc.tcp 4840）\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` — 自动发现 + 语义资产建模;`opcua_health_summary` 阈值分类;\n  `opcua_anomaly_scan` 有界统计异常扫描\n\n### Modbus-TCP（只读;PLCnext 过程数据 server）\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### 跨协议脑（永远随 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- 预测维护：`pdm_forecast`\n- 数据质量：`data_quality_scorecard` `data_quality_fleet_rollup`\n- 分析：`oee_compute` `downtime_events` `oee_multidim` `monitor_changes`\n- 资产：`asset_inventory` `cross_protocol_asset_model` `adopt_alias_map` `diff_alias_map`\n- 基线：`baseline_learn` `baseline_check` `baseline_record_change` `baseline_status`\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`\n  `stream_publish_event` `rca_narrate` `fleet_status` `fleet_incidents`\n- 程序解读：`plc_program_outline` `plc_program_xref` `plc_program_section` `plc_program_visibility`\n  （解读导出的 ST/AWL/L5X;PLCnext 工程可导出 IEC 61131 ST 文本后离线解读）\n- 元：`protocols_supported`\n\n## Workflows\n\n1. **Doctor-first**：`protocols_supported` → `iaiops doctor` → `opcua_diagnose_connection`\n   (先确认 PLCnext 内置 OPC-UA server 4840 可达、证书/策略匹配)。\n2. **Read-first**：过程量走 OPC-UA `opcua_read_many` / Modbus `modbus_read_holding`;\n   \"没数据\"用 `diagnose_dataflow`,停机用 `downtime_triage` / `downtime_root_cause_live`。\n3. **只读**:本 edition 工具表面全只读。若需写(输出/设定值),切到含写工具的 profile 并走统一\n   MOC:`risk=HIGH` + 默认 `dry_run=True` + 改前值 undo + `iaiops approve` 具名审批双确认。\n\n## 支持版本矩阵（内部 HLD §8，设计文档不随本仓发布;`待核实` 不得当既成事实）\n\n| 协议 | 库(pin) | 规范/版本 | 覆盖 | 传输 | 自测 |\n|---|---|---|---|---|---|\n| OPC-UA | `asyncua>=2.0,<3` | OPC UA 1.0x（DA+HA+AC 子集） | PLCnext 内置 OPC-UA server | opc.tcp/4840 | ✅ mock+HDA;真 PLCnext 待核实 |\n| Modbus-TCP | `pymodbus>=3.5,<4` | App 1.1b3;FC 1/2/3/4/5/6/15/16 | PLCnext 过程数据 server | TCP/502 | ✅;真 PLCnext 待核实 |\n\nFile v0.23.0:_meta.json\n\n{\n  \"ownerId\": \"kn7b067awq2s97bn3d7p5qfhw5827pxc\",\n  \"slug\": \"iaiops-plcnext\",\n  \"version\": \"0.23.0\",\n  \"publishedAt\": 1787632403420\n}\n\nFile v0.23.0:skill-card.md\n\n## Description:\n\niaiops-plcnext helps agents work with Phoenix Contact PLCnext Control and virtual PLC environments through OPC-UA and Modbus workflows for diagnostics, asset modeling, alarm, OEE, downtime, historian, export, stream, UNS, and compliance tasks.\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 industrial engineers use this skill to route PLCnext and virtual PLC requests to OPC-UA and Modbus workflows for connection diagnosis, process-data reading, historian and alarm analysis, OEE and downtime investigation, asset modeling, and controlled data export or publishing.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Export and publish tools could send industrial data outside the PLC environment despite the artifact's read-only positioning.\n\nMitigation: Confirm historian, stream, UNS, export, and compliance bundle destinations before use, and require explicit operator approval before handling sensitive plant data.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/zw008/skills/iaiops-plcnext)\n\n## Skill Output:\n\n**Output Type(s):** [Guidance, Markdown, Shell commands, Configuration]\n\n**Output Format:** [Markdown guidance with inline commands and tool names]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May describe OPC-UA, Modbus, historian, export, stream, UNS, and compliance workflows; operator approval is recommended before using tools with sensitive plant data.]\n\n## Skill Version(s):\n\n0.23.0 (source: evidence.release.version)\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, 3998 bytes\n\nFiles: skill-card.md (2440b), SKILL.md (4355b), _meta.json (134b)\n\nFile v0.22.0:SKILL.md\n\n---\nname: iaiops-plcnext\ndescription: >-\n  PLCnext / virtualized-PLC edition of iaiops — Phoenix Contact PLCnext Control\n  and vPLC (虚拟化 PLC) reached over its built-in OPC-UA server (opc.tcp 4840) and\n  Modbus-TCP process-data server, plus the cross-protocol brain (dataflow\n  diagnosis, downtime root cause, PdM, OEE, alarm, baseline). A packaging edition\n  — no new connector, no PLCnext-vendor SDK: it routes to the standard OPC-UA and\n  Modbus tools already shipped. Use when the task mentions PLCnext / PLCnext\n  Control / AXC F / vPLC / virtual PLC / 虚拟 PLC / Phoenix Contact controller over\n  OPC-UA or Modbus. Read-first; this edition's tool surface is read-only.\n---\n\n# iaiops-plcnext — PLCnext / vPLC edition（OPC-UA + Modbus + 脑）\n\n启动：`IAIOPS_MCP=plcnext` / `iaiops-mcp-plcnext`（= opcua + modbus + 脑;等价\n`IAIOPS_MCP=opcua,modbus`）。**打包型 edition**:PLCnext Control / vPLC 通过其**内置\nOPC-UA server**(opc.tcp 4840)与 **Modbus-TCP 过程数据 server** 读取 —— 不新增 connector、\n不依赖 PLCnext 厂商 SDK,直接复用已发布的标准 OPC-UA / Modbus 工具 + 跨协议脑。\n\n## 工具\n\n### OPC-UA（只读;PLCnext 内置 OPC-UA server,opc.tcp 4840）\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` — 自动发现 + 语义资产建模;`opcua_health_summary` 阈值分类;\n  `opcua_anomaly_scan` 有界统计异常扫描\n\n### Modbus-TCP（只读;PLCnext 过程数据 server）\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### 跨协议脑（永远随 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- 预测维护：`pdm_forecast`\n- 数据质量：`data_quality_scorecard` `data_quality_fleet_rollup`\n- 分析：`oee_compute` `downtime_events` `oee_multidim` `monitor_changes`\n- 资产：`asset_inventory` `cross_protocol_asset_model` `adopt_alias_map` `diff_alias_map`\n- 基线：`baseline_learn` `baseline_check` `baseline_record_change` `baseline_status`\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`\n  `stream_publish_event` `rca_narrate` `fleet_status` `fleet_incidents`\n- 程序解读：`plc_program_outline` `plc_program_xref` `plc_program_section` `plc_program_visibility`\n  （解读导出的 ST/AWL/L5X;PLCnext 工程可导出 IEC 61131 ST 文本后离线解读）\n- 元：`protocols_supported`\n\n## Workflows\n\n1. **Doctor-first**：`protocols_supported` → `iaiops doctor` → `opcua_diagnose_connection`\n   (先确认 PLCnext 内置 OPC-UA server 4840 可达、证书/策略匹配)。\n2. **Read-first**：过程量走 OPC-UA `opcua_read_many` / Modbus `modbus_read_holding`;\n   \"没数据\"用 `diagnose_dataflow`,停机用 `downtime_triage` / `downtime_root_cause_live`。\n3. **只读**:本 edition 工具表面全只读。若需写(输出/设定值),切到含写工具的 profile 并走统一\n   MOC:`risk=HIGH` + 默认 `dry_run=True` + 改前值 undo + `iaiops approve` 具名审批双确认。\n\n## 支持版本矩阵（内部 HLD §8，设计文档不随本仓发布;`待核实` 不得当既成事实）\n\n| 协议 | 库(pin) | 规范/版本 | 覆盖 | 传输 | 自测 |\n|---|---|---|---|---|---|\n| OPC-UA | `asyncua>=2.0,<3` | OPC UA 1.0x（DA+HA+AC 子集） | PLCnext 内置 OPC-UA server | opc.tcp/4840 | ✅ mock+HDA;真 PLCnext 待核实 |\n| Modbus-TCP | `pymodbus>=3.5,<4` | App 1.1b3;FC 1/2/3/4/5/6/15/16 | PLCnext 过程数据 server | TCP/502 | ✅;真 PLCnext 待核实 |\n\nFile v0.22.0:_meta.json\n\n{\n  \"ownerId\": \"kn7b067awq2s97bn3d7p5qfhw5827pxc\",\n  \"slug\": \"iaiops-plcnext\",\n  \"version\": \"0.22.0\",\n  \"publishedAt\": 1785676159183\n}\n\nFile v0.22.0:skill-card.md\n\n## Description: <br>\nPLCnext and virtualized-PLC edition of iaiops for monitoring Phoenix Contact PLCnext Control and vPLC systems through built-in OPC-UA and Modbus-TCP interfaces, with cross-protocol diagnostics, downtime root cause analysis, predictive maintenance, OEE, alarm analysis, and baseline workflows. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[zw008](https://clawhub.ai/user/zw008) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers, automation engineers, and industrial operations teams use this skill to route PLCnext and virtual PLC monitoring tasks through standard OPC-UA and Modbus workflows. It helps inspect process data, diagnose connectivity or dataflow issues, analyze downtime and alarms, compute OEE, and review exported PLC program text. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill describes a read-only PLC monitoring posture while also listing export, publish, evidence-bundling, stream, and historian write tools that can move industrial data outside the PLC environment. <br>\nMitigation: Before deployment, confirm the enabled runtime profile, disable nonessential export or publish tools, verify every non-local destination, and require approval gates for data movement. <br>\nRisk: PLCnext and virtual PLC telemetry may include sensitive operational data. <br>\nMitigation: Limit access to approved operators, review exported or streamed data paths, and use least-privilege credentials for OPC-UA, Modbus, historian, and publishing integrations. <br>\n\n\n## Reference(s): <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Guidance, Analysis, Shell commands, Configuration] <br>\n**Output Format:** [Markdown with inline command names, environment variables, and tool references] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [May reference OPC-UA, Modbus, PLC monitoring, export, publish, historian, and evidence-bundling tool behavior; the skill itself is documentation-only evidence.] <br>\n\n## Skill Version(s): <br>\n0.22.0 (source: server release metadata) <br>\n\n## Ethical Considerations: <br>\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. <br>\n\nArchive v0.21.1: 3 files, 3909 bytes\n\nFiles: skill-card.md (2251b), SKILL.md (4355b), _meta.json (134b)\n\nFile v0.21.1:SKILL.md\n\n---\nname: iaiops-plcnext\ndescription: >-\n  PLCnext / virtualized-PLC edition of iaiops — Phoenix Contact PLCnext Control\n  and vPLC (虚拟化 PLC) reached over its built-in OPC-UA server (opc.tcp 4840) and\n  Modbus-TCP process-data server, plus the cross-protocol brain (dataflow\n  diagnosis, downtime root cause, PdM, OEE, alarm, baseline). A packaging edition\n  — no new connector, no PLCnext-vendor SDK: it routes to the standard OPC-UA and\n  Modbus tools already shipped. Use when the task mentions PLCnext / PLCnext\n  Control / AXC F / vPLC / virtual PLC / 虚拟 PLC / Phoenix Contact controller over\n  OPC-UA or Modbus. Read-first; this edition's tool surface is read-only.\n---\n\n# iaiops-plcnext — PLCnext / vPLC edition（OPC-UA + Modbus + 脑）\n\n启动：`IAIOPS_MCP=plcnext` / `iaiops-mcp-plcnext`（= opcua + modbus + 脑;等价\n`IAIOPS_MCP=opcua,modbus`）。**打包型 edition**:PLCnext Control / vPLC 通过其**内置\nOPC-UA server**(opc.tcp 4840)与 **Modbus-TCP 过程数据 server** 读取 —— 不新增 connector、\n不依赖 PLCnext 厂商 SDK,直接复用已发布的标准 OPC-UA / Modbus 工具 + 跨协议脑。\n\n## 工具\n\n### OPC-UA（只读;PLCnext 内置 OPC-UA server,opc.tcp 4840）\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` — 自动发现 + 语义资产建模;`opcua_health_summary` 阈值分类;\n  `opcua_anomaly_scan` 有界统计异常扫描\n\n### Modbus-TCP（只读;PLCnext 过程数据 server）\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### 跨协议脑（永远随 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- 预测维护：`pdm_forecast`\n- 数据质量：`data_quality_scorecard` `data_quality_fleet_rollup`\n- 分析：`oee_compute` `downtime_events` `oee_multidim` `monitor_changes`\n- 资产：`asset_inventory` `cross_protocol_asset_model` `adopt_alias_map` `diff_alias_map`\n- 基线：`baseline_learn` `baseline_check` `baseline_record_change` `baseline_status`\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`\n  `stream_publish_event` `rca_narrate` `fleet_status` `fleet_incidents`\n- 程序解读：`plc_program_outline` `plc_program_xref` `plc_program_section` `plc_program_visibility`\n  （解读导出的 ST/AWL/L5X;PLCnext 工程可导出 IEC 61131 ST 文本后离线解读）\n- 元：`protocols_supported`\n\n## Workflows\n\n1. **Doctor-first**：`protocols_supported` → `iaiops doctor` → `opcua_diagnose_connection`\n   (先确认 PLCnext 内置 OPC-UA server 4840 可达、证书/策略匹配)。\n2. **Read-first**：过程量走 OPC-UA `opcua_read_many` / Modbus `modbus_read_holding`;\n   \"没数据\"用 `diagnose_dataflow`,停机用 `downtime_triage` / `downtime_root_cause_live`。\n3. **只读**:本 edition 工具表面全只读。若需写(输出/设定值),切到含写工具的 profile 并走统一\n   MOC:`risk=HIGH` + 默认 `dry_run=True` + 改前值 undo + `iaiops approve` 具名审批双确认。\n\n## 支持版本矩阵（内部 HLD §8，设计文档不随本仓发布;`待核实` 不得当既成事实）\n\n| 协议 | 库(pin) | 规范/版本 | 覆盖 | 传输 | 自测 |\n|---|---|---|---|---|---|\n| OPC-UA | `asyncua>=1.0,<2` | OPC UA 1.0x（DA+HA+AC 子集） | PLCnext 内置 OPC-UA server | opc.tcp/4840 | ✅ mock+HDA;真 PLCnext 待核实 |\n| Modbus-TCP | `pymodbus>=3.5,<4` | App 1.1b3;FC 1/2/3/4/5/6/15/16 | PLCnext 过程数据 server | TCP/502 | ✅;真 PLCnext 待核实 |\n\nFile v0.21.1:_meta.json\n\n{\n  \"ownerId\": \"kn7b067awq2s97bn3d7p5qfhw5827pxc\",\n  \"slug\": \"iaiops-plcnext\",\n  \"version\": \"0.21.1\",\n  \"publishedAt\": 1785655494255\n}\n\nFile v0.21.1:skill-card.md\n\n## Description: <br>\niaiops-plcnext helps agents inspect PLCnext Control and virtual PLC systems through existing OPC-UA and Modbus-TCP tooling for connection diagnosis, process-data reads, alarms, historian checks, root-cause analysis, predictive maintenance, OEE, and baseline monitoring. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[zw008](https://clawhub.ai/user/zw008) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers, controls engineers, and operations teams use this skill to guide read-first PLCnext troubleshooting and monitoring workflows over OPC-UA and Modbus-TCP. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The release advertises a read-only PLCnext profile while also listing export, stream publishing, and historian push tools that could move industrial data outside the read path. <br>\nMitigation: Review runtime tool availability before installation and confirm export, stream publishing, and historian push are disabled or separately approved for the intended profile. <br>\nRisk: PLC and process data may be sensitive, especially in production operational technology environments. <br>\nMitigation: Treat PLC/process data as sensitive and avoid production OT use until the read-only contract is explicit and enforceable. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/zw008/skills/iaiops-plcnext) <br>\n- [ClawHub publisher profile](https://clawhub.ai/user/zw008) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance] <br>\n**Output Format:** [Markdown with inline shell commands and configuration notes] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Outputs are guidance for agent-mediated PLCnext monitoring and troubleshooting workflows.] <br>\n\n## Skill Version(s): <br>\n0.21.1 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\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. <br>\n\nArchive v0.21.0: 3 files, 3793 bytes\n\nFiles: skill-card.md (1934b), SKILL.md (4355b), _meta.json (134b)\n\nFile v0.21.0:SKILL.md\n\n---\nname: iaiops-plcnext\ndescription: >-\n  PLCnext / virtualized-PLC edition of iaiops — Phoenix Contact PLCnext Control\n  and vPLC (虚拟化 PLC) reached over its built-in OPC-UA server (opc.tcp 4840) and\n  Modbus-TCP process-data server, plus the cross-protocol brain (dataflow\n  diagnosis, downtime root cause, PdM, OEE, alarm, baseline). A packaging edition\n  — no new connector, no PLCnext-vendor SDK: it routes to the standard OPC-UA and\n  Modbus tools already shipped. Use when the task mentions PLCnext / PLCnext\n  Control / AXC F / vPLC / virtual PLC / 虚拟 PLC / Phoenix Contact controller over\n  OPC-UA or Modbus. Read-first; this edition's tool surface is read-only.\n---\n\n# iaiops-plcnext — PLCnext / vPLC edition（OPC-UA + Modbus + 脑）\n\n启动：`IAIOPS_MCP=plcnext` / `iaiops-mcp-plcnext`（= opcua + modbus + 脑;等价\n`IAIOPS_MCP=opcua,modbus`）。**打包型 edition**:PLCnext Control / vPLC 通过其**内置\nOPC-UA server**(opc.tcp 4840)与 **Modbus-TCP 过程数据 server** 读取 —— 不新增 connector、\n不依赖 PLCnext 厂商 SDK,直接复用已发布的标准 OPC-UA / Modbus 工具 + 跨协议脑。\n\n## 工具\n\n### OPC-UA（只读;PLCnext 内置 OPC-UA server,opc.tcp 4840）\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` — 自动发现 + 语义资产建模;`opcua_health_summary` 阈值分类;\n  `opcua_anomaly_scan` 有界统计异常扫描\n\n### Modbus-TCP（只读;PLCnext 过程数据 server）\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### 跨协议脑（永远随 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- 预测维护：`pdm_forecast`\n- 数据质量：`data_quality_scorecard` `data_quality_fleet_rollup`\n- 分析：`oee_compute` `downtime_events` `oee_multidim` `monitor_changes`\n- 资产：`asset_inventory` `cross_protocol_asset_model` `adopt_alias_map` `diff_alias_map`\n- 基线：`baseline_learn` `baseline_check` `baseline_record_change` `baseline_status`\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`\n  `stream_publish_event` `rca_narrate` `fleet_status` `fleet_incidents`\n- 程序解读：`plc_program_outline` `plc_program_xref` `plc_program_section` `plc_program_visibility`\n  （解读导出的 ST/AWL/L5X;PLCnext 工程可导出 IEC 61131 ST 文本后离线解读）\n- 元：`protocols_supported`\n\n## Workflows\n\n1. **Doctor-first**：`protocols_supported` → `iaiops doctor` → `opcua_diagnose_connection`\n   (先确认 PLCnext 内置 OPC-UA server 4840 可达、证书/策略匹配)。\n2. **Read-first**：过程量走 OPC-UA `opcua_read_many` / Modbus `modbus_read_holding`;\n   \"没数据\"用 `diagnose_dataflow`,停机用 `downtime_triage` / `downtime_root_cause_live`。\n3. **只读**:本 edition 工具表面全只读。若需写(输出/设定值),切到含写工具的 profile 并走统一\n   MOC:`risk=HIGH` + 默认 `dry_run=True` + 改前值 undo + `iaiops approve` 具名审批双确认。\n\n## 支持版本矩阵（内部 HLD §8，设计文档不随本仓发布;`待核实` 不得当既成事实）\n\n| 协议 | 库(pin) | 规范/版本 | 覆盖 | 传输 | 自测 |\n|---|---|---|---|---|---|\n| OPC-UA | `asyncua>=1.0,<2` | OPC UA 1.0x（DA+HA+AC 子集） | PLCnext 内置 OPC-UA server | opc.tcp/4840 | ✅ mock+HDA;真 PLCnext 待核实 |\n| Modbus-TCP | `pymodbus>=3.5,<4` | App 1.1b3;FC 1/2/3/4/5/6/15/16 | PLCnext 过程数据 server | TCP/502 | ✅;真 PLCnext 待核实 |\n\nFile v0.21.0:_meta.json\n\n{\n  \"ownerId\": \"kn7b067awq2s97bn3d7p5qfhw5827pxc\",\n  \"slug\": \"iaiops-plcnext\",\n  \"version\": \"0.21.0\",\n  \"publishedAt\": 1785640055059\n}\n\nFile v0.21.0:skill-card.md\n\n## Description: <br>\niaiops-plcnext helps agents work with Phoenix Contact PLCnext Control and virtual PLC environments through OPC-UA and Modbus-TCP reads, diagnostics, OEE, alarms, predictive maintenance, data quality, baseline, and asset analysis. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[zw008](https://clawhub.ai/user/zw008) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and industrial automation engineers use this skill to route PLCnext or virtual PLC analysis requests to existing OPC-UA and Modbus workflows for diagnostics, root cause analysis, asset modeling, OEE, alarms, and predictive maintenance. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Server security evidence flags a mismatch between the read-only posture and listed export, publish, and historian-push tools that could send or write operational data elsewhere. <br>\nMitigation: Review before production or connected industrial use, and gate or disable export, stream publication, and historian-push capabilities unless explicitly approved. <br>\n\n\n## Reference(s): <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance] <br>\n**Output Format:** [Markdown guidance with tool names, workflows, and shell command snippets] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [May reference industrial protocol tools and operational data workflows; review connected-environment actions before use.] <br>\n\n## Skill Version(s): <br>\n0.21.0 (source: server release metadata) <br>\n\n## Ethical Considerations: <br>\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. <br>\n\nArchive v0.20.4: 3 files, 3889 bytes\n\nFiles: skill-card.md (2181b), SKILL.md (4355b), _meta.json (134b)\n\nFile v0.20.4:SKILL.md\n\n---\nname: iaiops-plcnext\ndescription: >-\n  PLCnext / virtualized-PLC edition of iaiops — Phoenix Contact PLCnext Control\n  and vPLC (虚拟化 PLC) reached over its built-in OPC-UA server (opc.tcp 4840) and\n  Modbus-TCP process-data server, plus the cross-protocol brain (dataflow\n  diagnosis, downtime root cause, PdM, OEE, alarm, baseline). A packaging edition\n  — no new connector, no PLCnext-vendor SDK: it routes to the standard OPC-UA and\n  Modbus tools already shipped. Use when the task mentions PLCnext / PLCnext\n  Control / AXC F / vPLC / virtual PLC / 虚拟 PLC / Phoenix Contact controller over\n  OPC-UA or Modbus. Read-first; this edition's tool surface is read-only.\n---\n\n# iaiops-plcnext — PLCnext / vPLC edition（OPC-UA + Modbus + 脑）\n\n启动：`IAIOPS_MCP=plcnext` / `iaiops-mcp-plcnext`（= opcua + modbus + 脑;等价\n`IAIOPS_MCP=opcua,modbus`）。**打包型 edition**:PLCnext Control / vPLC 通过其**内置\nOPC-UA server**(opc.tcp 4840)与 **Modbus-TCP 过程数据 server** 读取 —— 不新增 connector、\n不依赖 PLCnext 厂商 SDK,直接复用已发布的标准 OPC-UA / Modbus 工具 + 跨协议脑。\n\n## 工具\n\n### OPC-UA（只读;PLCnext 内置 OPC-UA server,opc.tcp 4840）\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` — 自动发现 + 语义资产建模;`opcua_health_summary` 阈值分类;\n  `opcua_anomaly_scan` 有界统计异常扫描\n\n### Modbus-TCP（只读;PLCnext 过程数据 server）\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### 跨协议脑（永远随 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- 预测维护：`pdm_forecast`\n- 数据质量：`data_quality_scorecard` `data_quality_fleet_rollup`\n- 分析：`oee_compute` `downtime_events` `oee_multidim` `monitor_changes`\n- 资产：`asset_inventory` `cross_protocol_asset_model` `adopt_alias_map` `diff_alias_map`\n- 基线：`baseline_learn` `baseline_check` `baseline_record_change` `baseline_status`\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`\n  `stream_publish_event` `rca_narrate` `fleet_status` `fleet_incidents`\n- 程序解读：`plc_program_outline` `plc_program_xref` `plc_program_section` `plc_program_visibility`\n  （解读导出的 ST/AWL/L5X;PLCnext 工程可导出 IEC 61131 ST 文本后离线解读）\n- 元：`protocols_supported`\n\n## Workflows\n\n1. **Doctor-first**：`protocols_supported` → `iaiops doctor` → `opcua_diagnose_connection`\n   (先确认 PLCnext 内置 OPC-UA server 4840 可达、证书/策略匹配)。\n2. **Read-first**：过程量走 OPC-UA `opcua_read_many` / Modbus `modbus_read_holding`;\n   \"没数据\"用 `diagnose_dataflow`,停机用 `downtime_triage` / `downtime_root_cause_live`。\n3. **只读**:本 edition 工具表面全只读。若需写(输出/设定值),切到含写工具的 profile 并走统一\n   MOC:`risk=HIGH` + 默认 `dry_run=True` + 改前值 undo + `iaiops approve` 具名审批双确认。\n\n## 支持版本矩阵（内部 HLD §8，设计文档不随本仓发布;`待核实` 不得当既成事实）\n\n| 协议 | 库(pin) | 规范/版本 | 覆盖 | 传输 | 自测 |\n|---|---|---|---|---|---|\n| OPC-UA | `asyncua>=1.0,<2` | OPC UA 1.0x（DA+HA+AC 子集） | PLCnext 内置 OPC-UA server | opc.tcp/4840 | ✅ mock+HDA;真 PLCnext 待核实 |\n| Modbus-TCP | `pymodbus>=3.5,<4` | App 1.1b3;FC 1/2/3/4/5/6/15/16 | PLCnext 过程数据 server | TCP/502 | ✅;真 PLCnext 待核实 |\n\nFile v0.20.4:_meta.json\n\n{\n  \"ownerId\": \"kn7b067awq2s97bn3d7p5qfhw5827pxc\",\n  \"slug\": \"iaiops-plcnext\",\n  \"version\": \"0.20.4\",\n  \"publishedAt\": 1785630530203\n}\n\nFile v0.20.4:skill-card.md\n\n## Description: <br>\nPLCnext and virtualized-PLC edition of iaiops for reading Phoenix Contact PLCnext Control and vPLC data through built-in OPC-UA and Modbus-TCP services, then supporting cross-protocol diagnostics, downtime analysis, predictive maintenance, OEE, alarm, and baseline workflows. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[zw008](https://clawhub.ai/user/zw008) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and industrial engineers use this skill to inspect PLCnext or virtual PLC process data through OPC-UA and Modbus-TCP, diagnose dataflow and downtime issues, and generate operational analyses without adding a PLCnext-specific connector. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill presents a read-first PLCnext diagnostic posture while listing export, historian push, and stream publish tools that can create outbound side effects. <br>\nMitigation: Before installation or use, confirm the active MCP profile disables or gates historian_push, export_data, stream_publish, and stream_publish_event, and require explicit approval plus destination scoping for any export or publish action. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/zw008/skills/iaiops-plcnext) <br>\n- [Publisher profile](https://clawhub.ai/user/zw008) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [guidance, shell commands, configuration, analysis, markdown] <br>\n**Output Format:** [Markdown guidance with inline tool names, commands, and configuration values] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [May propose read workflows and diagnostic analysis; export and publish operations require review and destination scoping.] <br>\n\n## Skill Version(s): <br>\n0.20.4 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\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. <br>\n\nArchive v0.20.3: 3 files, 3898 bytes\n\nFiles: skill-card.md (2243b), SKILL.md (4355b), _meta.json (134b)\n\nFile v0.20.3:SKILL.md\n\n---\nname: iaiops-plcnext\ndescription: >-\n  PLCnext / virtualized-PLC edition of iaiops — Phoenix Contact PLCnext Control\n  and vPLC (虚拟化 PLC) reached over its built-in OPC-UA server (opc.tcp 4840) and\n  Modbus-TCP process-data server, plus the cross-protocol brain (dataflow\n  diagnosis, downtime root cause, PdM, OEE, alarm, baseline). A packaging edition\n  — no new connector, no PLCnext-vendor SDK: it routes to the standard OPC-UA and\n  Modbus tools already shipped. Use when the task mentions PLCnext / PLCnext\n  Control / AXC F / vPLC / virtual PLC / 虚拟 PLC / Phoenix Contact controller over\n  OPC-UA or Modbus. Read-first; this edition's tool surface is read-only.\n---\n\n# iaiops-plcnext — PLCnext / vPLC edition（OPC-UA + Modbus + 脑）\n\n启动：`IAIOPS_MCP=plcnext` / `iaiops-mcp-plcnext`（= opcua + modbus + 脑;等价\n`IAIOPS_MCP=opcua,modbus`）。**打包型 edition**:PLCnext Control / vPLC 通过其**内置\nOPC-UA server**(opc.tcp 4840)与 **Modbus-TCP 过程数据 server** 读取 —— 不新增 connector、\n不依赖 PLCnext 厂商 SDK,直接复用已发布的标准 OPC-UA / Modbus 工具 + 跨协议脑。\n\n## 工具\n\n### OPC-UA（只读;PLCnext 内置 OPC-UA server,opc.tcp 4840）\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` — 自动发现 + 语义资产建模;`opcua_health_summary` 阈值分类;\n  `opcua_anomaly_scan` 有界统计异常扫描\n\n### Modbus-TCP（只读;PLCnext 过程数据 server）\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### 跨协议脑（永远随 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- 预测维护：`pdm_forecast`\n- 数据质量：`data_quality_scorecard` `data_quality_fleet_rollup`\n- 分析：`oee_compute` `downtime_events` `oee_multidim` `monitor_changes`\n- 资产：`asset_inventory` `cross_protocol_asset_model` `adopt_alias_map` `diff_alias_map`\n- 基线：`baseline_learn` `baseline_check` `baseline_record_change` `baseline_status`\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`\n  `stream_publish_event` `rca_narrate` `fleet_status` `fleet_incidents`\n- 程序解读：`plc_program_outline` `plc_program_xref` `plc_program_section` `plc_program_visibility`\n  （解读导出的 ST/AWL/L5X;PLCnext 工程可导出 IEC 61131 ST 文本后离线解读）\n- 元：`protocols_supported`\n\n## Workflows\n\n1. **Doctor-first**：`protocols_supported` → `iaiops doctor` → `opcua_diagnose_connection`\n   (先确认 PLCnext 内置 OPC-UA server 4840 可达、证书/策略匹配)。\n2. **Read-first**：过程量走 OPC-UA `opcua_read_many` / Modbus `modbus_read_holding`;\n   \"没数据\"用 `diagnose_dataflow`,停机用 `downtime_triage` / `downtime_root_cause_live`。\n3. **只读**:本 edition 工具表面全只读。若需写(输出/设定值),切到含写工具的 profile 并走统一\n   MOC:`risk=HIGH` + 默认 `dry_run=True` + 改前值 undo + `iaiops approve` 具名审批双确认。\n\n## 支持版本矩阵（内部 HLD §8，设计文档不随本仓发布;`待核实` 不得当既成事实）\n\n| 协议 | 库(pin) | 规范/版本 | 覆盖 | 传输 | 自测 |\n|---|---|---|---|---|---|\n| OPC-UA | `asyncua>=1.0,<2` | OPC UA 1.0x（DA+HA+AC 子集） | PLCnext 内置 OPC-UA server | opc.tcp/4840 | ✅ mock+HDA;真 PLCnext 待核实 |\n| Modbus-TCP | `pymodbus>=3.5,<4` | App 1.1b3;FC 1/2/3/4/5/6/15/16 | PLCnext 过程数据 server | TCP/502 | ✅;真 PLCnext 待核实 |\n\nFile v0.20.3:_meta.json\n\n{\n  \"ownerId\": \"kn7b067awq2s97bn3d7p5qfhw5827pxc\",\n  \"slug\": \"iaiops-plcnext\",\n  \"version\": \"0.20.3\",\n  \"publishedAt\": 1785558749797\n}\n\nFile v0.20.3:skill-card.md\n\n## Description: <br>\niaiops-plcnext helps agents work with PLCnext Control and virtual PLC data through existing OPC-UA and Modbus tooling for diagnostics, asset modeling, alarms, predictive maintenance, OEE, and data-quality workflows. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[zw008](https://clawhub.ai/user/zw008) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers, industrial engineers, and operations teams use this skill to guide read-first PLCnext and virtual PLC inspection over OPC-UA and Modbus, then apply cross-protocol diagnostics, downtime analysis, predictive maintenance, OEE, alarm, baseline, and compliance workflows. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The release is described as read-only while the security evidence notes export, push, and stream-publish tools for industrial data. <br>\nMitigation: Before installation, verify that historian_push, export_data, stream_publish, and stream_publish_event are disabled or protected by documented approval controls. <br>\nRisk: PLCnext and virtual PLC workflows may expose industrial operational data through OPC-UA, Modbus, or historian-related paths. <br>\nMitigation: Use the profile in a review posture until the publisher documents a clear read, write, publish, and outbound-data capability matrix. <br>\n\n\n## Reference(s): <br>\n- [iaiops-plcnext ClawHub release](https://clawhub.ai/zw008/skills/iaiops-plcnext) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [guidance, shell commands, configuration, text, markdown] <br>\n**Output Format:** [Markdown guidance with inline commands and tool names] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Read-first industrial protocol workflow guidance; no generated files are required by the skill itself.] <br>\n\n## Skill Version(s): <br>\n0.20.3 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\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. <br>","readmeExcerpt":"Skill: iaiops-plcnext Owner: zw008 Summary: PLCnext / virtualized-PLC edition of iaiops — Phoenix Contact PLCnext Control and vPLC (虚拟化 PLC) reached over its built-in OPC-UA server (opc.tcp 4840) and Modbus-TCP process-data server, plus the cross-protocol brain (dataflow diagnosis, downtime root cause, PdM, OEE, alarm, baseline). A packaging edition — no new connector, no PLCnext-vendor SDK: it routes to the standard","codeSnippets":[],"executableExamples":[],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: iaiops-plcnext\ndescription: >-\n  PLCnext / virtualized-PLC edition of iaiops — Phoenix Contact PLCnext Control\n  and vPLC (虚拟化 PLC) reached over its built-in OPC-UA server (opc.tcp 4840) and\n  Modbus-TCP process-data server, plus the cross-protocol brain (dataflow\n  diagnosis, downtime root cause, PdM, OEE, alarm, baseline). A packaging edition\n  — no new connector, no PLCnext-vendor SDK: it routes to the standard OPC-UA and\n  Modbus tools already shipped. Use when the task mentions PLCnext / PLCnext\n  Control / AXC F / vPLC / virtual PLC / 虚拟 PLC / Phoenix Contact controller over\n  OPC-UA or Modbus. Read-first; this edition's tool surface is read-only.\n---\n\n# iaiops-plcnext — PLCnext / vPLC edition（OPC-UA + Modbus + 脑）\n\n启动：`IAIOPS_MCP=plcnext` / `iaiops-mcp-plcnext`（= opcua + modbus + 脑;等价\n`IAIOPS_MCP=opcua,modbus`）。**打包型 edition**:PLCnext Control / vPLC 通过其**内置\nOPC-UA server**(opc.tcp 4840)与 **Modbus-TCP 过程数据 server** 读取 —— 不新增 connector、\n不依赖 PLCnext 厂商 SDK,直接复用已发布的标准 OPC-UA / Modbus 工具 + 跨协议脑。\n\n## 工具\n\n### OPC-UA（只读;PLCnext 内置 OPC-UA server,opc.tcp 4840）\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` — 自动发现 + 语义资产建模;`opcua_health_summary` 阈值分类;\n  `opcua_anomaly_scan` 有界统计异常扫描\n\n### Modbus-TCP（只读;PLCnext 过程数据 server）\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### 跨协议脑（永远随 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- 预测维护：`pdm_forecast`\n- 告警事件聚类：`alarm_event_clusters` — `alarm_bad_actors` 按**来源**排名,回答的是「哪台仪表最吵」,\n  不是「哪个故障最吵」;一个把同一条件写成十种说法的厂会得到十个 bad actor。这个按事件**说了什么**分组。\n  合并规则是**去掉大小写/标点/数字后的精确相等,不是相似度** —— 故意做笨,所以不需要模型、且可核对;\n  每个簇都列出被合并的原文与来源。**它不主张两条措辞不同的告警是同一个故障**,那由人判断。\n- 数据质量：`data_quality_scorecard` `data_quality_fleet_rollup`\n- 分析：`oee_compute` `downtime_events` `oee_multidim` `monitor_changes`\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- 设备公告对照：`d"},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn7b067awq2s97bn3d7p5qfhw5827pxc\",\n  \"slug\": \"iaiops-plcnext\",\n  \"version\": \"0.28.0\",\n  \"publishedAt\": 1789535404966\n}"},{"path":"skill-card.md","content":"## Description:\n\niaiops-plcnext helps agents operate a read-first PLCnext and vPLC monitoring workflow over OPC-UA and Modbus-TCP, with diagnostics, downtime root-cause analysis, PdM, OEE, alarms, baselines, data quality, onboarding, and investigation guidance.\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 industrial engineers use this skill to diagnose, monitor, and analyze Phoenix Contact PLCnext Control and vPLC environments through OPC-UA and Modbus-TCP without adding a PLCnext-specific connector. It supports read-first OT observability, onboarding, root-cause analysis, data-quality, compliance-evidence, and baseline workflows.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill is framed as read-only, but the evidence security summary notes documented export, publish, historian-push, UNS, baseline-persistence, and history functions.\n\nMitigation: Review before production OT installation and require explicit approval, verified destinations, least-privilege credentials, and data-classification checks before using export, publish, historian-push, UNS, baseline, or history functions.\n\nRisk: Using the skill in production OT environments can affect sensitive process data flows even when PLC process access is read-only.\n\nMitigation: Treat PLC process access as read-only, verify all external data destinations, and apply site change-control and approval processes for any workflow that persists, exports, publishes, or pushes data.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/zw008/skills/iaiops-plcnext)\n- [Artifact SKILL.md](artifact/SKILL.md)\n\n## Skill Output:\n\n**Output Type(s):** [guidance, markdown, shell commands, configuration, analysis]\n\n**Output Format:** [Markdown guidance with inline commands, tool names, and configuration snippets]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May produce reports, scorecards, evidence bundles, and configuration drafts for read-first PLCnext/vPLC workflows over OPC-UA and Modbus-TCP.]\n\n## Skill Version(s):\n\n0.28.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."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"PLCnext / virtualized-PLC edition of iaiops — Phoenix Contact PLCnext Control and vPLC (虚拟化 PLC) reached over its built-in OPC-UA server (opc.tcp 4840) and Modbus-TCP process-data server, plus the cross-protocol brain (dataflow diagnosis, downtime root cause, PdM, OEE, alarm, baseline). A packaging edition — no new connector, no PLCnext-vendor SDK: it routes to the standard OPC-UA and Modbus tools already shipped. Use when the task mentions PLCnext / PLCnext Control / AXC F / vPLC / virtual PLC / 虚拟 PLC / Phoenix Contact controller over OPC-UA or Modbus. Read-first; this edition's tool surface is read-only. Skill: iaiops-plcnext Owner: zw008 Summary: PLCnext / virtualized-PLC edition of iaiops — Phoenix Contact PLCnext Control and vPLC (虚拟化 PLC) reached over its built-in OPC-UA server (opc.tcp 4840) and Modbus-TCP process-data server, plus the cross-protocol brain (dataflow diagnosis, downtime root cause, PdM, OEE, alarm, baseline). A packaging edition — no new connector, no PLCnext-vendor SDK: it routes to the standard","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":1313,"uniquenessScore":48,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-10T03:06:09.496Z","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:06:09.496Z","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:42:13.313Z","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"}]}}}