Skip to content
TrustedSkillsbeta
Back to all skills

Aspire Service Defaults

Checked
aaronontheweb·vlatest·other·MIT

Aspire Service Defaults automatically configures optimal service settings for improved performance and reliability across your environment.

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 aspire-service-defaults -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.

Scanned
1 file, 358 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

The aspire-service-defaults skill provides default configuration settings for Aspire services within the .NET ecosystem. It streamlines project setup by applying consistent baseline parameters across multiple microservices without requiring manual intervention for each instance.

When to use it

  • Initializing new multi-service .NET applications that require uniform service configurations.
  • Establishing a standardized environment for development, testing, and production deployments.
  • Reducing configuration drift between different instances of the same Aspire service.
  • Accelerating onboarding for teams by enforcing best-practice defaults immediately upon project creation.

Key capabilities

  • Applies global default settings to all registered Aspire services automatically.
  • Ensures consistency in connection strings, health check endpoints, and logging levels.
  • Integrates seamlessly with the .NET Aspire dashboard for centralized management.
  • Eliminates repetitive configuration code across service definitions.

Example prompts

  • "Set up default configurations for my new Aspire project using aspire-service-defaults."
  • "Apply standard service defaults to ensure all my microservices use consistent health check settings."
  • "Configure the Aspire environment with baseline defaults before adding custom logic to my services."

Tips & gotchas

Ensure your .NET SDK version is compatible with the latest Aspire release, as default configurations may change between major versions. While this skill sets strong baselines, always review generated configuration files to verify they align with specific security or compliance requirements for your organization.