Add Pluginpack Target
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.
Install
$ agentstack add skill-gleanwork-pluginpack-add-pluginpack-target ✓ 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-add-pluginpack-target) 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
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, the Claude plugins reference, and the documented OpenAI Codex CLI plugin format). 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 means:
src/types.ts— add the name to theTargetNameunion.src/targets/.ts— implementPluginTargetDefinition(see
src/targets/types.ts): emit logic, manifest/marketplace builder, validation, install snippet, and defaults.
src/targets/registry.ts— add one entry mapping the name to that
definition.
Everything else — the CLI's --target choices, build()'s target set, and emit/validate dispatch — derives from the registry automatically via the shared engine in src/targets/engine.ts. Reuse src/targets/validation-shared.ts for checks whose shape genuinely matches the other targets (hooks, frontmatter); write your own where the shape is genuinely different, the way codex's structured source object does.
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.
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.