Agent skill

Swpm Manage Commands Args

by deinsoftware in deinsoftware/swpm

Manage cmds and args props in SWPM package manager configs (src/packages/managers/.ts), including adding, modifying or removing command and argument mappings across npm, yarn, pnpm, bun, deno.

MITAuto-check passedDevelopment

Install Swpm Manage Commands Args

skills CLI
$ npx skills add deinsoftware/swpm --skill swpm-manage-commands-args -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install deinsoftware/swpm swpm-manage-commands-args --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/deinsoftware/swpm.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/swpm-manage-commands-args .claude/skills/swpm-manage-commands-args && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
swpm-manage-commands-args
GitHub stars
125
Token cost
~1.5k tokens
SKILL.md length
625 words
Files
3
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

Manage cmds and args props in SWPM package manager configs (src/packages/managers/.ts), including adding, modifying or removing command and argument mappings across npm, yarn, pnpm, bun, deno.

  • Works in 5 steps: Modify/Add cmds or args in package… → Handle command files (only for… → Update CLI registration (only for new… → …
  • Development work in your project
  • SKILL.md covers When to Use, Instructions, Constraints and Examples, plus 1 more section
  • Calls npm and pnpm

What it does

Swpm Manage Commands Args is an agent skill from deinsoftware/swpm. Manage cmds and args props in SWPM package manager configs (src/packages/managers/.ts), including adding, modifying or removing command and argument mappings across npm, yarn, pnpm, bun, deno. Includes internal templates and real-world examples.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files (for example `templates/args.md` and `templates/commands.md`).

It sits in Development. It works with npm, pnpm, Deno and Node.js. The repository describes itself as: Switch Package Manager - Say goodbye to Package Manager confusion. The licence is MIT.

When your agent uses it

  • Development work in your project

Example prompts

  • “/swpm-manage-commands-args”

Requirements

  • Node.js

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Modify/Add cmds or args in package manager configs
  2. Handle command files (only for new/modified commands)
  3. Update CLI registration (only for new commands)
  4. Update documentation
  5. Verify

What it can do on your machine

Read from SKILL.md and the folder at commit ee443bd. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npm
    • pnpm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npm and pnpm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Swpm Manage Commands Args loads about 1.5k tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 625 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~68
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from deinsoftware/swpm at commit ee443bd, republished under its MIT licence (© deinsoftware). 625 words, ~1,526 tokens.

Download SKILL.mdSave it as .claude/skills/swpm-manage-commands-args/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
swpm-manage-commands-args
description
Manage cmds and args props in SWPM package manager configs (src/packages/managers/*.ts), including adding, modifying or removing command and argument mappings across npm, yarn, pnpm, bun, deno. Includes internal templates and real-world examples.
id
swpm-manage-commands-args
version
1.0.0
tags
swpm, package-manager, command-mapping, args-mapping, cli, typescript

Manage SWPM Commands and Args

Use this skill when creating or modifying cmds and/or args props in package manager configuration files under src/packages/managers/*.ts. Handles adding new mappings, updating existing ones, and ensuring consistency across all supported package managers.

When to Use

  • User requests to add/modify/remove a command or argument mapping
  • Changes to cmds or args props in src/packages/managers/*.ts files
  • Ensuring consistent command/argument support across npm, yarn, pnpm, bun, deno
  • Do not use for changes outside manager config files, or for commands/args identical across all package managers

Instructions

  1. Modify/Add cmds or args in package manager configs

    • Edit target files in src/packages/managers/*.ts (npm.ts, yarn.ts, pnpm.ts, bun.ts, deno.ts)
    • For cmds prop: follow templates in templates/commands.md (Replace, Replace+Flag, Not Available, Positional)
    • For args prop: follow templates in templates/args.md (Replace, Replace with Command, Convert to Commands, Remove, Package Decoration, Not Available)
    • Ensure consistency: update all relevant manager files for the same command/argument
  2. Handle command files (only for new/modified commands)

    • New command: Create src/cli/swpm/commands/<command-name>.ts with @yargs v18 API
    • Modified command: Edit existing command file if behavior changes
    • Command file MUST exist for the command to work
  3. Update CLI registration (only for new commands)

    • Edit src/cli/swpm/cli.ts to register new commands
    • Verify existing registration is valid for modified commands
  4. Update documentation

    • Update CHEATSHEET.md with [x]/[ ] markers for command support
    • Update README.md if support status changed (remove/add availability warnings)
  5. Verify

    • Run npm run build to compile TypeScript
    • Run npm run test to check regressions
    • Test changes with target package managers

Constraints

  • New commands require all three: manager config + command file + cli.ts registration
  • Args-only changes only require manager config updates
  • Only map cmds/args that differ across package managers
  • Identical commands/args across all managers do NOT need mapping
  • SWPM passes through unknown commands/args as-is to detected package manager
  • ESM only, Node.js >= 20, TypeScript strict mode
  • @yargs v18 API (not v17 or earlier)

Examples

Example 1: Replace command (remove → uninstall)

User request: "Map remove command to uninstall for npm"

Context: npm uses uninstall while other package managers use remove

Action:

  1. Edit src/packages/managers/npm.ts cmds prop following templates/commands.md:
typescript
cmds: {
  remove: 'uninstall',
  r: 'uninstall',
}

Result: swpm remove express → npm uninstall express


Example 2: Replace+Flag command (upgrade → install --latest)

User request: "Make upgrade command use install --latest in npm"

Context: npm uses install --latest to upgrade packages, while pnpm uses update

Action:

Edit src/packages/managers/npm.ts cmds prop:

typescript
cmds: {
  upgrade: ['install', '--latest'],
  ug: ['install', '--latest'],
}

Result: swpm upgrade express → npm install express --latest


Show full SKILL.md (236 more words)Show less
Example 3: Not Available command

User request: "Mark why command as not available for npm"

Context: npm doesn't have a why command, but pnpm and yarn do

Action:

Edit src/packages/managers/npm.ts cmds prop:

typescript
cmds: {
  why: ['', -1],
}

Result: swpm why express → Not executed in npm (shows error/warning)


Example 4: Positional command (run with -- separator)

User request: "Add support for passing args after -- in run command"

Context: Need to pass additional args to the script being run

Action:

Edit all manager config files:

typescript
cmds: {
  run: { '--': '--' },
}

Result: swpm run test -- --watch → npm run test -- --watch


Example 5: Package Decoration arg (--latest → @latest)

User request: "Make --latest flag add @latest to package name"

Context: Install package with latest tag

Action:

Edit src/packages/managers/npm.ts args prop following templates/args.md:

typescript
args: {
  '--latest': ['<package>@latest', 1],
  '-L': ['<package>@latest', 1],
}

Result: swpm add express --latest → npm install express@latest


Example 6: Replace with Command arg (--global → global command)

User request: "Convert --global flag to global command for npm"

Context: npm uses --global flag, pnpm uses global subcommand

Action:

Edit src/packages/managers/pnpm.ts args prop:

typescript
args: {
  '--global': ['global', 1],
  '-g': ['global', 1],
}

Result: swpm add express --global → pnpm global add express


Example 7: Convert to Commands arg (--frozen → ci)

User request: "Make --frozen flag convert install to ci command"

Context: pnpm uses ci for frozen installs

Action:

Edit src/packages/managers/pnpm.ts args prop:

typescript
args: {
  '--frozen': {
    install: 'ci',
    i: 'ci',
  },
}

Result: swpm install --frozen → pnpm ci


Observations

Before acting, observe:

  • Review existing cmds and args patterns in manager files at src/packages/managers/*.ts
  • Verify CHEATSHEET.md for current implementation status
  • Check src/cli/swpm/commands/ for existing command files
  • Reference templates/commands.md and templates/args.md for configuration patterns

© deinsoftware, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files in .agents/skills/swpm-manage-commands-args of deinsoftware/swpm.

  • SKILL.md
  • templates/args.md
  • templates/commands.md

Open the folder on GitHubat commit ee443bd

Compare with similar skills

Swpm Manage Commands Args next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Swpm Manage Commands Args compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Swpm Manage Commands Args this skilldeinsoftware/swpm125—~1.5kAutomated safety check: PassMIT
Migrate to Denodenoland/skills100—~2.2kAutomated safety check: WarnMIT
TS SDK Authormindfold-ai/Trellis15k—~6.1kAutomated safety check: PassMIT
npm Supply Chain Securitybodadotsh/npm-security-best-practices858—~1kAutomated safety check: WarnMIT
Pre Commitwellwelwel/poku1.2k—~728Automated safety check: PassMIT
Repo Healthcheck Nodecommercetools/ui-kit154—~1.6kAutomated safety check: NotesMIT

Similar skills

  • Migrate to Deno

    denoland/skills

    Official

    Moves a Node.js, npm, Yarn, pnpm or Bun project to Deno in reversible steps, starting with Deno as the package manager and changing no code unless needed.

    100 GitHub stars~2.2k tokensUpdated 2 mo ago
    DevelopmentAuto-check: warnings
  • TS SDK Author

    mindfold-ai/Trellis

    Design, build, verify, and publish production-grade TypeScript SDKs as npm packages inside a pnpm monorepo.

    15k GitHub stars~6.1k tokensUpdated 10 days ago
    DevelopmentAuto-check passed
  • npm Supply Chain Security

    bodadotsh/npm-security-best-practices

    Applies safer package manager defaults and dependency vetting to JavaScript and TypeScript projects to reduce supply-chain attack risk.

    858 GitHub stars~1k tokensUpdated 8 days ago
    SecurityAuto-check: warnings
  • Pre Commit

    wellwelwel/poku

    Run the mandatory pre-commit checks for the poku repository before staging a commit.

    1.2k GitHub stars~728 tokensUpdated 3 mo ago
    Testing & QAAuto-check passed
  • Repo Healthcheck Node

    commercetools/ui-kit

    Verify a Node.js/TypeScript repo's development environment is correctly set up.

    154 GitHub stars~1.6k tokensUpdated 6 days ago
    Frontend & DesignAuto-check: notes
  • Link Workspace Packages

    nomcopter/react-mosaic

    Link workspace packages in monorepos (npm, yarn, pnpm, bun).

    4.8k GitHub starsUsed in 6 repos~760 tokens
    DevelopmentAuto-check passed

More from deinsoftware/swpm

  • Swpm Code Review

    deinsoftware/swpm

    Automated code review bash script for SWPM. An agent skill from deinsoftware/swpm.

    125 GitHub stars~1.1k tokensUpdated 4 mo ago
    Auto-check passed
  • Swpm Keepachangelog

    deinsoftware/swpm

    Keep a Changelog 1.1.0 standards for SWPM. An agent skill from deinsoftware/swpm.

    125 GitHub stars~1.4k tokensUpdated 4 mo ago
    Auto-check passed
  • Swpm Release

    deinsoftware/swpm

    Automated release bash script for SWPM. An agent skill from deinsoftware/swpm.

    125 GitHub stars~1.1k tokensUpdated 4 mo ago
    Auto-check passed
  • Swpm Semver

    deinsoftware/swpm

    Semantic Versioning 2.0.0 guidelines for SWPM. An agent skill from deinsoftware/swpm.

    125 GitHub stars~1.3k tokensUpdated 4 mo ago
    Auto-check passed
  • Swpm Conventional Commits

    deinsoftware/swpm

    Conventional Commits 1.0.0 specification for SWPM. An agent skill from deinsoftware/swpm.

    125 GitHub stars~1.6k tokensUpdated 4 mo ago
    Auto-check passed
  • Swpm Dev Guide

    deinsoftware/swpm

    Development guide for setting up, debugging, and testing SWPM locally.

    125 GitHub stars~1k tokensUpdated 4 mo ago
    Auto-check passed

Categories

Questions about Swpm Manage Commands Args

What does Swpm Manage Commands Args do?

Manage cmds and args props in SWPM package manager configs (src/packages/managers/.ts), including adding, modifying or removing command and argument mappings across npm, yarn, pnpm, bun, deno. Swpm Manage Commands Args is an agent skill from deinsoftware/swpm.ts), including adding, modifying or removing command and argument mappings across npm, yarn, pnpm, bun, deno.

When should I use Swpm Manage Commands Args?

Swpm Manage Commands Args fits situations like: development work in your project.

How do I install Swpm Manage Commands Args in Claude Code?

Run `npx skills add deinsoftware/swpm --skill swpm-manage-commands-args -a claude-code`. Or copy the skill folder (.agents/skills/swpm-manage-commands-args in deinsoftware/swpm) into .claude/skills/swpm-manage-commands-args in your project. Claude Code loads it when a task matches its description.

How do I install Swpm Manage Commands Args in Codex?

Run `npx skills add deinsoftware/swpm --skill swpm-manage-commands-args -a codex`. Or copy the skill folder (.agents/skills/swpm-manage-commands-args in deinsoftware/swpm) into .agents/skills/swpm-manage-commands-args in your project. Codex loads it when a task matches its description.

Can I use Swpm Manage Commands Args in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add deinsoftware/swpm --skill swpm-manage-commands-args -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/swpm-manage-commands-args, .gemini/skills/swpm-manage-commands-args, .github/skills/swpm-manage-commands-args and .opencode/skills/swpm-manage-commands-args in your project.

What does Swpm Manage Commands Args need to run?

Going by SKILL.md and its folder, Swpm Manage Commands Args needs the command-line tools its instructions call (npm and pnpm). Our summary lists: Node.js.

Does Swpm Manage Commands Args access the network?

SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Swpm Manage Commands Args safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Swpm Manage Commands Args use?

Swpm Manage Commands Args is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Swpm Manage Commands Args use?

About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Swpm Manage Commands Args?

Skills that share tags, products or a category with Swpm Manage Commands Args: Migrate to Deno (denoland/skills, 100 stars), TS SDK Author (mindfold-ai/Trellis, 15k stars), npm Supply Chain Security (bodadotsh/npm-security-best-practices, 858 stars) and Pre Commit (wellwelwel/poku, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Swpm Manage Commands Args?

deinsoftware (a GitHub organization) maintains it in deinsoftware/swpm, which has 125 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on June 6, 2026.

Source: deinsoftware/swpm on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.