pilot-meeting-assistant-setup

Orchestrates a three-agent workflow for scheduling, note-taking, and action tracking.

7|3|Updated Apr 8, 2026

Search Tags:#automation #workflow #note-taking #meeting-management #action-tracking #pilot-protocol

Ready to run

npx skills add https://github.com/TeoSlayer/pilot-skills --skill pilot-meeting-assistant-setup

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pilot-meeting-assistant-setup
Source: https://github.com/TeoSlayer/pilot-skills/tree/main/skills/pilot-meeting-assistant-setup
Command: npx skills add https://github.com/TeoSlayer/pilot-skills --skill pilot-meeting-assistant-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates a three-agent meeting-management workflow to automate scheduling, note-taking, and action tracking across three roles.

Core Features & Use Cases

Scheduler automates calendar availability, invites, and rescheduling.
Note-taker captures structured meeting notes, decisions, and summaries.
Action-tracker extracts action items, assigns owners, and sends reminders.

Quick Start

Install the three roles with clawhub, assign hostnames for each role, and run the required handshakes to establish trust across scheduler, note-taker, and action-tracker.

Frequently Asked Questions about pilot-meeting-assistant-setup

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

FAQPage Schema

How do I automate meeting scheduling, note-taking, and action tracking across multiple agents?▼

Meeting automation across three roles is orchestrated by a scheduler handling calendar invites, a note-taker capturing structured summaries, and an action-tracker extracting assigned reminders. This workflow establishes end-to-end cross-role communication.

What is the Pilot protocol for cross-role agent communication?▼

The Pilot protocol is a framework establishing secure handshakes and trust across distinct agents. It defines role-specific skills, peer relationships, and data flows so separate roles like scheduler and note-taker can communicate securely.

How do I set up role-specific skills and hostnames using clawhub?▼

To set up role-specific skills, install the three roles via clawhub, assign a unique hostname to each role, and run the required handshakes to establish trust. This generates the setup manifests needed for deployment.

Do I need pilotctl to manage deployment metadata for automated workflows?▼

Yes, pilotctl is integrated to manage the deployment metadata for the three-agent workflow. It works alongside the Pilot protocol to define data flows and ensure secure cross-role communication for the meeting-management process.

Can I use this workflow for action item extraction and automated reminders?▼

Yes, the action-tracker role within the meeting-management workflow specifically extracts action items, assigns owners, and sends automated reminders. This ensures structured action tracking directly follows the note-taking phase.

What are the limitations of a three-agent meeting-management workflow?▼

The three-agent meeting-management workflow requires configuring secure handshakes and assigning distinct hostnames for each role before operation. It is limited to scenarios needing structured cross-role communication via the Pilot protocol.