setup-pm

Detect and configure npm, pnpm, yarn, or bun for projects and global environments.

Updated Jan 16, 2026
One-click install
npx skills add https://github.com/Eotel/claude-marketplace --skill setup-pm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-pm
Source: https://github.com/Eotel/claude-marketplace/tree/main/plugins/base/skills/setup-pm
Command: npx skills add https://github.com/Eotel/claude-marketplace --skill setup-pm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Configure your project to use a specific package manager (npm, pnpm, yarn, or bun) across local and global contexts, reducing setup friction and inconsistencies.

Core Features & Use Cases

  • Detect and switch between npm, pnpm, yarn, and bun based on environment, project config, or user preference.
  • Apply per-project or global configuration via dedicated config files and simple commands.
  • Support automated workflows for new projects and CI environments, ensuring consistent package manager usage.

Quick Start

Detect and set your preferred package manager for the current project.

Frequently Asked Questions about setup-pm

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure a specific Node package manager for my project?

You can configure a Node package manager for your project by applying dedicated config files and simple commands to detect and set npm, pnpm, yarn, or bun.

What is the best way to switch between npm, pnpm, yarn, and bun?

The best way to switch between npm, pnpm, yarn, and bun is to use detection order and environment variable overrides to apply per-project or global configuration.

Does this work for setting up package managers in CI environments?

Yes, it supports automated workflows for new projects and CI environments, ensuring consistent package manager usage across diverse JS and Node.js projects.

Can I set a global package manager configuration instead of per-project?

Yes, you can set a global package manager configuration instead of per-project by applying global config files and environment variable overrides to define your preference.

How does package manager detection work for Node.js projects?

Package manager detection works by checking environment variables, project config files, and global config files to identify the active manager in your Node.js project setup.