Skip to content
TrustedSkillsbeta
Back to all skills

Dotnet Devcert Trust

Checked
aaronontheweb·vlatest·backend·MIT

Verifies .NET developer certificates for authenticity and integrity, ensuring secure code development practices and bolstering project trust.

Repository

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 aaronontheweb/dotnet-skills --skill dotnet-devcert-trust -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

aaronontheweb

Taken from the source listing. We haven't verified who controls this account.

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 passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    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 aaronontheweb/dotnet-skills at e426ed93a9.

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

Commit
e426ed93a9
Manifest
skills/dotnet-devcert-trust/SKILL.md
Scanned
1 file, 379 lines
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

This skill configures the .NET runtime to trust development certificates, enabling secure HTTPS testing without production-grade certificate authorities. It resolves SSL/TLS handshake failures that occur when AI agents attempt to connect to local servers using self-signed or dev certs.

When to use it

  • Debugging API endpoints running on https://localhost with self-signed certificates.
  • Validating AI agent connectivity to internal services before deploying to production.
  • Automating CI/CD pipelines that require certificate validation for secure builds.
  • Testing microservices architectures where mutual TLS (mTLS) is enforced locally.

Key capabilities

  • Automatically adds development certificates to the trusted root store.
  • Prevents System.Net.Http.HttpRequestException caused by untrusted SSL certs.
  • Supports both Windows and Linux .NET environments.
  • Integrates seamlessly with existing .NET application configurations.

Example prompts

  • "Configure my .NET app to trust self-signed dev certificates for local HTTPS testing."
  • "Fix the SSL error when my AI agent tries to connect to a local API using a dev cert."
  • "Set up trusted development certificates in a .NET environment for secure localhost communication."

Tips & gotchas

Ensure you have write permissions to modify the system or user certificate store, as this skill may require elevated privileges. Always revert changes after testing to avoid trusting unverified certificates in production environments.