# 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.

- **Type:** Skill
- **Install:** `agentstack add skill-gleanwork-pluginpack-migrate-to-pluginpack`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [gleanwork](https://agentstack.voostack.com/s/gleanwork)
- **Installs:** 0
- **Category:** [Developer Tools](https://agentstack.voostack.com/c/developer-tools)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [gleanwork](https://github.com/gleanwork)
- **Source:** https://github.com/gleanwork/pluginpack/tree/main/skills/migrate-to-pluginpack

## Install

```sh
agentstack add skill-gleanwork-pluginpack-migrate-to-pluginpack
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## 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

1. **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.

2. **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.

3. **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.

4. **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`.

5. **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](https://github.com/gleanwork)
- **Source:** [gleanwork/pluginpack](https://github.com/gleanwork/pluginpack)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-gleanwork-pluginpack-migrate-to-pluginpack
- Seller: https://agentstack.voostack.com/s/gleanwork
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.