360 Secure SkillHub
360 安全技能中心

Pilot Priority Queue

核心功能:基于Pilot协议网络实现消息优先级管理,支持CRITICAL、HIGH、NORMAL、LOW四级标记,确保高紧急度消息优先处理,同优先级消息有序交付。典型场景:需紧急消息处理、SLA交付、消息优先级分流的场景;输入为带优先级前缀的消息,通过pilotctl命令发送;输出可按优先级筛选接收消息。需依赖pilot-protocol技能及pilotctl工具,且守护进程运行。

teoslayer
teoslayer
热度 46.55
最近更新 2026-05-11 17:41:37
分类:协作依赖:代码执行 / 第三方 API应用场景:任务管理 / 工作流

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add pilot-priority-queue
Metadata
name
pilot-priority-queue
description
Priority-based message delivery with urgency levels over the Pilot Protocol network. Use this skill when: 1. You need urgent message handling with priority levels 2. You want to implement SLA-based message delivery 3. You need priority triage for incoming messages Do NOT use this skill when: - All messages have equal priority (use pilot-chat) - You need file transfer (use pilot-send-file) - You need real-time streaming (use pilot-connect)
tags
["pilot-protocol","communication","priority","queue"]
license
AGPL-3.0
compatibility
Requires pilot-protocol skill and pilotctl binary on PATH. The daemon must be running (pilotctl daemon start).
metadata
{"author":"vulture-labs","version":"1.0","openclaw":{"requires":{"bins":["pilotctl"]},"homepage":"https://pilotprotocol.network"}}
allowed-tools
["Bash"]

pilot-priority-queue

Priority-based message delivery with urgency levels over the Pilot Protocol network. This skill enables structured message prioritization, ensuring urgent communications are processed first while maintaining ordered delivery for messages of equal priority.

Commands

Send messages with priority prefix

# Send critical message with [CRITICAL] prefix
pilotctl --json send-message <hostname> --data "[CRITICAL] System alert"

# Send high priority with [HIGH] prefix
pilotctl --json send-message <hostname> --data "[HIGH] Urgent task"

# Send normal message
pilotctl --json send-message <hostname> --data "Regular update"

# Send low priority with [LOW] prefix
pilotctl --json send-message <hostname> --data "[LOW] FYI: Log summary"

Receive and filter by priority

# View all inbox
pilotctl --json inbox

# Filter critical messages using jq
pilotctl --json inbox | jq '.items[]? | select(.content | startswith("[CRITICAL]"))'

# Filter high priority
pilotctl --json inbox | jq '.items[]? | select(.content | startswith("[HIGH]"))'

Manual queue management

# Clear inbox after processing
pilotctl --json inbox --clear

Workflow Example

Process messages by priority with automatic triage:

#!/bin/bash
# Process priority inbox using prefix tags

INBOX=$(pilotctl --json inbox)

# Extract and count by priority prefix
CRITICAL_COUNT=$(echo "$INBOX" | jq '[.items[]? | select(.content | startswith("[CRITICAL]"))] | length')
HIGH_COUNT=$(echo "$INBOX" | jq '[.items[]? | select(.content | startswith("[HIGH]"))] | length')
NORMAL_COUNT=$(echo "$INBOX" | jq '[.items[]? | select(.content | (startswith("[CRITICAL]") or startswith("[HIGH]") or startswith("[LOW]")) | not)] | length')
LOW_COUNT=$(echo "$INBOX" | jq '[.items[]? | select(.content | startswith("[LOW]"))] | length')

echo "Critical: $CRITICAL_COUNT, High: $HIGH_COUNT, Normal: $NORMAL_COUNT, Low: $LOW_COUNT"

# Process critical first
if [ "$CRITICAL_COUNT" -gt 0 ]; then
  echo "CRITICAL MESSAGES:"
  echo "$INBOX" | jq -r '.items[]? | select(.content | startswith("[CRITICAL]")) |
    "[\(.timestamp // "N/A")] \(.content)"'
fi

# Process high priority
if [ "$HIGH_COUNT" -gt 0 ]; then
  echo "HIGH PRIORITY:"
  echo "$INBOX" | jq -r '.items[]? | select(.content | startswith("[HIGH]")) |
    "[\(.timestamp // "N/A")] \(.content)"'
fi

Dependencies

Requires pilot-protocol skill, pilotctl binary, and running daemon.