About this skill

Problem

Manual packaging of local skills often breaks in three places: slug and version can drift between SKILL.md and _meta.json, runtime config such as packager.json may leak into release zips, and output can land inside the source skill directory or another project. This skill moves that workflow into a script so release packages are more predictable.

How it works

After the user confirms the source path, the skill runs scripts/pack.mjs. The script reads the SKILL.md frontmatter, updates _meta.json, clears stale zips, creates the package, validates key files and metadata, and reports the result. Backup location is resolved from an explicit argument, then packager.json, then the MySKILLs/ fallback. On repeat packaging, it also checks whether description still matches current functionality and fixes stale wording before continuing.

Boundaries

It is intended for local skill packaging, release zip generation, and backup-directory setup. It does not upload releases or manage versioning. The first argument is the source skill directory, and output should belong to the project where packaging is initiated.

Screenshots

Use Cases

After iterating on a local Opencode skill, create a distributable zip and verify version consistency.
During first packaging, store the backup directory in packager.json to avoid specifying output manually.
Before release, ensure runtime config files are excluded and metadata matches SKILL.md.
Avoid writing packaged output into the source skill directory or another project by mistake.

Best For

Skill authors maintaining local Opencode skills who need recurring release packages and metadata consistency.
Technical operations staff managing skill backup directories without manually choosing zip output paths.
Collaboration owners distributing local skills to teammates and excluding runtime config or temporary files.
Independent developers packaging local skills across projects and preventing output-path mixups.