Dotnet Skills
An MIT-licensed CLI that installs versioned, curated .NET skills and routing agents into Claude Code, GitHub Copilot, Gemini, Codex, and Junie.
If your team runs Claude Code, GitHub Copilot, Gemini, Codex, or Junie on a real .NET codebase, this is one of the few genuinely free tools that improves assistant output without changing your workflow — `dotnet skills install --auto` maps your existing NuGet packages to skills in one step, and bundles like quality (formatter, analyzers, complexity) install a coherent set instead of scattered prompts. Skip it if you work outside .NET or need a cloud-hosted skill marketplace with admin analytics; a shared prompt library or Notion doc will serve you better there.
Verified 16d ago · liveness 69/100 · cite: rightaichoice.com/tools/dotnet-skills
- .NET developers whose AI assistant keeps getting framework and middleware details wrong
- Platform teams standardizing AI code generation across an ASP.NET Core or Blazor codebase
- Teams modernizing EF6, MSBuild, or legacy .NET projects and needing migration-aware context
- Developers budgeting context windows and wanting per-skill token cost visibility
- Non-.NET developers — the entire catalog is .NET and Microsoft-stack specific
- Anyone not using Claude Code, GitHub Copilot, Gemini, Codex, or Junie
- Teams that want a cloud-hosted skill marketplace with admin controls and analytics
We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.
- Honest verdict, not marketing
- Real pros & cons from real users
- Attributed quotes with receipts
3 free scans · no card needed
Skip dotnet-skills if you don't write .NET or your team needs a cloud-hosted skill marketplace with admin controls, shared team analytics, and real-time sync rather than a local CLI and static skill files.
The tool itself is free, but skills consume context window tokens in your assistant — the quality bundle alone is 13,612 tokens, so installing too many at once can eat a large chunk of a prompt budget.
Pricing is the simplest part: the CLI is $0 under an MIT license, with the entire catalog, all 26 agents, 12 bundles, and 23 collections included. That puts it well below hosted skill platforms and paid prompt libraries, which typically charge per seat per month. The real cost is context budget, not dollars — the quality bundle spends 13,612 tokens, so a solo developer on a small context window and an enterprise platform team should plan their bundle selection differently.
In short
Dotnet Skills — An MIT-licensed CLI that installs versioned, curated .NET skills and routing agents into Claude Code, GitHub Copilot, Gemini, Codex, and Junie. Best for .NET developers whose AI assistant keeps getting framework and middleware details wrong, Platform teams standardizing AI code generation across an ASP.NET Core or Blazor codebase, Teams modernizing EF6, MSBuild, or legacy .NET projects and needing migration-aware context. Free to use.
What's new in Dotnet Skills
Checked yesterdayAcross the latest 1 update: 1 changelog entry.
What people actually say about Dotnet Skills — is it worth it?
We ran a structured research pass across product reviews, community discussions, and post-purchase forum threads to surface the patterns vendors won't publish themselves. Below: the recurring strengths, the hidden costs people mention most, and the cohort that consistently regrets adopting this tool.
53 mentions across 4 sources (YouTube, Bluesky, GitHub, Lemmy) · researched Jul 6, 2026.
Average across the 4 sources that answered — each source counts once, not each post.
- +Free, open-source, and MIT-licensed — no cost barrier.
- +185 structured skills covering major .NET frameworks and patterns.
- +Bundles and collections simplify installing related skills together.
- +CLI auto-detects NuGet packages from .csproj files.
- +Active development with additions like F# and C++ skills.
- −Install instructions are confusing for new users.
- −Very few real user experiences or reviews available.
- −Requires AI tool that supports custom skill injection.
- −No explicit support or customer service channel.
- −Small community — contributions and bug fixes may lag.
- • No hidden costs — fully free and open-source.
Viability Score
How well maintained and how widely used is Dotnet Skills? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this
Last calculated: September 2026
How we score →Key Features
- Versioned .NET skill catalog, currently at catalog-v2026.9.5.0
- 182 curated .NET skill files across frameworks, tooling, and diagnostics
- 26 routing agents that orchestrate multiple linked skills
- 12 bundles for one-command grouped installs
- 23 collections for browsing the catalog taxonomy via Collection → Lane → Skill
- CLI install via dotnet tool install --global dotnet-skills
- Auto-detect NuGet packages from .csproj to match relevant skills (dotnet skills install --auto)
- Interactive control center for browsing collections and lanes (dotnet skills)
- Per-skill token count export (dotnet skills catalog tokens --catalog-root .)
- Structured SKILL.md files with routing and validation metadata
- manifest.json package metadata for catalog entries
- Upstream-watch automation tracking official .NET releases and docs
- Vendir-managed upstream package integration
- Local-first operation with no cloud dependency
- Works with Claude Code, GitHub Copilot, Gemini, Codex, and Junie
About Dotnet Skills
dotnet-skills is a free, MIT-licensed command-line tool that feeds structured, versioned .NET knowledge into AI coding assistants. Instead of hand-writing prompts or maintaining a generic rules file, you install curated skill files that describe how ASP.NET Core, Blazor, Entity Framework Core, EF6, Aspire, Azure Functions, MSBuild, NuGet, testing, and diagnostics work on current .NET, then let your assistant pull them in when it answers. The install flow is deliberately narrow: the catalog currently ships 182 skills, 26 routing agents, 23 collections for browsing the taxonomy, and 12 bundles for one-command grouped installs, with the catalog page counting 417,170 skill tokens across the set at catalog-v2026.9.5.0. Bundles such as quality, foundations, testing, and architecture-core lay down a focused multi-skill set in a single command rather than dumping the whole catalog into context. If you would rather start from your own code, `dotnet skills install --auto` scans your .csproj files and matches the NuGet packages you already reference. It is built for .NET developers and platform teams who already use an AI assistant and want framework-aware output without babysitting prompts. Token accounting is part of the package: `dotnet skills catalog tokens --catalog-root .` exports per-skill token counts so you can see what each piece of context actually costs before you commit it to a prompt window. Everything runs locally with no cloud component, and contributions land through normal GitHub pull requests. Positioning-wise, this sits in the same territory as hand-maintained prompt libraries and generic AI rules files, but it is versioned and .NET-specific — a generic prompt pack will not know the difference between EF6 maintenance and EF Core modernization or isolated-worker Azure Functions setup. The trade-off is scope: it only has value inside the .NET ecosystem.
Behind the Verdict
The interesting thing about dotnet-skills is how narrow it deliberately is. It is not a prompt marketplace, not a chat wrapper, and not a cloud platform with dashboards. It is a NuGet-installed CLI (dotnet tool install --global dotnet-skills) that lays down structured SKILL.md files with routing and validation metadata, sourced from a versioned catalog that is currently at catalog-v2026.9.5.0 and was tracking 179 skills and 384,981 tokens as recently as the catalog-v2026.7.22.0 release. That versioning matters: when .NET ships a release, the upstream-watch automation picks it up and skills are updated, which is more than you can say for the average GitHub prompt gist. The design bets on two ideas. First, bundles and collections are separated on purpose. Collections are the taxonomy — 23 of them, with Collection → Lane → Skill drilldowns for browsing and comparing related skills and agents. Bundles are 12 one-command installs (foundations, quality, frontend-quality, architecture-core, testing, and more) built from that taxonomy for people who already know the direction they want. Second, routing agents do the orchestration: 26 agents, each linked to a set of skills. The .NET Aspire Orchestrator links to the aspire and aspnet-core skills plus six more; the .NET Data agent routes across entity-framework-core, entity-framework6 and others; the Microsoft Agent Framework Router handles agent-vs-workflow decisions and AgentThread/AgentSession state. That linkage is what keeps a broad question from pulling in the wrong half of the catalog. The token accounting is the sleeper feature. Each skill has a real cost — ASP.NET Core 1,842 tokens, Aspire 3,089 tokens, Azure Functions 2,210 tokens, Blazor 1,869 tokens, EF6 1,036 tokens, EF Core 2,138 tokens, the foundations bundle 4,043 tokens, quality 13,612 tokens, frontend-quality 8,322 tokens. Exporting those counts before you install means you can reason about context budget instead of guessing why your assistant got vague halfway through a session. Where it falls short: coverage is community- and upstream-dependent, so niche .NET libraries may simply not be represented. Skills are static text files — there is no real-time sync, no cloud-hosted admin surface, no shared team dashboard, no GUI. If your team has standardized on a hosted skill platform with analytics and role controls, this does not replace that. And if you are not on .NET, nothing here applies to you at all. Within those bounds, for a .NET shop already paying for an AI assistant, it is close to free upside.
Researching Dotnet Skills? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Real-world workflow fit
Concrete scenarios for the personas Dotnet Skills actually fits — and what changes day-one when you adopt it.
Runs dotnet tool install --global dotnet-skills, then dotnet skills install --auto to scan the .csproj and match the Microsoft.AspNetCore.* NuGet references already in the project.
Outcome: The matching ASP.NET Core, Blazor, and EF Core skills land locally, and subsequent Copilot answers follow current hosting, middleware, and configuration patterns instead of generic examples.
Installs the quality bundle (10 skills, 13,612 tokens) and the Aspire orchestration agent, then checks dotnet skills catalog tokens --catalog-root . to see the context cost before rollout.
Outcome: Every developer on the team gets the same formatter, analyzer, complexity, and Aspire guidance, and the team can justify the token spend with real per-skill numbers.
Installs the Entity Framework 6 skill (1,036 tokens) plus the .NET Data orchestration agent, which routes across entity-framework-core, entity-framework6, and two more skills.
Outcome: The assistant distinguishes what to keep in EF6 from what to modernize, and the migration path to EF Core is answered with the catalog's guidance rather than guesswork.
Use Cases
- Installing the Blazor skill to get accurate component design, state flow, and rendering patterns in GitHub Copilot
- Auto-detecting NuGet packages from your project and installing matching skills with one command
- Using the interactive control center to browse collections and compare skills before installing
- Installing the .NET Aspire Orchestrator agent to route multi-skill context for cloud-native development
- Measuring skill tokens to understand the context cost of each skill before adding it to your assistant
- Installing the quality bundle in one command to get formatter, analyzers, complexity, and CRAP analysis guidance
- Contributing a new skill for your favorite .NET library by submitting a pull request to the catalog
Limitations
- You need to install the dotnet tool CLI and have one of the supported assistants (Claude Code, GitHub Copilot, Gemini, Codex, or Junie).
- Skills are static text files — no real-time updates and no cloud sync.
- Coverage depends on community and upstream contributions, so some niche .NET libraries may not be represented.
- There is no GUI; everything runs through terminal commands.
- There is no shared team workspace, admin console, or analytics layer.
- The catalog is exclusively .NET, so it is worthless outside the Microsoft stack.
as of 2026-09-14
Verification history
We have re-verified Dotnet Skills 7 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-checked, vendor evidence unchanged
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
Showing the 6 most recent of 7 verification passes.
Free to cite with attribution — this page re-verifies continuously.
12-month cost
Project the real annual outlay, including the implied monthly cost when only an annual tier is published.
Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.
Plans compared
For each published Dotnet Skills tier: who it actually fits, and what it adds vs. the previous tier. Cross-reference the cost calculator above for projected annual outlay.
Open Source
$0
Ideal for
.NET developers and platform teams already using Claude Code, GitHub Copilot, Gemini, Codex, or Junie who want versioned, framework-aware skills without a subscription
What this tier adds
Free entry point: $0 under MIT license, includes the full CLI, all 182 catalog skills, 26 agents, 12 bundles, 23 collections, auto-detect, and per-skill token export
Where the pricing makes sense
The company stage and team size where Dotnet Skills's pricing actually pencils out — and where peers do it cheaper.
Pricing is the simplest part: the CLI is $0 under an MIT license, with the entire catalog, all 26 agents, 12 bundles, and 23 collections included. That puts it well below hosted skill platforms and paid prompt libraries, which typically charge per seat per month. The real cost is context budget, not dollars — the quality bundle spends 13,612 tokens, so a solo developer on a small context window and an enterprise platform team should plan their bundle selection differently.
Setup time & first value
How long it actually takes to get something useful out of Dotnet Skills — broken out by persona, not the marketing-page minute.
Solo developer: a few minutes — one dotnet tool install --global dotnet-skills, then dotnet skills install --auto against your .csproj. Platform team: 15-30 minutes if you pick bundles deliberately and run the token export first. Legacy EF6 or MSBuild modernization: budget a short session to install the right skills and agent rather than the whole catalog.
Switching to or from Dotnet Skills
How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.
- →From hand-maintained prompt libraries: replace ad-hoc prompt files with versioned skills installed via dotnet skills install <skill>
- →From generic AI rules files: install the foundations bundle for core platform, project setup, modern C#, and Microsoft.Extensions guidance
- →From a project with no AI context: run dotnet skills install --auto to match skills to the NuGet packages already referenced in your .csproj
- ↗To a cloud-hosted skill platform: export is manual — skills are static text files, so you copy what you need into the hosted platform's format
- ↗To a self-maintained prompt repository: skills are plain SKILL.md files, so they can be committed and versioned in your own repo
- ↗To no AI skill layer: simply stop installing bundles; nothing is cached remotely, so there is no account to close
Integrations
Resources & Guides
Tutorials & Learning
YouTube returned 6 videos for “Dotnet Skills”, and we withheld 6: 6 did not mention Dotnet Skills. We are showing none, because we could not prove any of them are about Dotnet Skills.
Official links
Tools that pair well with Dotnet Skills
Common stack mates teams adopt alongside Dotnet Skills, with the specific reason each pairing earns its keep.
GitHub Copilot
GitHub Copilot is an AI coding agent that completes code, reviews pull requests, and runs agents from issue to merge
Claude Code
Claude Code is Anthropic's agentic coding assistant that plans, edits, and runs commands across your repo from the terminal, IDE, or browser.
Junie (JetBrains)
Junie is JetBrains' AI coding agent that runs in your terminal, IDE, GitHub, or GitLab — with any model you bring.
Featured Head-to-Head Comparisons
Dotnet Skills vs Cognition Ai
If you're an enterprise team needing an autonomous engineer to handle complex multi-step tasks across platforms, Cognition AI's Devin (with its recent FrontierCode eval and productivity guarantee) justifies the investment. If you're a .NET developer using AI assistants and want to supercharge them with curated, framework-specific context, dotnet-skills is a free, open-source must-have that complements any coding AI.
Dotnet Skills vs Bito
If you’re a .NET developer or team looking for free, open-source skill files to boost AI assistant accuracy on .NET projects, Dotnet Skills is the best choice. But if your organization operates large, multi-repo codebases and needs a system-wide context layer for AI agents, Bito’s knowledge graph and cross-repo analysis are far more powerful, though it requires a usage-based subscription for its AI Architect feature.
Dotnet Skills vs Poolside Ai
Poolside AI and dotnet-skills serve entirely different purposes. Choose Poolside if you are an enterprise needing secure, custom AI agents for complex software engineering in regulated environments. Choose dotnet-skills if you are a .NET developer seeking free, high-quality skill files to supercharge your existing AI coding assistant. They are complementary, not competitive.
Alternatives to Dotnet Skills
View allGitHub Copilot
GitHub Copilot is an AI coding agent that completes code, reviews pull requests, and runs agents from issue to merge
Claude Code
Claude Code is Anthropic's agentic coding assistant that plans, edits, and runs commands across your repo from the terminal, IDE, or browser.
Junie (JetBrains)
Junie is JetBrains' AI coding agent that runs in your terminal, IDE, GitHub, or GitLab — with any model you bring.
Frequently Asked Questions
Categories
Used Dotnet Skills? Help shape our editorial sentiment research.