telerik/ai-plugins/telerik-for-dotnet-framework-upgrade
Claude Code and agent skill by telerik/ai-plugins
- community
Checking that the SKILL.md file is still in the repository.
Telerik UI for WinForms rules for a .NET Framework version upgrade (net4xx to net481) — verify the referenced Telerik version still supports net481, offer (never force) the assembly-to-NuGet migration, and keep licensing consistent with whichever reference mechanism the customer keeps.
Install
npx vskill@latest install telerik/ai-plugins/telerik-for-dotnet-framework-upgradeSKILL.md
Telerik UI for WinForms rules for the .NET Framework version upgrade
The platform's own compatibility data doesn't know about Telerik UI for WinForms, so a dotnet-framework-version-upgrade run must not decide anything about it without this guidance.
The rule that always holds: net4xx → net481 is a minor TFM bump. It usually does not force a Telerik version change — verify against the telerik-winforms-dependency-management compatibility matrix instead of assuming one is needed. Direct Telerik assembly references are a fully supported .NET Framework configuration; NuGet is a recommendation put to the customer, never a silent conversion.
Telerik presence is this extension's own responsibility to detect. The host scenario's traits (.NET, WinForms) only say the repository is a .NET WinForms solution — they cannot say whether Telerik specifically is referenced. Assessment checks for that, once, before any other step. If no project references Telerik, Planning, Execution, and IntegrityReview all contribute nothing and must not re-inspect the project themselves.
This body is what the IntegrityReview scope receives (it is declared in scope but left out of scopeInstructions). When reviewing the resulting change, confirm that:
- the referenced Telerik version supports
net481(verified, or upgraded to
one that does, if that was actually required);
- if the customer accepted the NuGet migration, no
<Reference>/HintPath
or packages.config entry for Telerik survives, and every added package shares one version;
- if the customer declined NuGet, no assembly reference was touched except to
repoint HintPath at a customer-supplied path for a required version bump;
- licensing (NuGet-transitive vs. Script Key) matches whichever reference
mechanism is actually in use.
This skill is a scenario extension: no workflow of its own, never user-selectable. It calls into telerik-winforms-reference-detection, telerik-winforms-dependency-management, telerik-winforms-assembly-mapping, telerik-winforms-reference-migration, telerik-winforms-reference-retargeting, telerik-winforms-license-detection, telerik-winforms-license-key-setup, telerik-winforms-license-nuget-migration, and telerik-winforms-migration-verification for the mechanics.
Security
- Security scanPassed, 90 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingplugins/telerik-winforms-upgrade-plugin/upgrade/skills/extensions/telerik-for-dotnet-framework-upgrade/SKILL.md
Popularity
- Repository stars
- 1
- 7-day trend score
- 0
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/telerik/ai-plugins/telerik-for-dotnet-framework-upgrade)