local-tools

Manage .NET local tools via manifest files and CLI commands.

10|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill local-tools-agibuild
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: local-tools
Source: https://github.com/AGIBuild/Agibuild.Fulora/tree/main/.cursor/skills/local-tools
Command: npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill local-tools-agibuild

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the management of .NET local tools, ensuring consistent development environments and simplifying CI/CD integration by defining and restoring project-specific CLI tools.

Core Features & Use Cases

  • Manifest Management: Initializes and maintains the .config/dotnet-tools.json file.
  • Tool Installation & Restoration: Installs specific tool versions and restores all defined tools with a single command.
  • CI/CD Integration: Provides clear guidance for integrating tool restoration into GitHub Actions and Azure Pipelines.
  • Use Case: When onboarding a new developer to a project, they can simply run dotnet tool restore to get all the necessary CLI tools (like docfx, dotnet-ef, csharpier) configured exactly as the team uses them.

Quick Start

Use the local-tools skill to set up a new .NET local tools manifest for your project.

Frequently Asked Questions about local-tools

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

FAQPage Schema
How do I manage .NET local tools for consistent project-specific tooling?

Manage .NET local tools by initializing and maintaining a `.config/dotnet-tools.json` manifest file. This ensures reproducible builds and isolated tool versioning per repository for consistent development environments.

What is the best way to restore .NET CLI tools in a CI/CD pipeline?

Restore .NET CLI tools in CI/CD pipelines by integrating tool restoration commands into GitHub Actions or Azure Pipelines. This ensures CI/CD parity by installing exact tool versions defined in the manifest.

How do I set up a .NET development environment with tools like dotnet-ef and docfx?

Set up a .NET development environment by running `dotnet tool restore` to install specific CLI tool versions like docfx and dotnet-ef. This configures project-specific tooling exactly as defined by the team.

Can I use a .NET local tools manifest for reproducible builds across different machines?

Use a .NET local tools manifest to achieve reproducible builds across different machines. The manifest defines project-specific CLI tools and isolated versioning, ensuring every developer restores the exact same toolset.

Why do I need a dotnet-tools manifest file instead of installing tools globally?

You need a dotnet-tools manifest file instead of global installation to isolate tool versioning per repository. This addresses scenarios requiring CI/CD parity and consistent project-specific tooling without affecting other environments.

Does this approach work for onboarding new developers to a .NET project?

This approach works for onboarding new developers to a .NET project by allowing them to run a single restore command. It automatically configures all necessary CLI tools defined in the local tools manifest.