pkg-binary-builder
Configure pkg for Node.js binary builds with asset bundling and cross-platform targets.
npx skills add a5c-ai/babysitter --skill pkg-binary-builder --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Pkg Binary Builder Configure pkg for Node.js binary builds. ## Generated Patterns ```json { "pkg": { "scripts": "dist/**/*.js", "assets": ["dist/**/*.json", "node_modules/better-sqlite3/**/*"], "targets": ["node18-linux-x64", "node18-macos-x64", "node18-win-x64"], "outputPath": "build" }, "scripts": { "build:binary": "pkg . --compress GZip" } } ``` ## Target Processes - cli-binary-distribution - package-manager-publishing
- Generated Patterns
- Target Processes
What does the pkg-binary-builder skill do?
Configure pkg for Node.js binary builds with asset bundling and cross-platform targets.
How do I install it?
Run `npx skills add a5c-ai/babysitter --skill pkg-binary-builder --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From a5c-ai/babysitter, a repository with 1,642 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.