How do I install the Pilot Role Assign skill?

Run npx skillmds@latest add teoslayer/pilot-role-assign in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Pilot Role Assign safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pilot Role Assign?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pilot Role Assign free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under AGPL-3.

Who published Pilot Role Assign?

TeoSlayer (@teoslayer) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pilot Role Assign by teoslayer — Agent Skill

Name: Pilot Role Assign
Author: TeoSlayer

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)

TeoSlayer c64851c 2 files · 3.0 KB Updated Sep 17, 2026

File contents

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.

---name: pilot-role-assigndescription: 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)license: AGPL-3.0---# pilot-role-assignDynamically assign and manage roles in agent swarms using capability-based matching.## Commands### Advertise agent capabilities```bashpilotctl --json publish "registry-hostname" "capabilities:$SWARM_NAME" \ --data "{\"agent\":\"$AGENT_ID\",\"capabilities\":{\"cpu_cores\":16,\"ram_gb\":64,\"gpu\":true}}"```### Assign role to agent```bashpilotctl --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```bashROLE_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 ExampleCoordinator assigns roles based on capabilities:```bash#!/bin/bashSWARM_NAME="compute-swarm"REGISTRY_HOST="registry.example.com"# Get agent capabilitiesCAPABILITIES=$(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\"}" &donewait```## DependenciesRequires pilot-protocol skill, jq, and base64.

Frequently asked questions