← Back to Skills Marketplace
ivangdavila

AirDrop

by Iván · GitHub ↗ · v1.0.0 · MIT-0
darwin ✓ Security Clean
275
Downloads
0
Stars
1
Active Installs
1
Versions
Install in OpenClaw
/install airdrop
Description
Send local files to nearby Apple devices through AirDrop with macOS guardrails, staging checks, and automation-friendly workflows.
README (SKILL.md)

When to Use

User wants the agent to send a local file, export, screenshot, log bundle, or review artifact to a nearby Apple device with AirDrop. Agent handles file staging, confirmation, local handoff, and mode selection between direct AppKit launch and Shortcut fallback.

Requirements

  • macOS with AirDrop enabled in Finder.
  • Nearby Apple recipient available and visible to the current Mac.
  • Direct mode uses xcrun swift or swift to run airdrop-send.swift.
  • Shortcut mode uses the built-in shortcuts CLI and a user-owned shortcut that accepts file input.

Architecture

Memory lives in ~/airdrop/. If ~/airdrop/ does not exist, run setup.md. See memory-template.md for structure.

~/airdrop/
|- memory.md          # Activation and confirmation preferences
`- staging/           # Optional user-approved temp exports before sharing

Quick Reference

Topic File
First-run behavior and activation setup.md
Memory structure memory-template.md
Direct CLI wrapper airdrop-send.sh
AppKit AirDrop launcher airdrop-send.swift
Common execution patterns workflow-recipes.md
Recovery and diagnostics troubleshooting.md

Core Rules

1. Resolve Exact Files Before Sharing

  • Work only with explicit local file paths.
  • For generated text or mixed output, stage to a user-approved file first, then share that file.
  • Refuse vague requests like "send the project" until the exact payload is listed.

2. Use the Smallest Safe Payload

  • Prefer the exact artifact the recipient needs: one PDF, one ZIP, one screenshot set, one installer.
  • When the source is a directory, curate or archive the approved subset before launch.
  • Treat hidden files, secrets, and unrelated workspace state as excluded by default.

3. Keep Recipient Choice Interactive

  • AirDrop recipient selection stays in the macOS share UI.
  • Do not claim silent recipient targeting, background delivery, or machine-verifiable recipient identity.
  • If the user wants zero-click routing, use Shortcut mode only when they already built that behavior locally.

4. Pick the Right Execution Mode

  • Default to airdrop-send.sh for direct local handoff because it launches the native AirDrop sharing service without inventing unsupported CLI verbs.
  • Use Shortcut mode when the user already has a Shortcut that renames, compresses, or routes files before AirDrop.
  • If swift is unavailable, fall back to the user's Shortcut flow or stop with a concrete requirement message.

5. Confirm Sensitive Shares

  • Before launching AirDrop for logs, source bundles, contracts, exports, or anything private, list the exact files and ask for confirmation.
  • If the user says "only the final artifact", strip extras before sharing.
  • Never include credential files, env files, database dumps, or hidden config unless the user explicitly requests them.

6. Report Handoff Honestly

  • Success means the AirDrop chooser launched with the requested files.
  • Do not say the transfer completed unless the user confirms it on-device.
  • If launch succeeds but the device does not appear, route to troubleshooting.md instead of retrying blindly.

Common Traps

Trap Why It Fails Better Move
Treating AirDrop like scp No stable official recipient CLI targeting Launch native chooser and keep recipient selection interactive
Sending raw text directly AirDrop works on shareable items, not vague chat content Write the text to a file, then share that file
Sharing whole folders by reflex Leaks unrelated files and slows discovery Zip or curate the exact approved subset first
Claiming delivery success too early Launching the chooser is not transfer confirmation Report "handoff started" until the user confirms receipt
Retrying with the same bad payload Hidden files or unsupported items keep failing Reduce to one known-good file and retry once

Data Storage

This skill can operate with no persistent local state. If the user wants repeatable behavior, store only activation, confirmation, and staging preferences in ~/airdrop/memory.md. Create ~/airdrop/staging/ only with user approval when temporary share files are useful.

Security & Privacy

Data that stays local:

  • Skill memory and optional staging files in ~/airdrop/
  • The source files until the user chooses a nearby AirDrop recipient

Data that may leave your machine:

  • Only the specific files the user approved for AirDrop
  • Discovery and transfer metadata handled by macOS AirDrop services with nearby Apple devices

This skill does NOT:

  • Upload files to undeclared cloud services
  • Select recipients silently in the background
  • Confirm transfer completion without user-visible evidence
  • Read or share files outside the approved payload list

Related Skills

Install with clawhub install \x3Cslug> if user confirms:

  • macos - General macOS command workflows, permissions checks, and native app automation patterns.
  • applescript - Finder and app automation when AirDrop workflows need UI scripting around local files.
  • files - File selection, packaging, renaming, and cleanup before sharing the final payload.
  • photos - Exporting and converting image assets before sending them to another Apple device.

Feedback

  • If useful: clawhub star airdrop
  • Stay updated: clawhub sync
Usage Guidance
This skill appears to do what it says: stage explicit local files and launch the native macOS AirDrop chooser. Before installing, verify the package source (the registry lists an unknown source and a homepage), and ensure you trust that origin. Note the small metadata omission: SKILL.md expects xcrun/swift or the shortcuts CLI but the registry metadata doesn't declare required binaries; if you rely on direct mode, ensure Xcode Command Line Tools (swift) is installed, or use the shortcuts fallback if you already have a trusted Shortcut. If you decline persistence, do not create ~/airdrop/ (the skill documents how to operate session-only). If you want extra assurance, review the two included files (airdrop-send.sh and airdrop-send.swift) yourself — they only validate passed file paths and invoke macOS sharing APIs or the Shortcuts CLI and do not contact external endpoints.
Capability Analysis
Type: OpenClaw Skill Name: airdrop Version: 1.0.0 The 'airdrop' skill is a legitimate utility designed to facilitate file sharing between macOS devices using the native AirDrop sharing service. It utilizes a Swift script (airdrop-send.swift) to invoke the standard NSSharingService UI and a shell wrapper (airdrop-send.sh) for validation, ensuring that recipient selection remains interactive and under the user's control. The instructions in SKILL.md and setup.md emphasize security guardrails, such as requiring explicit confirmation for sensitive files and refusing to store secrets or recipient identities.
Capability Assessment
Purpose & Capability
The skill's name, description, and files (shell wrapper + Swift AppKit launcher) match the stated purpose of launching the macOS AirDrop chooser for local files. One mild inconsistency: the SKILL.md requires either xcrun/swift or the shortcuts CLI for fallback, but the registry metadata does not list any required binaries. This is plausibly an editorial omission rather than malicious behavior.
Instruction Scope
Runtime instructions restrict the agent to explicit local file paths, staging under ~/airdrop/ only with user consent, interactive recipient selection via macOS UI, and explicit confirmation before sharing sensitive files. The included scripts only read provided file paths and call native macOS sharing APIs or the user-owned Shortcuts CLI; they do not read unrelated system files or environment variables.
Install Mechanism
There is no install spec (instruction-only skill) and the shipped code is small and local (airdrop-send.sh and a Swift helper). No network downloads or archive extraction are performed by an installer. This is low-risk compared with skills that fetch remote code at install time.
Credentials
The skill requests no environment variables, no credentials, and only an optional local memory directory (~/airdrop/) for persistent preferences. That local storage is aligned with the described purpose and is limited to preferences and staging; the documentation explicitly forbids storing recipient identifiers or file contents by default.
Persistence & Privilege
The skill does not request always-on presence and does not modify other skills. Its optional persistence is limited to a user-controlled ~/airdrop/ directory. The agent would only write there with user approval per the documentation.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install airdrop
  3. After installation, invoke the skill by name or use /airdrop
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release with direct AirDrop launch, shortcut fallback, and safer file-sharing guardrails for nearby Apple devices.
Metadata
Slug airdrop
Version 1.0.0
License MIT-0
All-time Installs 1
Active Installs 1
Total Versions 1
Frequently Asked Questions

What is AirDrop?

Send local files to nearby Apple devices through AirDrop with macOS guardrails, staging checks, and automation-friendly workflows. It is an AI Agent Skill for Claude Code / OpenClaw, with 275 downloads so far.

How do I install AirDrop?

Run "/install airdrop" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is AirDrop free?

Yes, AirDrop is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does AirDrop support?

AirDrop is cross-platform and runs anywhere OpenClaw / Claude Code is available (darwin).

Who created AirDrop?

It is built and maintained by Iván (@ivangdavila); the current version is v1.0.0.

💬 Comments