Sanitize, translate, package, and share Claude skills sequentially.
npx skills add https://github.com/epologee/leclause-skills --skill export-skill
Please help me install this Agent Skill. Skill: export-skill Source: https://github.com/epologee/leclause-skills/tree/main/packages/export-skill/skills/export-skill Command: npx skills add https://github.com/epologee/leclause-skills --skill export-skill
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.
Run /export-skill say en to sanitize the say skill, translate it to English, package it, and open a Finder handoff.
High-intent search queries and answers about installing and using this skill.
To package and share a Claude skill, you can run the export-skill command to sanitize the source directory, optionally translate or port it, package it, and open a Finder handoff. This orchestrated workflow prevents leaking sensitive information.
Sanitizing a skill directory removes PII and environment-specific data from the local Claude skill files before sharing. This prevents leaking sensitive information or producing broken packages when handing off skills to recipients.
Yes, you can port a local Claude skill to another platform for local testing. The export workflow supports an optional porting step, allowing you to produce a platform-specific port alongside sanitization and packaging.
You can translate a Claude skill to English during the export process by passing the target language as an argument. The workflow chains the translation step sequentially after sanitization and before packaging the final artifact.
Your skill export aborts with a clear error when expected outputs are missing from a step, or if the source skill does not exist under the ~/.claude/skills directory. The workflow validates filesystem paths and arguments to prevent silent failures.
No, you do not need to run the entire workflow if you only want to port a skill. Each step is available as a standalone sub-skill, allowing you to run partial workflows for porting or re-packaging only without repeating unnecessary steps.
epologeeStrip PII and security issues from Claude Code skills for shareable exports.
aresbitSearch, install, update, and publish AI agent skills via ClawdHub CLI.
louisbrulenaudetSynchronizes local agent skill directories with upstream sources via Node.js and Git.
hasnaxyzCreate and package Claude skill directories with valid SKILL.md frontmatter.
