How do I install the Skill Packager skill?

Run npx skillmds@latest add danishi/skill-packager 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.

Is Skill Packager safe to use?

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 Skill Packager?

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.

Is Skill Packager free to use?

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

Who published Skill Packager?

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

Skill Packager by danishi — Agent Skill

Name: Skill Packager
Author: danishi

Skill Packager

Package a skill directory into a distributable `.skill` archive placed on the Desktop. Use when the user asks to "package", "bundle", "zip up", "export", "distribute", or "ship" a skill, or mentions creating a `.skill` file from `~/.claude/skills/<skill-name>/`.

danishi 7fa4f19 2 files · 3.0 KB Updated Sep 17, 2026

File contents

skill-packager

Compresses ~/.claude/skills/<skill-name>/ into ~/Desktop/<skill-name>.skill — a zip archive with a .skill extension, ready for sharing or installation via Claude Desktop.

Steps

Step 1 — Identify the target skill

Determine which skill to package from the user's request.

If the skill name is explicit, use it directly.
If the user was editing or testing a skill earlier in the conversation, assume that one is the target.
If unclear, list the available skills and ask which one to package:

  ls ~/.claude/skills/

Step 2 — Inspect the contents

List every file that will be included, so the user can spot anything unexpected before it ships:

cd ~/.claude/skills/<skill-name> && \
  find . -type f \
    -not -path '*/__pycache__/*' \
    -not -name '*.pyc' \
    -not -name '.DS_Store' \
  | sort

Confirm that caches (__pycache__/, *.pyc) and OS metadata (.DS_Store) are excluded. Flag anything suspicious before zipping — large binaries, credentials, .env files, local-only configs, personal data — and confirm with the user if in doubt.

Step 3 — Create the `.skill` archive

cd ~/.claude/skills/<skill-name> && \
  zip -r ~/Desktop/<skill-name>.skill . \
    -x '__pycache__/*' '*/__pycache__/*' '*.pyc' '.DS_Store' '*/.DS_Store'

Output: ~/Desktop/<skill-name>.skill
Overwrites any existing file at that path.
ASCII-safe filenames required. Claude Desktop rejects archives containing non-ASCII filenames. If the skill directory contains Japanese or other non-ASCII filenames, rename them to ASCII equivalents before zipping — and update any references inside SKILL.md or supporting scripts accordingly.

Step 4 — Verify and report

Confirm the archive exists and report its path and size:

ls -lh ~/Desktop/<skill-name>.skill

Tell the user the full output path and the file size. If the archive is unexpectedly large (e.g., >5 MB for a typical skill), suggest reviewing Step 2's file list for accidentally-bundled assets.

---name: skill-packagerdescription: Package a skill directory into a distributable `.skill` archive placed on the Desktop. Use when the user asks to "package", "bundle", "zip up", "export", "distribute", or "ship" a skill, or mentions creating a `.skill` file from `~/.claude/skills/<skill-name>/`.---# skill-packagerCompresses `~/.claude/skills/<skill-name>/` into `~/Desktop/<skill-name>.skill` — a zip archive with a `.skill` extension, ready for sharing or installation via Claude Desktop.## Steps### Step 1 — Identify the target skillDetermine which skill to package from the user's request.- If the skill name is explicit, use it directly.- If the user was editing or testing a skill earlier in the conversation, assume that one is the target.- If unclear, list the available skills and ask which one to package:```bash ls ~/.claude/skills/```### Step 2 — Inspect the contentsList every file that will be included, so the user can spot anything unexpected before it ships:```bashcd ~/.claude/skills/<skill-name> && \ find . -type f \ -not -path '*/__pycache__/*' \ -not -name '*.pyc' \ -not -name '.DS_Store' \ | sort```Confirm that caches (`__pycache__/`, `*.pyc`) and OS metadata (`.DS_Store`) are excluded. Flag anything suspicious before zipping — large binaries, credentials, `.env` files, local-only configs, personal data — and confirm with the user if in doubt.### Step 3 — Create the `.skill` archive```bashcd ~/.claude/skills/<skill-name> && \ zip -r ~/Desktop/<skill-name>.skill . \ -x '__pycache__/*' '*/__pycache__/*' '*.pyc' '.DS_Store' '*/.DS_Store'```- **Output:** `~/Desktop/<skill-name>.skill`- **Overwrites** any existing file at that path.- **ASCII-safe filenames required.** Claude Desktop rejects archives containing non-ASCII filenames. If the skill directory contains Japanese or other non-ASCII filenames, rename them to ASCII equivalents *before* zipping — and update any references inside `SKILL.md` or supporting scripts accordingly.### Step 4 — Verify and reportConfirm the archive exists and report its path and size:```bashls -lh ~/Desktop/<skill-name>.skill```Tell the user the full output path and the file size. If the archive is unexpectedly large (e.g., >5 MB for a typical skill), suggest reviewing Step 2's file list for accidentally-bundled assets.

Frequently asked questions