feat: improve skill scores for dotnet-skills

[rohan-tessl]

Hey 👋 @managedcode

I ran your skills through tessl skill review at work and found some targeted improvements.

Here's the full before/after:

Skill	Before	After	Change
dotnet-mcaf	44%	80%	+36%
dotnet-managedcode-orleans-graph	46%	76%	+30%
dotnet-winforms	49%	93%	+44%
dotnet-winui	49%	86%	+37%
dotnet-entity-framework6	53%	80%	+27%

This PR intentionally caps manual optimization at five skills to keep it reviewable. The included Tessl Skill Review workflow (see below) will surface feedback on future SKILL.md changes automatically.

Changes summary

dotnet-mcaf (44% → 80%): Consolidated repeated governance vs implementation boundary explanations into a single routing table, tightened the workflow to be more actionable, removed redundant prose.

dotnet-managedcode-orleans-graph (46% → 76%): Added concrete code examples (grain interface, traversal implementation), NuGet install command, fixed category to "Data, Distributed, and AI", added validation for bounded traversal depth.

dotnet-winforms (49% → 93%): Restructured to use SKILL.md as the control plane per CONTRIBUTING.md — moved massive inline code blocks to existing references/ files, kept concise MVP example and DI setup inline, added key decisions table and validation checkpoints. Fixed category to "Desktop and Mobile".

dotnet-winui (49% → 86%): Same restructuring — moved large inline code to references/, kept essential MVVM Toolkit and x:Bind examples inline, added key decisions table, packaging guidance, and XamlRoot validation note. Fixed category to "Desktop and Mobile".

dotnet-entity-framework6 (53% → 80%): Added concrete EF6 feature audit checklist, runtime vs ORM migration decision table with clear guidance, Mermaid decision flowchart, and specific validation checkpoints. Fixed category to "Data, Distributed, and AI".

All changes follow CONTRIBUTING.md conventions: SKILL.md stays as control plane, heavy content lives in references/, descriptions are precise quoted strings, and versions are bumped as patch for wording/structure improvements.

Tessl Skill Review GitHub Action

This PR also adds .github/workflows/skill-review.yml — a lightweight workflow that automatically reviews any SKILL.md changes on future PRs.

How it works and why it helps

• What runs: On PRs that change **/SKILL.md, the workflow runs tesslio/skill-review and posts one comment with Tessl scores and feedback (updated on new pushes).
• Zero extra accounts: Contributors do not need a Tessl login — only the repo's default GITHUB_TOKEN is used to post the comment.
• Non-blocking by default: Unless you add fail-threshold, the check is feedback-only — no surprise red CI.
• Not a build replacement: This is review automation for skill markdown quality, not a substitute for your catalog-check or publish pipelines.
• Optional gate: You can add with: fail-threshold: 70 later if you want PRs to fail on low skill scores.
• Why only five skills here: This PR caps manual optimization so it stays reviewable. After merge, every PR that touches SKILL.md gets automatic review comments, so the rest of the library improves incrementally.

Honest disclosure — I work at @tesslio where we build tooling around skills like these. Not a pitch - just saw room for improvement and wanted to contribute.

Want to self-improve your skills? Just point your agent (Claude Code, Codex, etc.) at this Tessl guide and ask it to optimize your skill. Ping me - @rohan-tessl - if you hit any snags.

Thanks in advance 🙏