Scans .NET code for ~50 performance anti-patterns across async, memory, strings, collections, LINQ, regex, serialization, and I/O with tiered severity classification.
SkillScore83Maintained
Automatic
◆Coding pack
Last verified 9/8/2026
What it changes
Passed 17 of 20 test cases with the skill, and 15 of 20 without it.
Without skill74%
With skill83%
Checks it passed that the model alone missed
Flags cross-file pattern inconsistency as Moderate severity
Escalates severity to Moderate due to having over 50 instances
Outputs a scan execution checklist showing each recipe and hit count
3 fixed16 passed either way3 still failing1 broke
Pass-rate lift
+9 pp
Tokens
+129%
Agent turns
0%
Response time
-5%
Model gemini-3.6-flashMeasured 9/8/2026v219 of 23 cases passed with skill · 20 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 3
Prompt
In `src/Handlers/OrderHandler.cs`, `StringComparison.Ordinal` is used for string comparisons, but in sibling file `src/Handlers/InvoiceHandler.cs` in the same directory, standard `.ToLower()` comparison is used. How should this cross-file inconsistency be reported?
What was checked, without and with the skill
Checked
Without skill
With skill
Flags cross-file pattern inconsistency as Moderate severity
Missed
Passed
case-15 · gemini-3.6-flash · 9/8/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md204 lines8 files
.NET Performance Patterns
Scan C#/.NET code for performance anti-patterns and produce prioritized findings with concrete fixes. Patterns sourced from the official .NET performance blog series, distilled to customer-actionable guidance.
When to Use
Reviewing C#/.NET code for performance optimization opportunities
Auditing hot paths for allocation-heavy or inefficient patterns
Systematic scan of a codebase for known anti-patterns before release
Second-opinion analysis after manual performance review
When Not to Use
Algorithmic complexity analysis — this skill targets API usage patterns, not algorithm design
Code not on a hot path with no performance requirements — avoid premature optimization
Inputs
Input
Required
Description
Source code
Yes
C# files, code blocks, or repository paths to scan
Hot-path context
Recommended
Which code paths are performance-critical
Target framework
Recommended
.NET version (some patterns require .NET 8+)
Scan depth
Optional
critical-only, standard (default), or comprehensive
Workflow
Step 1: Load Critical Reference
Resolve bundled paths from the directory that contains this SKILL.md, not from the user's workspace. Load this reference file first:
references/critical-patterns.md
If a direct read fails, list this skill's references/ directory once and retry only when the listing shows the expected file. Do not use workspace file or text search to locate the skill installation.
Step 2: Detect Code Signals and Select Topic Recipes
Scan the code for signals that indicate which pattern categories to check. Use the ## Detection section from the critical reference when available and the inline recipes in Step 3 for initial signal detection.
After detecting signals, load only the topic-specific references selected by scan depth:
Analyzes the variety and depth of assertions across test suites in any language. Use when the user asks to evaluate assertion quality, find shallow tests, identify assertion-free tests (no assertions or only trivial ones like Assert.IsNotNull / toBeTruthy()), flag self-referential or tautological assertions, measure assertion diversity, or audit whether tests verify different facets of behavior. Polyglot: .NET, Python, TS/JS, Java, Go, Ruby, Rust, Swift, Kotlin, PowerShell, C++. DO NOT USE FOR: