pilot-inbox

Centralize messages, files, and trust requests into a unified inbox.

7|3|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/TeoSlayer/pilot-skills --skill pilot-inbox
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pilot-inbox
Source: https://github.com/TeoSlayer/pilot-skills/tree/main/skills/pilot-inbox
Command: npx skills add https://github.com/TeoSlayer/pilot-skills --skill pilot-inbox

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Centralized inbox for messages, files, and trust requests
  • Quick triage and prioritization of inbound items across channels
  • Unified view to manage workflows including messaging, file reception, and trust requests

Quick Start

Install the pilot-inbox skill to enable the unified inbox across your agent.

Frequently Asked Questions about pilot-inbox

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I centralize messages, files, and trust requests into a single inbox?

You can centralize messages, files, and trust requests by using a unified inbox that aggregates incoming items across the Pilot Protocol network for simplified triage and prioritization.

How do I triage incoming items across the Pilot Protocol network?

Triage incoming items across the Pilot Protocol network by viewing messages, received files, and pending trust requests in a single centralized inbox for quick prioritization.

Do I need the pilotctl binary on PATH to manage trust requests?

Yes, managing trust requests requires the pilotctl binary on PATH, an active daemon, and the pilot-protocol skill to run triage workflows across the network.

What's the best way to unify messaging and file reception workflows for agents?

Unify messaging and file reception workflows by centralizing all inbound items into a single view, enabling efficient triage and prioritization across multiple communication channels.

Are there limitations when centralizing inbox items if the daemon is inactive?

If the daemon is inactive, centralized inbox triage will not work because the skill requires pilotctl running and an active daemon to process items safely with validation and safe defaults.