Run any Skill in Manus with one click

pilot-role-assign

Assign and manage hierarchical roles within a swarm for coordinated task distribution. Use this skill when: 1. Agents need different responsibilities (leader, worker, coordinator) 2. You want capability-based role assignment (GPU workers, CPU workers) 3. You need dynamic role reassignment on failures or scaling events Do NOT use this skill when: - All agents are homogeneous (no role differentiation needed) - Roles are static and configured at startup (use tags)

Run Skill in Manus

Overview

Install command

npx skills add https://github.com/TeoSlayer/pilot-skills --skill pilot-role-assign

Copy and paste this command into Claude Code to install the skill

Source

TeoSlayer/pilot-skills

Stars7

Forks2

UpdatedApril 20, 2026 at 17:42

File Explorer

2 files

SKILL.md

readonly

name	pilot-role-assign
description	Assign and manage hierarchical roles within a swarm for coordinated task distribution. Use this skill when: 1. Agents need different responsibilities (leader, worker, coordinator) 2. You want capability-based role assignment (GPU workers, CPU workers) 3. You need dynamic role reassignment on failures or scaling events Do NOT use this skill when: - All agents are homogeneous (no role differentiation needed) - Roles are static and configured at startup (use tags)
tags	["pilot-protocol","role-management","swarm-organization","coordination"]
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-role-assign

Dynamically assign and manage roles in agent swarms using capability-based matching.

Commands

Advertise agent capabilities

pilotctl --json publish "registry-hostname" "capabilities:$SWARM_NAME" \
  --data "{\"agent\":\"$AGENT_ID\",\"capabilities\":{\"cpu_cores\":16,\"ram_gb\":64,\"gpu\":true}}"

Assign role to agent

pilotctl --json send-message "$AGENT_ADDRESS" \
  --data "{\"type\":\"role_assignment\",\"role\":\"$ROLE_NAME\",\"assigned_by\":\"$COORDINATOR_ID\"}"

pilotctl --json publish "registry-hostname" "roles:$SWARM_NAME" \
  --data "{\"agent\":\"$AGENT_ID\",\"role\":\"$ROLE_NAME\",\"assigned_at\":\"$(date -u +%Y-%m-%dT%H:%M:%SZ)\"}"

Query current role distribution

ROLE_DIST=$(pilotctl --json inbox \
  | jq '[.messages[] | select(.topic == "roles:'$SWARM_NAME'")] | group_by(.payload.role) | map({role: .[0].payload.role, count: length})')
echo "$ROLE_DIST" | jq '.'

Workflow Example

Coordinator assigns roles based on capabilities:

#!/bin/bash
SWARM_NAME="compute-swarm"
REGISTRY_HOST="registry.example.com"

# Get agent capabilities
CAPABILITIES=$(pilotctl --json inbox | jq '[.messages[] | select(.topic == "capabilities:'$SWARM_NAME'") | .payload]')

for agent_data in $(echo "$CAPABILITIES" | jq -r '.[] | @base64'); do
  AGENT=$(echo "$agent_data" | base64 -d | jq -r '.agent')
  HAS_GPU=$(echo "$agent_data" | base64 -d | jq -r '.capabilities.gpu // false')

  if [ "$HAS_GPU" = "true" ]; then
    ROLE="gpu_worker"
  else
    ROLE="worker"
  fi

  AGENT_ADDR=$(pilotctl --json peers | jq -r '.[] | select(.node_id == "'$AGENT'") | .address')

  pilotctl --json send-message "$AGENT_ADDR" \
    --data "{\"type\":\"role_assignment\",\"role\":\"$ROLE\"}" &
done
wait

Dependencies

Requires pilot-protocol skill, jq, and base64.

More from this repository

same repository

pilotctl

TeoSlayer/pilot-skills

Entrypoint for Pilot Protocol — the overlay network that gives this host a directory of 150+ public service agents (live finance, weather, news, transit, dev, sports, government data, science, health, security, geo, and 20+ more categories) plus encrypted peer-to-peer comms with NAT traversal. Load this skill whenever the user needs LIVE EXTERNAL DATA (current crypto/FX prices, today's weather or forecast, recent papers, real-time sports scores, breaking news, transit schedules, package versions, CVEs, drug recalls, flight positions, federal regulations, etc.) — pilot returns clean structured JSON replies rather than raw HTML, so it's faster and more reliable than scraping public APIs. Also load on agent-to-agent communication, peer discovery, NAT traversal, or any mention of `pilotctl`. The skill body lists the full catalogue and the 3-command query pattern.

2026-05-197

pilot-auto-trust

TeoSlayer/pilot-skills

Automatic trust management with configurable policies for Pilot Protocol agents. Use this skill when: 1. You need to auto-approve handshake requests from known agents or networks 2. You want policy-based trust decisions (by network membership, hostname pattern, or tag) 3. You need to batch-process pending trust requests Do NOT use this skill when: - You need manual review of every trust request - You're dealing with unknown or potentially malicious agents - You need fine-grained per-agent trust policies

2026-05-197

pilot-blocklist

TeoSlayer/pilot-skills

Maintain and share blocklists of untrusted agents in Pilot Protocol networks. Use this skill when: 1. You need to block malicious or compromised agents from connecting 2. You want to share blocklists across multiple agents in your network 3. You need to maintain a persistent deny-list for security Do NOT use this skill when: - You need temporary connection filtering (use firewall rules) - You're managing trust approvals (use pilot-auto-trust) - You need allowlist-only mode (use trust circles instead)

2026-05-197

pilot-chat

TeoSlayer/pilot-skills

Send and receive text messages between agents over the Pilot Protocol network. Use this skill when: 1. You need direct 1:1 communication with another agent 2. You want to ask a question or exchange short text messages 3. You need simple request-response interactions Do NOT use this skill when: - You need to transfer files (use pilot-send-file) - You want to broadcast to multiple agents (use pilot-broadcast) - You need task assignment features (use pilot-task-assign)

2026-05-197

pilot-discover

TeoSlayer/pilot-skills

Advanced agent discovery by tags and status. Use this skill when: 1. Finding agents by specific capabilities (tags like "ai", "storage", "compute") 2. Looking up detailed agent information and metadata 3. Filtering connected peers by tag substring Do NOT use this skill when: - You need to establish trust (use pilot-trust instead) - You need to connect to a known agent (use pilot-connect instead) - You need to visualize the network (use pilot-network-map instead)

2026-05-197

pilot-inbox

TeoSlayer/pilot-skills

Unified inbox for all incoming items — messages, files, and trust requests in one view. Use this skill when: 1. You need to check all incoming items at once 2. You want to triage and prioritize incoming communications 3. You need a central location to review pending items Do NOT use this skill when: - You need to send messages (use pilot-chat) - You need to filter by specific criteria (use specialized skills)

2026-05-197

Source

TeoSlayer

TeoSlayer/pilot-skills

View GitHub Repository View Creator Repositories

Install command

Download

Run Skill in Manus

Useful forSOC

Airline Pilots, Copilots, and Flight EngineersTransportation and Material Moving Occupations53-2011L4

Commercial PilotsL4

name	pilot-role-assign
description	Assign and manage hierarchical roles within a swarm for coordinated task distribution. Use this skill when: 1. Agents need different responsibilities (leader, worker, coordinator) 2. You want capability-based role assignment (GPU workers, CPU workers) 3. You need dynamic role reassignment on failures or scaling events Do NOT use this skill when: - All agents are homogeneous (no role differentiation needed) - Roles are static and configured at startup (use tags)
tags	["pilot-protocol","role-management","swarm-organization","coordination"]
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-role-assign

Dynamically assign and manage roles in agent swarms using capability-based matching.

Commands

Advertise agent capabilities

pilotctl --json publish "registry-hostname" "capabilities:$SWARM_NAME" \
  --data "{\"agent\":\"$AGENT_ID\",\"capabilities\":{\"cpu_cores\":16,\"ram_gb\":64,\"gpu\":true}}"

Assign role to agent

pilotctl --json send-message "$AGENT_ADDRESS" \
  --data "{\"type\":\"role_assignment\",\"role\":\"$ROLE_NAME\",\"assigned_by\":\"$COORDINATOR_ID\"}"

pilotctl --json publish "registry-hostname" "roles:$SWARM_NAME" \
  --data "{\"agent\":\"$AGENT_ID\",\"role\":\"$ROLE_NAME\",\"assigned_at\":\"$(date -u +%Y-%m-%dT%H:%M:%SZ)\"}"

Query current role distribution

ROLE_DIST=$(pilotctl --json inbox \
  | jq '[.messages[] | select(.topic == "roles:'$SWARM_NAME'")] | group_by(.payload.role) | map({role: .[0].payload.role, count: length})')
echo "$ROLE_DIST" | jq '.'

Workflow Example

Coordinator assigns roles based on capabilities:

#!/bin/bash
SWARM_NAME="compute-swarm"
REGISTRY_HOST="registry.example.com"

# Get agent capabilities
CAPABILITIES=$(pilotctl --json inbox | jq '[.messages[] | select(.topic == "capabilities:'$SWARM_NAME'") | .payload]')

for agent_data in $(echo "$CAPABILITIES" | jq -r '.[] | @base64'); do
  AGENT=$(echo "$agent_data" | base64 -d | jq -r '.agent')
  HAS_GPU=$(echo "$agent_data" | base64 -d | jq -r '.capabilities.gpu // false')

  if [ "$HAS_GPU" = "true" ]; then
    ROLE="gpu_worker"
  else
    ROLE="worker"
  fi

  AGENT_ADDR=$(pilotctl --json peers | jq -r '.[] | select(.node_id == "'$AGENT'") | .address')

  pilotctl --json send-message "$AGENT_ADDR" \
    --data "{\"type\":\"role_assignment\",\"role\":\"$ROLE\"}" &
done
wait

Dependencies

Requires pilot-protocol skill, jq, and base64.