setup-pm

Configure the package manager for a software project.

1|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/hafidzlvm/opencode --skill setup-pm-hafidzlvm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: setup-pm
Source: https://github.com/hafidzlvm/opencode/tree/main/.dsh/skills/setup-pm
Command: npx skills add https://github.com/hafidzlvm/opencode --skill setup-pm-hafidzlvm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up or switching a project's package manager involves repetitive manual steps and environment-specific decisions. This Skill guides the AI through configuring the package manager for your project based on your instructions. ## Core Features & Use Cases - Package Manager Configuration: Sets up the package manager for a project following the instructions defined in the underlying command file. - Argument-Driven Customization: Accepts free-text arguments so you can specify which package manager or settings to apply. - Use Case: You start a new project and want it configured to use a specific package manager. Invoke the skill with your preference and let the AI perform the setup steps. ## Quick Start Ask the AI to run /setup-pm with your preferred package manager, for example to configure pnpm 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 package manager for my project?▼

Invoke the /setup-pm command and pass your preferred package manager as an argument. The AI follows the instructions in the referenced command file to perform the configuration steps for your project.

How to pass arguments to the setup-pm command?▼

Type any text after /setup-pm when invoking it. That text is treated as $ARGUMENTS and forwarded to the AI, which uses it to determine which package manager or settings to apply.

Does setup-pm support a specific package manager like npm or pnpm?▼

The skill itself does not hardcode a package manager. It delegates to the instructions in commands/setup-pm.md and your provided arguments, so supported managers depend on that referenced file.

Why does setup-pm not perform any configuration steps?▼

The SKILL.md file references an external file, commands/setup-pm.md, for its actual instructions. If that file is missing or empty, the skill has no concrete steps to execute beyond your arguments.