菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
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.
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.
| name | authoring-pluginpack-config |
| description | 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. |
pluginpack compiles one portable source into each app's native plugin format.
The config (pluginpack.config.ts) declares the source layout and the targets
to emit.
npx @gleanwork/pluginpack init scaffolds a pluginpack.config.ts and an
example source plugin. Then edit to taste.
import { defineConfig } from "@gleanwork/pluginpack";
export default defineConfig({
name: "acme-plugins",
version: "0.1.0",
source: {
// Recommended: portable skills at the repo-level skills/ directory.
skills: "skills",
rootPlugin: { id: "core", description: "Acme portable skills." },
// Alternatively, richer source plugins live under plugins/<id>/.
// plugins: "plugins",
},
metadata: {
description: "Acme agent plugins.",
author: { name: "Acme" },
owner: { name: "Acme", email: "support@acme.com" },
license: "MIT",
},
targets: {
cursor: {
outDir: ".",
plugins: {
acme: {
from: ["core"],
path: "plugins/cursor/acme",
components: ["skills"],
},
},
},
claude: {
outDir: ".",
pluginRoot: "plugins/claude",
plugins: { acme: { from: ["core"] } },
},
antigravity: {
outDir: "plugins/antigravity",
plugins: { acme: { from: ["core"] } },
},
copilot: {
outDir: "plugins/copilot",
plugins: { acme: { from: ["core"] } },
},
},
});
source.skills is the portable surface; source.rootPlugin.id is the source
plugin name targets reference via from.from lists the source plugin id(s) to include; multiple
ids merge (a colliding file path is an error).path / pluginRoot control where a target places the emitted plugin.claude and copilot both write .claude-plugin/marketplace.json, so they
cannot share an outDir. Give them distinct roots (e.g. claude at ., copilot
at plugins/copilot). pluginpack build errors on overlapping output paths.
Add a .mcp.json ({ "mcpServers": { "name": { ... } } }) at the source plugin
root, or an mcpServers key in plugin.pluginpack.json. pluginpack wires it
into each target natively.
After editing: pluginpack build then pluginpack validate --target <t>. See
the build-and-verify skill.