How do I install the Osmo skill?

Run npx skillmds@latest add crafter-station/osmo in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Osmo skill do?

Operate the local-first DJI Osmo Nano import CLI safely and with machine-readable receipts. It is listed under Coding & Dev Tools on SkillMD.

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Osmo?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

crafter-station (@crafter-station) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Osmo by crafter-station — Agent Skill

Name: Osmo
Author: crafter-station

File contents

osmo

Use this skill when a DJI Osmo Nano is connected to macOS in USB file-transfer mode.

Contract

Captured stdout is JSON automatically.
Success is {schemaVersion, ok, command, data, meta.nextSteps}.
Errors include {code, message, hint} and a nonzero exit code.
Inspect live schemas with osmo schema [operation] --json.
Pass --volume <path> only when automatic discovery does not select the intended mount.

Workflow

Run osmo doctor --json.
Run osmo device status --json.
Review with osmo media list --json or osmo media inspect latest --json.
Preview with osmo import plan --dest <path> --json.
Stop if conflictFiles is not zero.
Import with the same filters using osmo import run --dest <path> --json.
Confirm copied files and receiptId in the result.
Eject with osmo device eject --json only after all file work is complete.

Boundaries

Never treat LRF files as originals. Add --include-proxies only when proxies are wanted.
Never delete source media through shell commands as part of this workflow.
Do not claim the CLI can change recording settings, microphone routing, firmware, or DJI Mimo state.
A suspect timestamp must not be used as the sole organization key.
If a destination conflict exists, choose a new destination or have a human resolve it. Do not overwrite it.
Use osmo receipt list --json to audit prior writes.

Recovery

DEVICE_NOT_FOUND: reconnect the Vision Dock, accept the accessory on macOS, select file transfer on the Nano, then rerun osmo doctor.
DEPENDENCY_MISSING or probe unavailable: install ffmpeg for rich metadata. Listing and import remain available.
IMPORT_CONFLICT: inspect the destination and rerun osmo import plan with a different directory.
HASH_MISMATCH: leave source media untouched, retry to a new destination, and inspect the USB connection.
EJECT_FAILED: close applications using the volume, then retry.

---name: osmodescription: Operate the local-first DJI Osmo Nano import CLI safely and with machine-readable receipts.---# osmoUse this skill when a DJI Osmo Nano is connected to macOS in USB file-transfer mode.## Contract- Captured stdout is JSON automatically.- Success is `{schemaVersion, ok, command, data, meta.nextSteps}`.- Errors include `{code, message, hint}` and a nonzero exit code.- Inspect live schemas with `osmo schema [operation] --json`.- Pass `--volume <path>` only when automatic discovery does not select the intended mount.## Workflow1. Run `osmo doctor --json`.2. Run `osmo device status --json`.3. Review with `osmo media list --json` or `osmo media inspect latest --json`.4. Preview with `osmo import plan --dest <path> --json`.5. Stop if `conflictFiles` is not zero.6. Import with the same filters using `osmo import run --dest <path> --json`.7. Confirm copied files and `receiptId` in the result.8. Eject with `osmo device eject --json` only after all file work is complete.## Boundaries- Never treat LRF files as originals. Add `--include-proxies` only when proxies are wanted.- Never delete source media through shell commands as part of this workflow.- Do not claim the CLI can change recording settings, microphone routing, firmware, or DJI Mimo state.- A `suspect` timestamp must not be used as the sole organization key.- If a destination conflict exists, choose a new destination or have a human resolve it. Do not overwrite it.- Use `osmo receipt list --json` to audit prior writes.## Recovery- `DEVICE_NOT_FOUND`: reconnect the Vision Dock, accept the accessory on macOS, select file transfer on the Nano, then rerun `osmo doctor`.- `DEPENDENCY_MISSING` or probe unavailable: install ffmpeg for rich metadata. Listing and import remain available.- `IMPORT_CONFLICT`: inspect the destination and rerun `osmo import plan` with a different directory.- `HASH_MISMATCH`: leave source media untouched, retry to a new destination, and inspect the USB connection.- `EJECT_FAILED`: close applications using the volume, then retry.

Frequently asked questions

Osmo