Use this skill when reviewing an ASP.NET Core API for backward compatibility, authentication, persistence and performance risks before it ships.
SkillScore95Maintained
Automatic
◆Coding pack
Last verified 8/3/2026
What it changes
Passed 21 of 22 test cases with the skill, and 19 of 22 without it.
Without skill86%
With skill95%
Checks it passed that the model alone missed
Omits method syntax and variable naming style preferences from the risk findings.
Identifies the inline ToList call inside the Select projection as an N+1 database query hazard.
2 fixed19 passed either way1 still failing0 broke
Pass-rate lift
+9 pp
Tokens
-11%
Agent turns
0%
Response time
-89%
Model gemini-3.6-flashMeasured 8/3/2026v121 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 2
Prompt
During review of `Controllers/ReportsController.cs`, you notice the developer used block-bodied methods `public IActionResult Get() { return Ok(); }` instead of expression-bodied methods `public IActionResult Get() => Ok();`, and local variables use `mgr` instead of `reportManager`. Determine how to present these items in the review findings report.
What was checked, without and with the skill
Checked
Without skill
With skill
Omits method syntax and variable naming style preferences from the risk findings.
Missed
Passed
case-08 · gemini-3.6-flash · 8/3/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md34 lines2 files
.NET API Review
Use this skill when reviewing ASP.NET Core APIs. It is also SkillForge's own documentation example, so
it is written the way a real, useful skill should be.
Goals
Detect backward compatibility risks before they reach a published contract.
Review authentication and authorization on every reachable endpoint.
Identify performance bottlenecks in persistence access.
Produce findings a developer can act on without further investigation.
Workflow
Inventory the surface. List controllers, minimal API endpoints and their routes. Note which are
anonymous.
Review contracts. For each request and response type, check whether a change would break an
existing client: removed fields, narrowed types, changed enum values, altered status codes.
Review authentication. Confirm every endpoint either requires authorization or is deliberately
anonymous. Treat a missing attribute as anonymous, not as an oversight to assume away.
Review persistence. Look for N+1 access patterns, queries without pagination, and unbounded
result sets.
Report findings ordered by severity, each with the file, the risk, and the smallest change that
resolves it.
What not to do
Do not rewrite the API's architecture as part of a review.
Do not report style preferences as risks.
Do not claim an endpoint is secure. Report what was checked and what was found.
Amazon A+ Content strategy and creation. Module layouts, persuasive copy, comparison charts, image briefs, and conversion optimization. Use when the user asks about A+ Content, Enhanced Brand Content, product storytelling, or Amazon listing enhancement.