add-package

Verify NuGet and npm package licenses before installation.

1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/piers-sinclair/Dostar --skill add-package-piers-sinclair
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-package
Source: https://github.com/piers-sinclair/Dostar/tree/main/.claude/skills/add-package
Command: npx skills add https://github.com/piers-sinclair/Dostar --skill add-package-piers-sinclair

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents the accidental introduction of restrictive or non-compliant software licenses into your commercial codebase by automating license verification before package installation.

Core Features & Use Cases

  • Automated License Auditing: Automatically queries NuGet or npm registries to fetch and validate package license metadata against a pre-defined list of permissive licenses.
  • Policy Enforcement: Blocks the installation of packages with restrictive licenses like GPL or AGPL, ensuring your project remains compliant for closed-source distribution.
  • Use Case: When you need to add a new dependency, this skill ensures you never inadvertently include a library that would force your proprietary project to be open-sourced.

Quick Start

Use the add-package skill to install the Newtonsoft.Json package into the current project after verifying its license.

Frequently Asked Questions about add-package

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

FAQPage Schema
How do I check npm package licenses before adding dependencies?

Automated license auditing queries the npm registry to fetch and validate package license metadata against a list of permissive licenses. This prevents accidental introduction of restrictive software into your commercial codebase before installation.

Can I block GPL or AGPL packages during NuGet installation?

Yes, you can block GPL or AGPL packages during NuGet installation by enforcing policy validation against permissive licenses. This prevents the accidental introduction of restrictive licenses that would force your proprietary project to become open-sourced.

Does automated license verification work with both pnpm and dotnet CLI?

Automated license verification works with both pnpm and dotnet CLI tools by querying the respective package registry APIs. It requires network access to fetch metadata and locally executes the appropriate CLI tool to complete the installation process.

What is the best way to enforce permissive licensing policies for commercial projects?

The best way to enforce permissive licensing policies for commercial projects is to automate license verification directly within your software development workflow. This systematically blocks restrictive packages before installation, ensuring your codebase remains compliant for closed-source distribution.

Why should I verify package license compliance before installation?

You should verify package license compliance before installation to prevent restrictive licenses from entering your codebase. This automation stops you from inadvertently including libraries that would legally force your proprietary project to be open-sourced.