dotnet-local-tools

Manage local .NET tools via a dotnet-tools.json manifest file.

1|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/bbsbot/mac-md-win --skill dotnet-local-tools-bbsbot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-local-tools
Source: https://github.com/bbsbot/mac-md-win/tree/main/.claude/skills/dotnet/skills/local-tools
Command: npx skills add https://github.com/bbsbot/mac-md-win --skill dotnet-local-tools-bbsbot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that all developers on a team and all CI/CD pipelines use the exact same versions of project-specific .NET CLI tools, preventing version conflicts and ensuring reproducible builds.

Core Features & Use Cases

  • Centralized Tool Management: Define and manage .NET tools (like DocFX, EF Core CLI, ReportGenerator) within a repository using dotnet-tools.json.
  • Reproducible Environments: Guarantees that the same tools are available and at the same versions across all development machines and build agents.
  • CI/CD Integration: Simplifies setup in pipelines with a single dotnet tool restore command.
  • Use Case: A team needs to use a specific version of DocFX for documentation generation. By adding it to dotnet-tools.json, every developer and the CI server will automatically use that exact version when running dotnet docfx.

Quick Start

Run dotnet tool restore to install all tools defined in the project's manifest.

Frequently Asked Questions about dotnet-local-tools

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

FAQPage Schema
How do I ensure consistent .NET CLI tool versions across my development team and CI/CD pipelines?

You manage local .NET tools using a dotnet-tools.json manifest file to pin specific tool versions. Running dotnet tool restore across all environments guarantees reproducible builds by automatically installing the exact required versions.

What is the best way to manage project-specific .NET tools like DocFX and EF Core?

The best way to manage project-specific .NET tools like DocFX and EF Core is by defining them in a dotnet-tools.json manifest. This centralizes tool management and ensures every environment uses the exact versions specified for your repository.

How does dotnet tool restore work for CI/CD integration?

For CI/CD integration, dotnet tool restore reads the dotnet-tools.json manifest file and automatically installs the pinned .NET CLI tools. This single command simplifies pipeline setup and guarantees the build agent has the exact tool versions required.

When do I need a dotnet-tools.json manifest file for .NET tooling?

You need a dotnet-tools.json manifest file when you want to prevent version conflicts and ensure reproducible builds across multiple development machines. It is essential whenever your team relies on project-specific .NET CLI tools like ReportGenerator or EF Core.

Can I update existing .NET local tools defined in my repository manifest?

Yes, you can update existing .NET local tools defined in your repository manifest. The local tool management workflow supports the installation, restoration, and updating of project-specific CLI tools to maintain consistent tooling environments.