package

Package skill directories into SKILL.md files or zip archives.

3|1|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/epologee/leclause-skills --skill package-epologee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: package
Source: https://github.com/epologee/leclause-skills/tree/main/packages/export-skill/skills/package
Command: npx skills add https://github.com/epologee/leclause-skills --skill package-epologee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sharing or distributing a skill directory requires creating a portable artifact while preserving files and avoiding accidental content changes, which is tedious and error-prone when done manually. This skill automates the packaging decision and produces a ready-to-share file without transforming the skill content.

Core Features & Use Cases

  • Mechanical packaging: emit a single SKILL.md file when the directory contains only that file, or create a zip archive for multi-file directories.
  • Safety and validation: verify the input is a directory, count text files to decide format, prevent silent overwrites, and only remove intermediate directories when the input is under the designated temporary export location.
  • Use cases: prepare a skill for sharing with a colleague, create a marketplace-ready bundle, or hand off a translated or sanitized skill directory.

Quick Start

Invoke /export-skill:package with the path /tmp/skill-exports/say/ to create say.zip next to the input directory.

Frequently Asked Questions about package

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I package a skill directory into a single zip file for sharing?

To package a skill directory, the tool validates the input path and counts text files. If multiple files exist, it creates a zip archive; if only a SKILL.md exists, it outputs that single file for easy distribution.

What is the best way to export a single-file skill for marketplace publishing?

Exporting a single-file skill requires counting text files in the directory. When only a SKILL.md is present, the packaging tool emits that file directly, creating a ready-to-share artifact without altering the original content.

Can I use this packaging process on directories outside the temporary export location?

Yes, you can package directories from any valid path. However, the tool only deletes intermediate source directories when the input is located under the designated temporary export location to prevent accidental data loss.

How does the skill packaging mechanism decide between creating a zip archive or a single file?

The packaging mechanism decides by counting text files within the validated input directory. Multi-file directories produce a zip archive, while directories containing only a single SKILL.md file produce a standalone markdown file.

Are there any limitations or safety precautions when preparing a skill zip archive?

Safety precautions include verifying the input is a directory and preventing silent overwrites. The tool avoids deleting sources outside the designated temporary export location and reports the resulting path without transforming content.

Do I need to manually zip multi-file skill directories before distribution?

No, manual zipping is unnecessary. The packaging tool automates the process by validating the directory, counting files, and creating a zip archive for multi-file skills to ensure a portable, ready-to-share bundle.