← Back to Skills Marketplace
Pilot Meeting Assistant Setup
by
Calin Teodor
· GitHub ↗
· v1.0.0
· MIT-0
82
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install pilot-meeting-assistant-setup
Description
Deploy a meeting assistant system with 3 agents. Use this skill when: 1. User wants to set up an automated meeting assistant system 2. User is configuring an...
Usage Guidance
This skill is internally consistent with its stated purpose, but verify a few things before proceeding:
- Confirm pilotctl and clawhub are the official/expected binaries and obtain them from trusted sources; the skill will call these CLIs directly.
- Review each pilot-* skill the setup installs (pilot-cron, pilot-webhook-bridge, pilot-receipt, pilot-stream-data, pilot-share, pilot-archive, pilot-task-router, pilot-alert, pilot-slack-bridge) to learn what credentials or network access they require (Slack tokens, webhook URLs, calendar API keys, etc.). The setup does not itself request those secrets but the installed components may need them.
- Be aware that the handshake behavior auto-approves trust when both sides send a handshake; only perform handshakes with hosts you control or trust to avoid connecting to unknown agents.
- The manifest is stored under ~/.pilot/setups — back up any existing files there if needed and inspect the manifest before starting agents.
- Confirm network exposure and firewall rules for ports mentioned (1002 for agent-to-agent events, 443 for external webhooks), and restrict access as appropriate.
- The skill bundle contains only documentation/instructions (no code); commands are executed only when you run them, so exercise the usual caution when copying/running CLI snippets.
If you want higher assurance, ask the skill author or vendor for the exact requirements of each pilot-* component and for signed/official releases of pilotctl and clawhub.
Capability Analysis
Type: OpenClaw Skill
Name: pilot-meeting-assistant-setup
Version: 1.0.0
The skill bundle provides a legitimate orchestration workflow for deploying a multi-agent meeting assistant system. It uses framework-specific utilities (pilotctl and clawhub) to install dependencies, configure hostnames, and establish communication channels between agents as described in SKILL.md and README.md. No evidence of data exfiltration, unauthorized execution, or malicious prompt injection was found.
Capability Tags
Capability Assessment
Purpose & Capability
The name and description describe deploying three Pilot agents; the skill requires pilotctl and clawhub which are exactly the CLI tools used in the instructions. All required binaries and actions (installing pilot-* skills, setting hostnames, writing manifest to ~/.pilot/setups, performing handshakes) align with the stated goal.
Instruction Scope
Runtime instructions are concrete: ask user for prefix/role, run clawhub install commands, set hostname via pilotctl, write a JSON manifest under ~/.pilot/setups, and perform handshakes. The instructions do not read unrelated files or environment variables, nor do they transmit data to unexpected endpoints beyond the described agent-to-agent and webhook flows.
Install Mechanism
This is an instruction-only skill (no install spec, no code files). No binaries or archives are downloaded by the skill itself, so there is minimal install-risk from the skill bundle. Risk depends on the provenance of the external tools (pilotctl, clawhub) which are invoked by the user.
Credentials
The skill itself requests no environment variables or credentials (declared or used). However, several downstream skills it instructs to install (e.g., pilot-slack-bridge, pilot-webhook-bridge) commonly require external tokens or webhook URLs. The skill does not declare those credential requirements — you should review each pilot-* component before installing to see what secrets/config they will need.
Persistence & Privilege
The skill does not request always:true, does not modify other skills' configs, and only writes a manifest under the user's ~/.pilot/setups directory. It relies on user-run CLI commands; it does not autonomously install or enable itself.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install pilot-meeting-assistant-setup - After installation, invoke the skill by name or use
/pilot-meeting-assistant-setup - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release
Metadata
Frequently Asked Questions
What is Pilot Meeting Assistant Setup?
Deploy a meeting assistant system with 3 agents. Use this skill when: 1. User wants to set up an automated meeting assistant system 2. User is configuring an... It is an AI Agent Skill for Claude Code / OpenClaw, with 82 downloads so far.
How do I install Pilot Meeting Assistant Setup?
Run "/install pilot-meeting-assistant-setup" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Pilot Meeting Assistant Setup free?
Yes, Pilot Meeting Assistant Setup is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Pilot Meeting Assistant Setup support?
Pilot Meeting Assistant Setup is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Pilot Meeting Assistant Setup?
It is built and maintained by Calin Teodor (@teoslayer); the current version is v1.0.0.
More Skills