Skip to content
TrustedSkillsbeta
Back to all skills

Dotnet Testing Test Output Logging

Checked
kevintsengtw·vlatest·testing·MIT

Logs detailed test output from .NET tests (MSTest, xUnit, NUnit) for improved debugging and analysis.

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 kevintsengtw/dotnet-testing-agent-skills --skill dotnet-testing-test-output-logging -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

kevintsengtw

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 kevintsengtw/dotnet-testing-agent-skills at 4e34a97764.

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

Commit
4e34a97764
Manifest
skills/dotnet-testing-test-output-logging/SKILL.md
Scanned
4 files, 852 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 allows AI agents to capture and analyze test output from .NET tests. It can extract information like test results, error messages, and stack traces directly from the console output of a running test process. This enables automated analysis of testing failures and improved debugging workflows.

When to use it

  • Automated Failure Analysis: Automatically identify and categorize failing tests in a CI/CD pipeline.
  • Debugging Assistance: Provide detailed error information, including stack traces, directly to developers for faster troubleshooting.
  • Test Result Reporting: Generate comprehensive test reports with extracted data from console output.
  • Integration Testing: Capture and analyze output from integration tests that rely on console logging for feedback.

Key capabilities

  • Captures standard output and error streams from .NET test processes.
  • Extracts relevant information like test results, errors, and stack traces.
  • Supports various testing frameworks commonly used in the .NET ecosystem.

Example prompts

  • "Analyze the console output of my unit tests and report any failures."
  • "Extract all error messages and stack traces from the last run of my integration tests."
  • "Generate a summary report of test results, including the number of passed, failed, and skipped tests."

Tips & gotchas

  • Ensure that your .NET tests are configured to output relevant information to the console.
  • The skill's effectiveness depends on the clarity and consistency of the test output format.