dotnet-test: reduce assertion-quality over-structuring on small suites

plugins/dotnet-test/skills/assertion-quality/SKILL.md

@@ -116,6 +116,8 @@ Before reporting, calibrate findings:
 
 ### Step 6: Report findings
 
+**Scale the report depth to the size and complexity of the suite.** The structure below is the full template for a substantial suite (roughly 15+ tests or a multi-file project). For a small or simple input (a single file with only a handful of tests), do not emit every section — a padded multi-section dashboard on a trivial input reads as noise and buries the answer. Instead, answer the user's question directly and concisely: which tests are assertion-free or trivial-only, the overall assertion-quality verdict, and concrete recommendations (still distinguishing intentional smoke tests from tests masquerading as real verification). Use only the sections that carry real signal for the input at hand; a short metric summary plus the assertion-free list and recommendations is often enough. Never omit the rubric-relevant substance (assertion-free/trivial identification, the quality verdict, and concrete recommendations) — only trim structural overhead that adds no information.
+
 Present the analysis in this structure:
 
 1. **Summary Dashboard** — A quick-reference table of key metrics: