Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

add-pluginpack-target

Estrellas4

Forks0

Actualizado1 de junio de 2026 a las 23:49

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.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

gleanwork

gleanwork/pluginpack

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Otras ocupaciones informáticasOcupaciones informáticas y matemáticas·SOC 15-1299

SKILL.md

readonly

name	add-pluginpack-target
description	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.

Adding a pluginpack target

A target adapter owns one app's native layout, manifests, and validation.

First: get the real format, do not guess

Find the app's actual plugin format from official docs or a real published plugin repo (the way the existing adapters were derived from github/copilot-plugins, gleanwork/cursor-plugins, and the Claude plugins reference). Capture an external oracle you can validate against — a published JSON Schema, the app's own validator CLI, or a real repo to diff against. Record it in CONFORMANCE.md.

Touch points

Adding a target currently means editing ~5 places:

src/types.ts — add the name to the TargetName union.
src/cli.ts — add it to the targets array and parseTarget.
src/build.ts — add it to allTargets.
src/targets.ts — add an emitFoo and register it in the emitters map, plus a manifest builder. Reuse the emitPlugins engine if the target has a per-plugin manifest + a marketplace (like cursor/claude); write a bespoke emitter otherwise (like copilot).
src/validate.ts — add a branch and a validateFoo.

Because the touch points are spread across five files, consider introducing a single target registry (one object per target carrying its emitter, validator, and defaults) before or as part of adding the target. The cost of the registry is repaid immediately by the target you are adding.

Wire MCP

If the app supports MCP servers, decide whether it reads a .mcp.json file (reference it from the manifest, like cursor/copilot, or rely on auto-discovery, like claude), a target-specific config file (like Antigravity's mcp_config.json), or another native shape. resolveMcpServers already merges a plugin's servers; thread the result into your emitter.

Verify

Add conformance tests in tests/ against the external oracle, extend CONFORMANCE.md, then run npm run check.

Más de este repositorio

mismo repositorio

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

migrate-to-pluginpack

gleanwork/pluginpack

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.

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

Adding a pluginpack target

A target adapter owns one app's native layout, manifests, and validation.

First: get the real format, do not guess

Touch points

Adding a target currently means editing ~5 places:

src/types.ts — add the name to the TargetName union.

src/cli.ts — add it to the targets array and parseTarget.

src/build.ts — add it to allTargets.

src/targets.ts — add an emitFoo and register it in the emitters map, plus a manifest builder. Reuse the emitPlugins engine if the target has a per-plugin manifest + a marketplace (like cursor/claude); write a bespoke emitter otherwise (like copilot).

src/validate.ts — add a branch and a validateFoo.

Because the touch points are spread across five files, consider introducing a single target registry (one object per target carrying its emitter, validator, and defaults) before or as part of adding the target. The cost of the registry is repaid immediately by the target you are adding.

Wire MCP

Verify

Add conformance tests in tests/ against the external oracle, extend CONFORMANCE.md, then run npm run check.