Pilot Inbox

v1.0.0

Unified inbox for all incoming items — messages, files, tasks, and trust requests in one view. Use this skill when: 1. You need to check all incoming items a...

0· 140·0 current·0 all-time
byCalin Teodor@teoslayer

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for teoslayer/pilot-inbox.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Pilot Inbox" (teoslayer/pilot-inbox) from ClawHub.
Skill page: https://clawhub.ai/teoslayer/pilot-inbox
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required binaries: pilotctl
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install pilot-inbox

ClawHub CLI

Package manager switcher

npx clawhub@latest install pilot-inbox
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description map to the actions performed by the instructions (listing inbox items, files, tasks, and trust requests via pilotctl). Required capability (pilotctl + running daemon) is appropriate for a Pilot Protocol inbox skill.
Instruction Scope
Instructions are narrowly scoped to running pilotctl and parsing JSON with jq. They include destructive commands (pilotctl ... --clear) which match the claimed 'clear inbox' functionality. The SKILL.md references jq for JSON parsing but jq is not declared in the registry's required binaries list — a minor inconsistency to fix.
Install Mechanism
Instruction-only skill with no install spec and no code files — nothing is written to disk by the skill itself. Low install risk.
Credentials
The skill does not request environment variables or credentials. The commands operate via the pilotctl binary and a running daemon; this is proportionate to the stated purpose.
Persistence & Privilege
always is false and the skill does not request persistent agent-wide privileges or modify other skills. The default ability for the agent to invoke the skill autonomously is unchanged and is reasonable for this functionality.
Assessment
This skill appears coherent for viewing and triaging Pilot Protocol inbox items, but check a few things before installing: (1) Ensure pilotctl is a trusted binary and up-to-date (verify its source and checksum); (2) Install or confirm jq on PATH (SKILL.md uses it but the registry metadata doesn't list it); (3) Be aware that pilotctl --clear is destructive — the agent running this skill could delete items if asked to; (4) Confirm the Pilot Protocol daemon is running and that you intend to grant that local access to the agent; (5) If you need the skill to run automatically, remember autonomous invocation is allowed by default — restrict if you don't want the agent to execute these commands without your approval.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

Binspilotctl
latestvk9757db6f6pwbwzkgm3hjs1hkd84h542
140downloads
0stars
1versions
Updated 2w ago
v1.0.0
MIT-0

pilot-inbox

Unified inbox for all incoming items across the Pilot Protocol network. This skill provides a single view of messages, files, tasks, and trust requests, enabling efficient triage and prioritization.

Essential Commands

View all inbox items

pilotctl --json inbox

Check specific item types

# Messages in inbox
pilotctl --json inbox

# Files received
pilotctl --json received

# Tasks received
pilotctl --json task list --type received

# Trust requests pending
pilotctl --json pending

Clear inbox

# Clear all inbox items
pilotctl --json inbox --clear

# Clear received files
pilotctl --json received --clear

Workflow Example

Morning inbox triage:

#!/bin/bash
# inbox-triage.sh

echo "=== PILOT INBOX TRIAGE ==="

# Check inbox
INBOX=$(pilotctl --json inbox)
echo "Inbox:"
echo "$INBOX" | jq -r '.items[]? | "  [\(.timestamp)] \(.type): \(.content)"' | head -5

# Check received files
FILES=$(pilotctl --json received)
FILE_COUNT=$(echo "$FILES" | jq '.files | length // 0')
echo "Files: $FILE_COUNT"

# Check tasks
TASKS=$(pilotctl --json task list --type received)
TASK_COUNT=$(echo "$TASKS" | jq '.tasks | length // 0')
echo "Tasks: $TASK_COUNT"

# Check trust requests
TRUST=$(pilotctl --json pending)
TRUST_COUNT=$(echo "$TRUST" | jq '.requests | length // 0')
echo "Trust Requests: $TRUST_COUNT"

if [ "$TRUST_COUNT" -gt 0 ]; then
  echo "Pending Trust Requests:"
  echo "$TRUST" | jq -r '.requests[]? | "  - \(.node_id)"'
fi

Dependencies

Requires pilot-protocol skill, pilotctl binary on PATH, running daemon, and jq for JSON parsing.

Comments

Loading comments...