dotnet:intent-detection

Detect user intent and route requests to /dotnet:* commands.

2|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/dimsour/dotnet-ai-toolkit --skill dotnet-intent-detection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet:intent-detection
Source: https://github.com/dimsour/dotnet-ai-toolkit/tree/main/plugins/dotnet/skills/intent-detection
Command: npx skills add https://github.com/dimsour/dotnet-ai-toolkit --skill dotnet-intent-detection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill simplifies the process of routing user requests to the correct command within the plugin, ensuring efficient command execution and reducing ambiguity.

Core Features & Use Cases

  • Intent Detection: Determines the user's intent from natural-language requests.
  • Command Routing: Routes requests to the appropriate /dotnet:* command.
  • Use Case: For instance, if a user says "Add cancel button to order detail page," the Skill routes the request to the correct command for implementing the feature.

Quick Start

Run the command '/dotnet:plan' to start planning a new feature.

Frequently Asked Questions about dotnet:intent-detection

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

FAQPage Schema
How does natural language intent detection work for .NET command routing?

Natural language intent detection for .NET command routing works by processing user input text to determine the desired action and directing it to the appropriate /dotnet:* command. It reduces command ambiguity and improves workflow efficiency.

Can I use this intent detection Skill to route plain English requests to .NET CLI commands?

Yes, you can use this intent detection Skill to route plain English requests to .NET CLI commands. It interprets natural language requests, such as asking to add a button, and routes them to the correct /dotnet:* command for implementation.

What is the best way to reduce command ambiguity in a .NET command-line interface?

The best way to reduce command ambiguity in a .NET command-line interface is to apply natural language intent detection. This approach interprets user requests precisely and routes them to the appropriate /dotnet:* command for accurate execution.

How do I start planning a new .NET feature after intent is detected?

To start planning a new .NET feature after intent is detected, run the /dotnet:plan command. This initiates the workflow to translate the detected user intent into an actionable development plan.

Does intent detection for .NET commands require any additional dependencies?

No additional dependencies are required for intent detection in .NET commands. The Skill operates independently to process natural language input and route it to the correct /dotnet:* command without external modules.