Pluginpack Build And Verify
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.
Install
$ agentstack add skill-gleanwork-pluginpack-pluginpack-build-and-verify ✓ 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-pluginpack-build-and-verify) 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
Building and verifying with pluginpack
pluginpack is a deterministic build tool. Every command is scriptable and exits non-zero on failure.
Build
pluginpack build # all configured targets
pluginpack build --target cursor # one target
pluginpack build --target claude --dry-run # print planned managed files, write nothingExit 0 on success; 1 on config/source/output failure. The build errors if two targets resolve to the same output path (give them distinct outDirs).
Validate
pluginpack validate --target cursor --dir ../cursor-pluginsChecks an output directory against that target's native manifest/path/frontmatter rules. Exit 0 = passes, 1 = errors. (For Claude, claude plugin validate is the authoritative check; pluginpack's conformance tests use it when available.)
Diff (CI staleness gate)
pluginpack diff --target cursor --against ../cursor-pluginsBuilds to a temp dir and compares managed files against an existing target repo. Exit 1 when the repo is stale — wire this into CI to fail or to open a PR against the generated repo. Use ignoredDiffPaths in the target config for paths the generated repo intentionally owns.
Prune / clean
pluginpack prune --dry-run # show stale managed files
pluginpack prune # remove them
pluginpack clean --target cursor # remove all managed files for a targetThese only touch files recorded in .pluginpack/.json. A guard refuses to delete anything inside your declared source (source.skills/source.plugins) or the config; pass --force to override (rarely needed — usually it means an outDir overlaps your source).
Developing pluginpack itself
Run the full gate before considering work done: npm run check (format, lint, typecheck, test, build, docs). Regenerate the README CLI reference with node dist/cli.js docs after changing commands.
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.