Skip to content
TrustedSkillsbeta
Back to all skills

Dotnet Slopwatch

Checked
aaronontheweb·vlatest·backend·MIT

Dotnet Slopwatch analyzes .NET code for performance bottlenecks and potential issues, boosting application efficiency and stability.

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-slopwatch -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/slopwatch/SKILL.md
Scanned
1 file, 293 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 enables AI agents to monitor .NET application performance and detect slop (unnecessary code or bloat) within the codebase. It provides automated insights into build times, resource usage, and potential inefficiencies in .NET projects.

When to use it

  • Analyze large .NET repositories to identify bloated modules slowing down compilation.
  • Monitor production builds for unexpected spikes in memory consumption or CPU load.
  • Automate code quality checks to flag deprecated libraries or inefficient algorithms before deployment.
  • Track performance regressions across multiple branches during active development cycles.

Key capabilities

  • Real-time monitoring of .NET application metrics.
  • Detection of code bloat and unnecessary dependencies.
  • Automated reporting on build efficiency and resource utilization.
  • Integration with existing .NET development workflows for continuous feedback.

Example prompts

  • "Run a slopwatch analysis on my current .NET project to identify any performance bottlenecks."
  • "Generate a report comparing the resource usage of two different versions of this .NET application."
  • "Alert me if the build time for this .NET solution exceeds 10 minutes due to code bloat."

Tips & gotchas

Ensure your .NET environment is properly configured with necessary profiling tools before running this skill. Limit analysis scope to specific projects or modules to avoid overwhelming system resources during peak usage times.