Migrate To Pluginpack
Use when someone has an existing native plugin repo (a Claude Code marketplace, a Cursor plugin, an Antigravity CLI plugin, a GitHub Copilot plugin, or an OpenAI Codex CLI plugin) and wants to manage it from one portable source via pluginpack — generating the source layout and config, then proving the output matches the original with diff.
Install
$ agentstack add skill-gleanwork-pluginpack-migrate-to-pluginpack ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-gleanwork-pluginpack-migrate-to-pluginpack) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Migrating an existing plugin repo into pluginpack
Goal: stop hand-maintaining a native plugin repo by generating it from portable source, verified byte-for-byte against the original.
Steps
- Inspect the existing repo. Note its marketplace manifest
(.claude-plugin/marketplace.json, .cursor-plugin/marketplace.json, .codex-plugin/plugin.json, …), the per-plugin layout, and the skill/agent/command/hook/MCP content.
- Create portable source. Put skills under a repo-level
skills/directory
(or richer plugins under plugins// with skills/, agents/, commands/, rules/, hooks/, assets/). Add plugin.pluginpack.json for per-plugin metadata and a .mcp.json for MCP servers. Where a file must differ per app, add targets// next to the base file.
- Write the config targeting that app, mapping source → emitted plugin via
from, and path/pluginRoot to reproduce the original directory layout. See the authoring-pluginpack-config skill.
- Build and diff until clean:
``bash pluginpack build --target claude pluginpack diff --target claude --against ../claude-plugins ``
Iterate on the source/config until diff exits 0. For paths the generated repo legitimately owns (license, CI, hand-written README), add them to the target's ignoredDiffPaths.
- Wire diff into CI in the generated repo so future source changes that
aren't regenerated are caught.
Tip: migrate one target at a time; diff is the source of truth for fidelity.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: gleanwork
- Source: gleanwork/pluginpack
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.