Skip to content
TrustedSkillsbeta
Back to all skills

Dotnet Best Practices

Official
github·vlatest·backend·MIT

Ensures C# code adheres to GitHub's recommended .NET coding standards and best practices for maintainability.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add github/awesome-copilot --skill dotnet-best-practices -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

github

Matched to the vendor's own GitHub organisation.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • Declares what it does: failed

    No SKILL.md was found in the skill's directory.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned github/awesome-copilot at 6c4d33b9cf.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
0 files
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The dotnet-best-practices skill provides guidance on implementing industry-standard practices for .NET development. It covers areas such as code structure, performance optimization, security measures, and testing strategies to help developers build robust and maintainable applications.

When to use it

  • When refactoring legacy .NET code to improve readability and maintainability
  • When setting up new projects and looking for standardized templates or guidelines
  • When preparing for code reviews and wanting to ensure adherence to best practices
  • When optimizing application performance in production environments

Key capabilities

  • Code structure recommendations for clean, modular design
  • Performance optimization techniques for .NET applications
  • Security best practices for handling sensitive data and authentication
  • Testing strategies including unit testing, integration testing, and CI/CD pipelines

Example prompts

  • "What are the top 5 security best practices when building a .NET web API?"
  • "How can I optimize the performance of my ASP.NET Core application?"
  • "Can you provide a template for organizing a large-scale .NET solution?"

Tips & gotchas

  • Ensure your project is using up-to-date .NET SDK versions to take full advantage of modern best practices.
  • Some recommendations may require adjustments based on specific project requirements or team conventions.