Skip to content
mcp/skillhub

Agent Skill

Grade Tests skill

grade-testsdotnet/skillsplugins/dotnet-test/skills/grade-tests/SKILL.md

Grade curated individual tests for readiness, A-F quality and improvements. ALWAYS USE FOR: grade tests, review only a named test, per-test readiness or quality bands for supplied methods, bodies, file spans or bounded PR diffs, including existing tests. Return Pass/Failed/Uncertain/Not applicable; unresolved/empty scopes omit grades. Compose read-only per-test evidence. Polyglot. DO NOT USE FOR: suite audits (test-engineer/test-anti-patterns), concrete fix/feature detection proof (test-value-evidence), writing/fixing tests, or coverage.

5.7kMIT

always on

119 tokname + description

once used

6,123 tokSKILL.md body

bundled files

0

repo stars

5.7kGitHub

Install the Grade Tests skill

Skills CLI (Claude Code, Codex, Cursor and others)

npx skills add https://github.com/dotnet/skills --skill grade-tests

Claude Code, by hand (all projects)

git clone --depth 1 https://github.com/dotnet/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -R /tmp/skills/plugins/dotnet-test/skills/grade-tests ~/.claude/skills/grade-tests

For one project only, copy the folder into .claude/skills/ in that project instead. The agent picks it up when a task matches its description.

What it costs your context

Agent Skills load in three steps. Tokens counted with the o200k tokenizer; your model's count will differ a little.

WhenWhat loadsCost
Every sessionName and description119 tok
When the agent uses itThe SKILL.md instructions6,123 tok
Only if openedNo bundled files—

Until it is used, grade-tests costs about 11× less than the median MCP server we measured (1,362 tokens on every turn). Installing all 114 skills from dotnet/skills would load 15,432 tokens of descriptions. Skills vs MCP study

Checks

  • The instructions are over 5,000 tokens, the Agent Skills specification's guideline for SKILL.md.

Checked 2026-10-22 · method

What's inside

The headings of its SKILL.md. Read the full file on GitHub.

  • Grade Tests
  • Why a Decision Result Plus Quality Detail
  • When to Use
  • When Not to Use
  • Inputs
  • Step 0: Validate the input
  • Workflow
  • Step 1: Detect language and load extension
  • Step 2: Resolve the test bodies
  • Step 3: Assess the claimed behavior and score each resolved test
  • Step 4: Assign the decision result
  • Step 5: Build the note
  • Step 6: Report
  • Validation
  • Common Pitfalls

More skills from dotnet/skills

All skills in this repo
  1. agentic-workflowsdotnet/skills

    Route gh-aw workflow design/create/debug/upgrade requests to the right prompts.

    5.7k20 tok idle · 1,336 in use
  2. analyzing-dotnet-performancedotnet/skills

    Scans .NET code for ~50 performance anti-patterns across async, memory, strings, collections, LINQ, regex, serialization, and I/O with tiered severity classification. Use when analyzing .NET code for optimization opportunities, reviewing hot paths, or auditing allocation-heavy patterns.

    5.7k64 tok idle · 2,744 in use
  3. android-tombstone-symbolicationdotnet/skills

    Symbolicate the .NET runtime frames in an Android tombstone file. Extracts BuildIds and PC offsets from the native backtrace, downloads debug symbols from the Microsoft symbol server, and runs llvm-symbolizer to produce function names with source file and line numbers. USE FOR triaging a .NET MAUI or Mono Android app crash from a tombstone, resolving native backtrace frames in libmonosgen-2.0.so or libcoreclr.so to .NET runtime source code, or investigating SIGABRT, SIGSEGV, or other native signals originating from the .NET runtime on Android. DO NOT USE FOR pure Java/Kotlin crashes, managed .NET exceptions that are already captured in logcat, or iOS crash logs. INVOKES Symbolicate-Tombstone.ps1 script, llvm-symbolizer, Microsoft symbol server.

    5.7k1176 tok idle · 1,948 in use
  4. apple-crash-symbolicationdotnet/skills

    Symbolicate .NET runtime frames in Apple platform .ips crash logs (iOS, tvOS, Mac Catalyst, macOS). Extracts UUIDs and addresses from the native backtrace, locates dSYM debug symbols, and runs atos to produce function names with source file and line numbers. Automatically downloads .dwarf symbols from the Microsoft symbol server using Mach-O UUIDs. USE FOR triaging a .NET MAUI or Mono app crash from an .ips file on any Apple platform, resolving native backtrace frames in libcoreclr or libmonosgen-2.0 to .NET runtime source code, retrieving .ips crash logs from a connected iOS device or iPhone, or investigating EXC_CRASH, EXC_BAD_ACCESS, SIGABRT, or SIGSEGV originating from the .NET runtime. DO NOT USE FOR pure Swift/Objective-C crashes with no .NET components, or Android tombstone files. INVOKES Symbolicate-Crash.ps1 script, atos, dwarfdump, idevicecrashreport.

    5.7k1217 tok idle · 2,267 in use
  5. assertion-qualitydotnet/skills

    Analyze assertion quality, depth, variety, and false confidence in existing tests. ALWAYS USE when asked about weak, shallow, trivial, always-true, self-referential, assertion-free, presence/truthiness-only, or insufficiently diverse assertions, including MSTest, Jest, pytest, and Go. DO NOT USE for direct fixes: writing-mstest-tests owns supplied MSTest assertions; code-testing owns new cases. Use test-gap-analysis when asked whether tests would catch a production change, and test-anti-patterns for general severity-ranked audits.

    5.7k114 tok idle · 4,201 in use
  6. author-componentdotnet/skills

    Create or review Blazor components (.razor files) with correct architecture. USE FOR: writing new Blazor components that do NOT involve JavaScript interop, implementing parameters and EventCallback, RenderFragment slots, component lifecycle (OnInitializedAsync, OnParametersSet), async patterns, IAsyncDisposable, CancellationToken, CSS isolation, code-behind. DO NOT USE FOR: creating new projects (use create-blazor-project), JavaScript interop or calling browser APIs from Blazor (use use-js-interop), forms and validation (use collect-user-input), prerendering issues (use support-prerendering), HTTP data fetching patterns (use fetch-and-send-data), coordinating state between unrelated components (use coordinate-components).

    5.7k148 tok idle · 658 in use
  7. authoring-github-workflowsdotnet/skills

    Author and review GitHub Actions workflow YAML safely so syntactically-valid YAML can't ship a workflow that GitHub Actions refuses to run. USE FOR: editing, adding, or reviewing any file under .github/workflows/, writing run-name/name/if/env/run values that contain ${{ }} expressions, diagnosing a run that fails with 'This run likely failed because of a workflow file issue' and no jobs starting, deciding when a workflow scalar must be quoted, validating workflows with actionlint. DO NOT USE FOR: authoring application YAML unrelated to GitHub Actions, Azure Pipelines, GitLab CI, or non-workflow YAML. SCOPE: this skill covers *syntactic/structural* correctness of workflow YAML (quoting, parsing, actionlint); for *semantic and functional* workflow design (what a workflow should do, agentic-workflow behavior), see .github/agents/agentic-workflows.agent.md — the two are complementary. INVOKES: actionlint (downloaded pinned binary) plus git/grep for inspection.

    5.7k218 tok idle · 1,990 in use
  8. binlog-failure-analysisdotnet/skills

    Analyze MSBuild binary logs to diagnose build failures. USE FOR: build errors that are unclear from console output, diagnosing cascading failures across multi-project builds, tracing MSBuild target execution order, and generally any MSBuild build issues. Requires an existing .binlog file. DO NOT USE FOR: generating binlogs (use binlog-generation), binlog MCP startup or connection failures (use troubleshoot-binlog-mcp), non-MSBuild build systems.

    5.7k94 tok idle · 654 in use