部署一个包含 4 个智能体(agent)的数字孪生平台。在以下情况下使用该技能: 1. 用户希望为物理资产监控与预测性维护等场景搭建数字孪生系统……
数字双子设置是一项面向实际任务的技能,主要用于部署 4 个代理: 传感器-桥 模型-引擎 异常探测器 和动作计划器. . .;Roles.;
它将相关步骤、工具调用和结果整理方式集中到统一流程中,帮助使用者更快完成目标并减少重复操作。使用时应结合输入条件选择合适的执行方式,核对必要参数、依赖环境与输出内容,并按原始要求处理异常情况。从功能定位来看,该技能强调把分散的操作要求整理成清晰、可复用的处理流程,使用户能够围绕既定目标快速准备输入、选择执行方式并获得结构化结果。实际使用前应先确认任务范围、数据来源、运行环境、必要权限和关键参数,再依据技能说明逐步执行;
若输入条件不完整,应先补齐信息或采用保守配置,避免因错误假设导致结果偏离需求。执行过程中需要关注工具调用是否成功、接口或依赖是否可用、输出格式是否符合预期,并对异常提示、缺失字段和边界情况进行处理;涉及批量任务时,还应保存进度,避免中断后重复操作。该技能适合用于一次性任务,也可以接入自动化工作流,与其他技能或上层代理配合完成更完整的业务链路;在组合使用时,应明确每一步的输入输出关系,并避免不同步骤之间出现参数冲突。
部署 4 个智能体:sensor-bridge、model-engine、anomaly-detector 和 action-planner。
| 角色 | 主机名 | 能力(Skills) | 用途 |
|---|---|---|---|
| sensor-bridge | |
pilot-stream-data、pilot-metrics、pilot-gossip | 从物理资产实时采集遥测数据 |
| model-engine | |
pilot-dataset、pilot-task-router、pilot-consensus | 维护物理模型,运行仿真任务 |
| anomaly-detector | |
pilot-event-filter、pilot-alert、pilot-audit-log | 检测实际行为与预测行为之间的偏差(drift) |
| action-planner | |
pilot-webhook-bridge、pilot-cron、pilot-slack-bridge | 调度维护任务,并向现场团队发送通知 |
步骤 1: 向用户询问该智能体应承担的角色及所用前缀(prefix)。
步骤 2: 为选定角色安装对应的能力(skills):
# sensor-bridge: clawhub install pilot-stream-data pilot-metrics pilot-gossip # model-engine: clawhub install pilot-dataset pilot-task-router pilot-consensus # anomaly-detector: clawhub install pilot-event-filter pilot-alert pilot-audit-log # action-planner: clawhub install pilot-webhook-bridge pilot-cron pilot-slack-bridge
步骤 3: 设置主机名,并将配置清单(manifest)写入 ~/.pilot/setups/digital-twin.json。
步骤 4: 告知用户需与其角色对应的对等节点(peers)发起握手(handshake)。
{
"setup": "digital-twin", "role": "sensor-bridge", "role_name": "Sensor Bridge",
"hostname": "-sensor-bridge",
"skills": {
"pilot-stream-data": "Ingest real-time sensor telemetry from physical assets.",
"pilot-metrics": "Track sensor health, sampling rates, and data quality.",
"pilot-gossip": "Discover and sync with peer sensor bridges."
},
"data_flows": [{ "direction": "send", "peer": "-model-engine", "port": 1002, "topic": "telemetry", "description": "Unified telemetry stream from physical assets" }],
"handshakes_needed": ["-model-engine"]
}
{
"setup": "digital-twin", "role": "model-engine", "role_name": "Model Engine",
"hostname": "-model-engine",
"skills": {
"pilot-dataset": "Store physics model parameters and simulation state.",
"pilot-task-router": "Route simulation tasks across asset models.",
"pilot-consensus": "Reconcile model state across redundant engines."
},
"data_flows": [
{ "direction": "receive", "peer": "-sensor-bridge", "port": 1002, "topic": "telemetry", "description": "Real-time sensor data" },
{ "direction": "send", "peer": "-anomaly-detector", "port": 1002, "topic": "prediction", "description": "Expected behavior baselines and drift metrics" }
],
"handshakes_needed": ["-sensor-bridge", "-anomaly-detector"]
}
{
"setup": "digital-twin", "role": "anomaly-detector", "role_name": "Anomaly Detector",
"hostname": "-anomaly-detector",
"skills": {
"pilot-event-filter": "Filter predictions by drift threshold and severity.",
"pilot-alert": "Emit anomaly alerts for critical deviations.",
"pilot-audit-log": "Log all detected anomalies with evidence snapshots."
},
"data_flows": [
{ "direction": "receive", "peer": "-model-engine", "port": 1002, "topic": "prediction", "description": "Model predictions to compare" },
{ "direction": "send", "peer": "-action-planner", "port": 1002, "topic": "anomaly-alert", "description": "Anomaly alerts with severity and root cause" }
],
"handshakes_needed": ["-model-engine", "-action-planner"]
}
{
"setup": "digital-twin", "role": "action-planner", "role_name": "Action Planner",
"hostname": "-action-planner",
"skills": {
"pilot-webhook-bridge": "Push maintenance orders to field team systems.",
"pilot-cron": "Schedule maintenance windows during low-impact periods.",
"pilot-slack-bridge": "Notify operations teams of recommended interventions."
},
"data_flows": [
{ "direction": "receive", "peer": "-anomaly-detector", "port": 1002, "topic": "anomaly-alert", "description": "Anomaly alerts to act on" },
{ "direction": "send", "peer": "external", "port": 443, "topic": "maintenance-order", "description": "Work orders to field management systems" }
],
"handshakes_needed": ["-anomaly-detector"]
}
sensor-bridge → model-engine:来自物理资产的实时遥测数据(端口 1002)model-engine → anomaly-detector:预测结果与预期行为基线(端口 1002)anomaly-detector → action-planner:含严重等级与根因分析的异常告警(端口 1002)action-planner → external:下发至现场团队系统的维护工单(端口 443)# 在 sensor-bridge 上 —— 推送遥测数据: pilotctl --json publish-model-engine telemetry '{"asset_id":"PUMP-A7","sensors":{"temperature_c":87.3,"vibration_mm_s":4.2}}' # 在 model-engine 上 —— 发送预测结果: pilotctl --json publish -anomaly-detector prediction '{"asset_id":"PUMP-A7","drift_pct":{"temperature":6.3,"vibration":50.0}}' # 在 anomaly-detector 上 —— 向 action-planner 发送告警: pilotctl --json publish -action-planner anomaly-alert '{"asset_id":"PUMP-A7","severity":"warning","anomaly_type":"bearing_degradation"}'
需具备 pilot-protocol 能力、pilotctl 可执行文件、clawhub 可执行文件,以及一个正在运行的守护进程(daemon)。