BF roslyn-analyzers
Build, review, debug, package, and test Roslyn diagnostic analyzers, code fix providers, and incremental source generators. Use for DiagnosticAnalyzer, CodeFixProvider, IIncrementalGenerator, IOperation analysis, Microsoft.CodeAnalysis dependency pinning, Roslyn test harnesses, C#/VB tests, and analyzer NuGet packaging.
Build, review, debug, package, and test Roslyn diagnostic analyzers, code fix providers, and incremental source generators.
As a process F 35/100 · Will not run — References files that are not bundled: references/SourceWriter.cs, references/CSharpCodeFixVerifier.cs
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 8353 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: references/SourceWriter.cs - warning
missing-refreference to a missing file: references/CSharpCodeFixVerifier.cs
Process rating: all ten parameters 35/100
- 0Tools and files. 2 referenced file(s) missing: references/SourceWriter.cs, references/CSharpCodeFixVerifier.cs
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Execution cost. Instruction body is 8353 tokens: crowds the task out of the window
- 55Failures and branches. 1 branches
- 85Steps. 83 steps, 2 vague phrases
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- low 12 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 321: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 83 items
- +4Has examples (16 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.