export-skill

What problem does it solve?

Exporting a Claude skill for sharing requires removing PII and environment-specific data, optionally translating or porting it for other platforms, packaging it, and handing it off to recipients. Doing all these steps manually is error-prone and tedious, and can lead to leaking sensitive information or producing broken packages.

Core Features & Use Cases

• Orchestrated workflow: Chains sanitize, optional translate or port, package, and share as sequential Skill tool invocations so you can run the entire export in one command.
• Validation & safety checks: Verifies the source skill exists under ~/.claude/skills, ensures suffixes are valid, prevents overwriting existing /tmp/skill-exports paths, and aborts with clear errors when steps fail.
• Composable sub-skills: Each step is available standalone (sanitize, translate, port, package, share) for partial workflows like porting or re-packaging only.
• Use case: Share a colleague-friendly copy of a skill translated to English and packaged, or produce a platform-specific port for local testing.

Quick Start

Run /export-skill say en to sanitize the say skill, translate it to English, package it, and open a Finder handoff.