vixues/skill-packager
Authors Agent Skills v1.0 packages (SKILL.md plus references/scripts), runs package_skill to produce a standards-compliant zip, and uses install_skill to add skills from HTTPS, registry, workspace, or an uploaded archive. Use when the user wants to turn documentation, workflows, or code into a portable skill, export a skill zip, or install a skill from a link or file without leaving the chat.
npx skills add https://github.com/vixues/LeAgent --skill skill-packager
Help the user create, package, and install Agent Skills v1.0 bundles.
.zip / .tar.gz skill bundle to install.~/.cursor/skills/ or .cursor/skills/) or another agent.name field in SKILL.md frontmatter (kebab-case).references/ or assets/; keep SKILL.md concise with links to those files.scripts/ for helpers; script execution may require server env flags—document that.| Goal | Tool |
|------|------|
| Validate + zip a folder | package_skill with skill_directory (optional output_path) |
| Install from URL | install_skill with source_type: url, url, optional sha256 |
| Install from registry | install_skill with source_type: registry, registry_skill_name |
| Install from project folder | install_skill with source_type: workspace, workspace_path, target_skill_name |
| Install from uploaded archive | install_skill with source_type: uploaded_archive, file_id |
After installation, use load_skill with the returned skill name to pull instructions.
If the user only needs Cursor (not LeAgent runtime): give them the zip from package_skill and instruct them to extract so one top-level folder skill-name/ contains SKILL.md, then copy that folder into %USERPROFILE%\.cursor\skills\ or the project’s .cursor/skills/. Do not place skills in ~/.cursor/skills-cursor/ (reserved for built-ins).
description in frontmatter states what the skill does and when to use it (third person).name in SKILL.md.package_skill before sharing the zip; fix validation errors if any.Take vixues/skill-packager from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.