Skip to content

TeoSlayer/pilot-skills / skills/pilot-dropbox

pilot-dropbox

Verified

Shared folder that automatically synchronizes between peers using Pilot Protocol pub/sub. Use this skill when: 1. You need a persistent shared folder that stays in sync across agents 2. You want automatic file synchronization without manual intervention 3. You need multi-peer folder sharing with eventual consistency Do NOT use this skill when: - You only need one-time file transfer (use pilot-share instead) - You need strict consistency guarantees (use pilot-sync with locks) - You need real-time streaming (use pilot-stream-data instead)

FileKindSize
README.mdmarkdown724 B
SKILL.mdskill md3.3 KB
---
name: pilot-dropbox
description: >
  Shared folder that automatically synchronizes between peers using Pilot Protocol pub/sub.

  Use this skill when:
  1. You need a persistent shared folder that stays in sync across agents
  2. You want automatic file synchronization without manual intervention
  3. You need multi-peer folder sharing with eventual consistency

  Do NOT use this skill when:
  - You only need one-time file transfer (use pilot-share instead)
  - You need strict consistency guarantees (use pilot-sync with locks)
  - You need real-time streaming (use pilot-stream-data instead)
tags:
  - pilot-protocol
  - file-transfer
  - shared-folder
  - pub-sub
license: AGPL-3.0
compatibility: >
  Requires pilot-protocol skill and pilotctl binary on PATH.
  The daemon must be running (pilotctl daemon start).
metadata:
  author: vulture-labs
  version: "1.0"
  openclaw:
    requires:
      bins:
        - pilotctl
    homepage: https://pilotprotocol.network
allowed-tools:
  - Bash
---

# pilot-dropbox

Shared folder implementation using Pilot Protocol pub/sub and file transfer. Provides Dropbox-like functionality with eventual consistency.

## Essential Commands

### Create and join shared folder
```bash
DROPBOX_DIR="$HOME/pilot-dropbox"
PEER="agent-b"
TOPIC="team-shared"
mkdir -p "$DROPBOX_DIR"

pilotctl --json subscribe "$PEER" "$TOPIC"
```

### Publish file to folder
```bash
cp "$FILE" "$DROPBOX_DIR/"
FILENAME=$(basename "$FILE")
HASH=$(md5sum "$DROPBOX_DIR/$FILENAME" | cut -d' ' -f1)

pilotctl --json publish "$PEER" "$TOPIC" \
  --data "{\"type\":\"file_added\",\"filename\":\"$FILENAME\",\"hash\":\"$HASH\"}"
```

### Remove file from folder
```bash
rm "$DROPBOX_DIR/$FILENAME"
pilotctl --json publish "$PEER" "$TOPIC" \
  --data "{\"type\":\"file_removed\",\"filename\":\"$FILENAME\"}"
```

### Watch folder for changes
```bash
fswatch -0 "$DROPBOX_DIR" | while read -d "" changed_file; do
  [ -f "$changed_file" ] || continue
  FILENAME=$(basename "$changed_file")
  HASH=$(md5sum "$changed_file" | cut -d' ' -f1)
  pilotctl --json publish "$PEER" "$TOPIC" \
    --data "{\"type\":\"file_changed\",\"filename\":\"$FILENAME\",\"hash\":\"$HASH\"}"
done &
```

## Workflow Example

Shared folder daemon:

```bash
#!/bin/bash
DROPBOX_DIR="$HOME/pilot-dropbox"
PEER="${1:-agent-b}"
TOPIC="team-shared"

mkdir -p "$DROPBOX_DIR"

# Listen for events
pilotctl --json subscribe "$PEER" "$TOPIC" | while read -r event; do
  TYPE=$(echo "$event" | jq -r '.type')
  FROM=$(echo "$event" | jq -r '.from')

  case "$TYPE" in
    file_added)
      FILENAME=$(echo "$event" | jq -r '.filename')
      HASH=$(echo "$event" | jq -r '.hash')

      if [ -f "$DROPBOX_DIR/$FILENAME" ]; then
        LOCAL_HASH=$(md5sum "$DROPBOX_DIR/$FILENAME" | cut -d' ' -f1)
        [ "$LOCAL_HASH" = "$HASH" ] && continue
      fi

      echo "Pulling: $FILENAME from $FROM"
      pilotctl --json send-message "$FROM" \
        --data "{\"type\":\"dropbox_pull\",\"filename\":\"$FILENAME\"}"
      ;;

    file_removed)
      FILENAME=$(echo "$event" | jq -r '.filename')
      rm -f "$DROPBOX_DIR/$FILENAME"
      ;;

    dropbox_pull)
      FILENAME=$(echo "$event" | jq -r '.filename')
      pilotctl --json send-file "$FROM" "$DROPBOX_DIR/$FILENAME"
      ;;
  esac
done
```

## Dependencies

Requires `pilot-protocol` skill, `pilotctl`, `jq`, `fswatch` (macOS) or `inotifywait` (Linux), and file utilities.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall