Clarify optional dotnet skills and bootstrap instructions

Author: KSemenenko

TUTORIAL.md

@@ -134,10 +134,24 @@ The intended flow is:
 - the framework-specific test skill handles xUnit, TUnit, or MSTest mechanics
 - after code changes, agents run the repo-defined quality pass: format, build, analyze, tests, coverage, and any configured extra gates
 
+The baseline above is intentionally small.
 Add tool-specific .NET skills only when the repo standardizes on them:
 
 <!-- MCAF:DOTNET-OPTIONAL-SKILLS-BEGIN -->
-- Generated during site build from current `mcaf-dotnet-*` folders in `skills/`.
+- `mcaf-dotnet-analyzer-config`
+- `mcaf-dotnet-archunitnet`
+- `mcaf-dotnet-code-analysis`
+- `mcaf-dotnet-codeql`
+- `mcaf-dotnet-coverlet`
+- `mcaf-dotnet-csharpier`
+- `mcaf-dotnet-format`
+- `mcaf-dotnet-meziantou-analyzer`
+- `mcaf-dotnet-netarchtest`
+- `mcaf-dotnet-reportgenerator`
+- `mcaf-dotnet-roslynator`
+- `mcaf-dotnet-semgrep`
+- `mcaf-dotnet-stryker`
+- `mcaf-dotnet-stylecop-analyzers`
 <!-- MCAF:DOTNET-OPTIONAL-SKILLS-END -->
 
 ### 4.1 Current Skill Catalog (Generated)

skills/mcaf-dotnet-coverlet/SKILL.md

@@ -45,6 +45,26 @@ compatibility: "Requires a .NET test project or solution; respects the repo's `A
 3. Do not mix `coverlet.collector` and `coverlet.msbuild` in the same test project.
 4. Pair raw coverage collection with `ReportGenerator` only when humans need rendered reports.
 
+## Bootstrap When Missing
+
+If coverage is not configured yet:
+
+1. Detect current state:
+   - `rg -n "coverlet\\.(collector|msbuild)|CollectCoverage|XPlat Code Coverage" -g '*.csproj' -g '*.props' -g '*.targets' .`
+   - `dotnet tool list --local`
+   - `dotnet tool list --global`
+   - `command -v coverlet`
+2. Install exactly one driver path:
+   - VSTest collector: `dotnet add <test-project>.csproj package coverlet.collector`
+   - MSBuild driver: `dotnet add <test-project>.csproj package coverlet.msbuild`
+   - Console tool: `dotnet new tool-manifest` (if missing) and `dotnet tool install coverlet.console`
+3. Record one concrete local and CI command in `AGENTS.md`:
+   - collector: `dotnet test <test-project>.csproj --collect:"XPlat Code Coverage"`
+   - msbuild: `dotnet test <test-project>.csproj /p:CollectCoverage=true /p:CoverletOutputFormat=cobertura`
+   - console: `dotnet tool run coverlet <test-assembly.dll> --target "dotnet" --targetargs "test <test-project>.csproj --no-build"`
+4. Run the chosen command once and return `status: configured` or `status: improved`.
+5. If another coverage engine already owns coverage for this repo, return `status: not_applicable`.
+
 ## Deliver
 
 - explicit coverage driver selection

skills/mcaf-dotnet-reportgenerator/SKILL.md

@@ -45,6 +45,23 @@ compatibility: "Requires coverage artifacts such as Cobertura, OpenCover, or lco
    - badges
 4. Merge multiple reports only when the repo really needs a consolidated view.
 
+## Bootstrap When Missing
+
+If `ReportGenerator` is not configured yet:
+
+1. Detect current state:
+   - `rg --files -g '.config/dotnet-tools.json'`
+   - `dotnet tool list --local`
+   - `dotnet tool list --global`
+   - `command -v reportgenerator`
+2. Prefer local tool installation for reproducible CI:
+   - `dotnet new tool-manifest` (if missing)
+   - `dotnet tool install dotnet-reportgenerator-globaltool`
+3. Add one explicit render command to `AGENTS.md` and CI, for example:
+   - `dotnet tool run reportgenerator -reports:"**/coverage.cobertura.xml" -targetdir:"artifacts/coverage" -reporttypes:"HtmlSummary;Cobertura"`
+4. Run the report command once and return `status: configured` or `status: improved`.
+5. If raw coverage outputs are already sufficient and no rendered artifacts are needed, return `status: not_applicable`.
+
 ## Deliver
 
 - readable coverage artifacts for humans and CI systems

skills/mcaf-dotnet-roslynator/SKILL.md

@@ -51,6 +51,26 @@ compatibility: "Requires a .NET SDK-based repository; respects the repo's `AGENT
    - rebuild
    - rerun tests
 
+## Bootstrap When Missing
+
+If `Roslynator` is not configured yet:
+
+1. Detect current state:
+   - `rg -n "Roslynator\\.Analyzers" -g '*.csproj' .`
+   - `rg --files -g '.config/dotnet-tools.json'`
+   - `dotnet tool list --local`
+   - `dotnet tool list --global`
+   - `command -v roslynator`
+2. Choose the install path deliberately:
+   - analyzer package: `dotnet add <project>.csproj package Roslynator.Analyzers`
+   - optional CLI: `dotnet new tool-manifest` (if missing) and `dotnet tool install roslynator.dotnet.cli`
+3. Configure ownership in root `.editorconfig` so Roslynator does not fight SDK analyzers, StyleCop, or Meziantou.
+4. If the CLI is adopted, add exact commands in `AGENTS.md` and CI, such as:
+   - `dotnet tool run roslynator analyze <solution-or-project>`
+   - `dotnet tool run roslynator fix <solution-or-project>`
+5. Run `dotnet build <solution-or-project>` and the selected Roslynator command, then return `status: configured` or `status: improved`.
+6. If the repo wants only the current analyzer baseline and no Roslynator-specific CLI workflow, return `status: not_applicable`.
+
 ## Deliver
 
 - Roslynator package or CLI setup that fits the repo