feat: add pack command to create .skill files

[rh42-ic]

Add skills pack command that packages skills into .skill files (ZIP format) (like skill-creator/SKILL.md ).

Supports packing from local paths, GitHub/GitLab repos, and installed skills.

# Pack a local skill
npx skills pack ./my-skill

# Pack from GitHub repository
npx skills pack owner/repo

# Pack specific skill from repo with multiple skills
npx skills pack owner/repo --skill my-skill

# List available skills in a source
npx skills pack ./my-skills --list

# Pack an installed skill
npx skills pack --installed --skill git-commit

# List installed skills available for packing
npx skills pack --installed --list

# Pack all skills from a source
npx skills pack ./my-skills --all -o ./output

# Pack without confirmation prompts
npx skills pack owner/repo --skill my-skill -y

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​types/​archiver@​7.0.0
	archiver@​7.0.1

View full report

[elliotllliu]

The pack command is a solid addition to the skills workflow — being able to create .skill files directly from the CLI closes a gap in the current toolchain.

1748 lines is a big PR though. A few questions:

• Does it validate SKILL.md frontmatter before packing?
• Is there a size limit for the output .skill file?
• How does it handle symlinks inside the skill directory?

Great work on this 🔥

[rh42-ic]

• Does it validate SKILL.md frontmatter before packing?

Yes, I've added validation functionality based on the latest version of skill-creator. Currently, this only affects the pack process because I want to keep the merge overhead low and avoid modifying the add workflow for now. I may consider integrating it into the add flow after gathering more feedback.

Based on recent testing, the validation might be a bit too strict—it currently rejects all custom properties (such as those used by OpenClaw). I am considering adding an extra option to handle this more flexibly.

• Is there a size limit for the output .skill file?

Thanks for the heads-up! I will add two parameters to control and limit the size of both the skill and the repository, ensuring these checks happen before the download whenever possible.

• How does it handle symlinks inside the skill directory?

Thanks for the heads-up! This is definitely an area that needs improvement. I'll look into a better way to handle these.