Run any Skill in Manus with one click

migrate-to-pluginpack

Stars4

Forks0

UpdatedJune 1, 2026 at 23:49

Use when someone has an existing native plugin repo (a Claude Code marketplace, a Cursor plugin, an Antigravity CLI plugin, or a GitHub Copilot 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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

gleanwork

gleanwork/pluginpack

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Computer Occupations, All OtherComputer and Mathematical Occupations·SOC 15-1299

SKILL.md

readonly

name	migrate-to-pluginpack
description	Use when someone has an existing native plugin repo (a Claude Code marketplace, a Cursor plugin, an Antigravity CLI plugin, or a GitHub Copilot 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.

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, …), 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/<id>/ 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/<target>/<file> 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:
```
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.

More from this repository

same repository

add-pluginpack-target

gleanwork/pluginpack

Use when extending pluginpack itself with support for a new AI app or plugin format — i.e. adding a target adapter to the pluginpack codebase. This is for contributors hacking ON pluginpack, not for end users packaging their plugins.

2026-06-014

authoring-pluginpack-config

gleanwork/pluginpack

Use when someone wants to ship one set of agent skills/plugins to multiple AI apps (Claude Code, Cursor, Antigravity CLI, GitHub Copilot) from a single source, and needs to create or update a pluginpack.config.ts — choosing targets, source layout, MCP servers, and output directories.

2026-06-014

pluginpack-build-and-verify

gleanwork/pluginpack

Use when working in a repo that uses pluginpack (it has a pluginpack.config.ts) and you need to build the native plugin outputs, validate them, prune stale files, or check whether a generated plugin repo has drifted — i.e. driving the pluginpack CLI and interpreting its exit codes.

2026-05-294

name	migrate-to-pluginpack
description	Use when someone has an existing native plugin repo (a Claude Code marketplace, a Cursor plugin, an Antigravity CLI plugin, or a GitHub Copilot 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.

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, …), 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/<id>/ 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/<target>/<file> 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:
```
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.