New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Legacy Aspnet

by managedcode in managedcode/dotnet-skills

Maintain classic ASP.NET applications on .NET Framework, including Web Forms, older MVC, and legacy hosting patterns, while planning realistic modernization boundaries.

MITAuto-check passedDevelopment

Install Legacy Aspnet

skills CLI
$ npx skills add managedcode/dotnet-skills --skill legacy-aspnet -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install managedcode/dotnet-skills legacy-aspnet --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/managedcode/dotnet-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/catalog/Platform/Legacy-ASP.NET/skills/legacy-aspnet .claude/skills/legacy-aspnet && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
legacy-aspnet
GitHub stars
486
Token cost
~598 tokens
SKILL.md length
216 words
Files
4 (incl. references)
Skills in repo
81
Repo updated
First seen
Licence
MIT

At a glance

Maintain classic ASP.NET applications on .NET Framework, including Web Forms, older MVC, and legacy hosting patterns, while planning realistic modernization boundaries.

  • Works in 6 steps: Treat classic ASP.NET as a distinct… → Stabilize behavior first: routing,… → Plan modernization in seams: isolate… → …
  • : working in Web Forms
  • SKILL.md covers Trigger On, Workflow, Deliver and Validate, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Legacy Aspnet is an agent skill from managedcode/dotnet-skills. Maintain classic ASP.NET applications on .NET Framework, including Web Forms, older MVC, and legacy hosting patterns, while planning realistic modernization boundaries. USE FOR: working in Web Forms, legacy MVC, or classic ASP.NET applications; reviewing old IIS-centric configuration and lifecycle behavior; planning migration toward ASP.NET Core. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant…

Its SKILL.md is about 600 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `manifest.json`, `references/migration.md` and `references/patterns.md`). Compatibility notes: Requires classic ASP.NET on .NET Framework.

It sits in Development, covering Legacy modernization and Codebase knowledge for agents. It works with ASP.NET Core and .NET. The repository describes itself as: Installable .NET skill catalog and CLI for Codex, Claude Code, GitHub Copilot, and Gemini. The licence is MIT.

When your agent uses it

  • : working in Web Forms
  • Classic ASP.NET applications
  • Reviewing old IIS-centric configuration and lifecycle behavior
  • Planning migration toward ASP.NET Core

Example prompts

  • “/legacy-aspnet”

Requirements

  • Compatibility (from SKILL.md): Requires classic ASP.NET on .NET Framework.

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Treat classic ASP.NET as a distinct stack with different hosting, lifecycle, and configuration rules from ASP.NET Core.
  2. Stabilize behavior first: routing, session, auth, server controls, configuration transforms, and deployment assumptions.
  3. Plan modernization in seams: isolate domain and service logic, then move replaceable edges instead of rewriting the whole app at once.
  4. Use wcf or entity-framework6 when the legacy app depends on those subsystems rather than flattening them into generic web work.
  5. Be careful with guidance copied from ASP.NET Core because middleware, DI, and hosting assumptions do not transfer directly.
  6. Validate in an environment that resembles real IIS and configuration transforms.

What it can do on your machine

Read from SKILL.md and the folder at commit 535dd55. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Requires classic ASP.NET on .NET Framework.

    From compatibility in the SKILL.md frontmatter.

Context cost

Legacy Aspnet loads about 598 tokens when it runs, and up to ~5.5k if it reads all its reference files. Until then it costs about 149 tokens; SKILL.md has 216 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~149
When it runs · the whole SKILL.md, loaded when a task matches
~598
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from managedcode/dotnet-skills at commit 535dd55, republished under its MIT licence (© managedcode). 216 words, ~598 tokens.

Download SKILL.mdSave it as .claude/skills/legacy-aspnet/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
legacy-aspnet
description
Maintain classic ASP.NET applications on .NET Framework, including Web Forms, older MVC, and legacy hosting patterns, while planning realistic modernization boundaries. USE FOR: working in Web Forms, legacy MVC, or classic ASP.NET applications; reviewing old IIS-centric configuration and lifecycle behavior; planning migration toward ASP.NET Core. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
compatibility
Requires classic ASP.NET on .NET Framework.

Legacy ASP.NET

Trigger On

  • working in Web Forms, legacy MVC, or classic ASP.NET applications
  • reviewing old IIS-centric configuration and lifecycle behavior
  • planning migration toward ASP.NET Core without breaking core business flows

Workflow

  1. Treat classic ASP.NET as a distinct stack with different hosting, lifecycle, and configuration rules from ASP.NET Core.
  2. Stabilize behavior first: routing, session, auth, server controls, configuration transforms, and deployment assumptions.
  3. Plan modernization in seams: isolate domain and service logic, then move replaceable edges instead of rewriting the whole app at once.
  4. Use wcf or entity-framework6 when the legacy app depends on those subsystems rather than flattening them into generic web work.
  5. Be careful with guidance copied from ASP.NET Core because middleware, DI, and hosting assumptions do not transfer directly.
  6. Validate in an environment that resembles real IIS and configuration transforms.

Deliver

  • practical maintenance guidance for classic ASP.NET
  • stabilized legacy behavior and modernization seams
  • a migration path that avoids unnecessary risk

Validate

  • classic and Core guidance are not mixed
  • legacy runtime assumptions are preserved deliberately
  • migration steps are incremental and testable

References

  • Migration Paths: strategies for migrating from ASP.NET to ASP.NET Core, including incremental migration, strangler fig pattern, and component-specific guidance
  • Maintenance Patterns: stabilization and maintenance patterns for legacy ASP.NET code, including abstraction layers, testing seams, and deployment practices

© managedcode, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references) in catalog/Platform/Legacy-ASP.NET/skills/legacy-aspnet of managedcode/dotnet-skills.

  • SKILL.md
  • manifest.json
  • references/migration.md
  • references/patterns.md

Open the folder on GitHubat commit 535dd55

Compare with similar skills

Legacy Aspnet next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Legacy Aspnet compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Legacy Aspnet this skillmanagedcode/dotnet-skills486—~598Automated safety check: PassMIT
Migrate Dotnet8 To Dotnet9dotnet/skills5.6k2 repos~3.9kAutomated safety check: PassMIT
Migrate Dotnet9 To Dotnet10dotnet/skills5.6k2 repos~4.8kAutomated safety check: PassMIT
Migrate Dotnet10 To Dotnet11dotnet/skills5.6k1 repos~3.6kAutomated safety check: PassMIT
Directory Build Organizationmicrosoft/testfx1k1 repos~2.5kAutomated safety check: PassMIT
Msbuild Antipatternsrunceel/ReactiveProperty944—~3.7kAutomated safety check: PassMIT

Similar skills

  • Migrate Dotnet8 To Dotnet9

    dotnet/skills

    Official

    Migrate a .NET 8 project to .NET 9 and resolve all breaking changes.

    5.6k GitHub starsUsed in 2 repos~3.9k tokens
    DevelopmentAuto-check passed

  • Migrate Dotnet9 To Dotnet10

    dotnet/skills

    Official

    Migrate a .NET 9 project or solution to .NET 10 and resolve all breaking changes.

    5.6k GitHub starsUsed in 2 repos~4.8k tokens
    DevOps & CloudAuto-check passed

  • Migrate Dotnet10 To Dotnet11

    dotnet/skills

    Official

    Migrate a .NET 10 project or solution to .NET 11 and resolve all breaking changes.

    5.6k GitHub starsUsed in 1 repo~3.6k tokens
    DevOps & CloudAuto-check passed

  • Directory Build Organization

    microsoft/testfx

    Official

    Guide for organizing MSBuild infrastructure with Directory.Build.props, Directory.Build.targets, Directory.Packages.props, and Directory.Build.rsp.

    1k GitHub starsUsed in 1 repo~2.5k tokens
    DevelopmentAuto-check passed

  • Msbuild Antipatterns

    runceel/ReactiveProperty

    Catalog of MSBuild anti-patterns with detection rules and fix recipes.

    944 GitHub stars~3.7k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

  • Msbuild Modernization

    microsoft/testfx

    Official

    Guide for modernizing and migrating MSBuild project files to SDK-style format.

    1k GitHub starsUsed in 3 repos~4.3k tokens
    DevelopmentAuto-check passed

More from managedcode/dotnet-skills

All 81 skills in this repo

  • Analyzer Config

    managedcode/dotnet-skills

    Use a repo-root .editorconfig to configure free .NET analyzer and style rules.

    486 GitHub stars~1.3k tokensUpdated today
    Auto-check passed

  • Archunitnet

    managedcode/dotnet-skills

    Use the open-source free ArchUnitNET library for architecture rules in .NET tests.

    486 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Aspire

    managedcode/dotnet-skills

    Build, upgrade, and operate Aspire 13.5.x C or TypeScript application hosts with the current CLI, AppHost, ServiceDefaults, integrations, dashboard, testing, MCP, and deployment patterns for…

    486 GitHub stars~3.6k tokensUpdated today
    Auto-check passed

  • Aspnet Core

    managedcode/dotnet-skills

    Build, debug, modernize, or review ASP.NET Core applications with correct hosting, middleware, security, configuration, logging, and deployment patterns on current .NET.

    486 GitHub stars~2.1k tokensUpdated today
    Auto-check passed

  • Asynkron Profiler

    managedcode/dotnet-skills

    Use the open-source free Asynkron.Profiler dotnet tool for CLI-first CPU, allocation, exception, contention, and heap profiling of .NET commands or existing trace artifacts.

    486 GitHub stars~1.7k tokensUpdated today
    Auto-check passed

  • Azure Functions

    managedcode/dotnet-skills

    Build, review, or migrate Azure Functions in .NET with correct execution model, isolated worker setup, bindings, DI, and Durable Functions patterns.

    486 GitHub stars~2.6k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Legacy Aspnet

What does Legacy Aspnet do?

Maintain classic ASP.NET applications on .NET Framework, including Web Forms, older MVC, and legacy hosting patterns, while planning realistic modernization boundaries. Legacy Aspnet is an agent skill from managedcode/dotnet-skills.NET Framework, including Web Forms, older MVC, and legacy hosting patterns, while planning realistic modernization boundaries.

When should I use Legacy Aspnet?

Legacy Aspnet fits situations like: : working in Web Forms; classic ASP.NET applications; reviewing old IIS-centric configuration and lifecycle behavior; planning migration toward ASP.NET Core.

How do I install Legacy Aspnet in Claude Code?

Run `npx skills add managedcode/dotnet-skills --skill legacy-aspnet -a claude-code`. Or copy the skill folder (catalog/Platform/Legacy-ASP.NET/skills/legacy-aspnet in managedcode/dotnet-skills) into .claude/skills/legacy-aspnet in your project. Claude Code loads it when a task matches its description.

How do I install Legacy Aspnet in Codex?

Run `npx skills add managedcode/dotnet-skills --skill legacy-aspnet -a codex`. Or copy the skill folder (catalog/Platform/Legacy-ASP.NET/skills/legacy-aspnet in managedcode/dotnet-skills) into .agents/skills/legacy-aspnet in your project. Codex loads it when a task matches its description.

Can I use Legacy Aspnet in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add managedcode/dotnet-skills --skill legacy-aspnet -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/legacy-aspnet, .gemini/skills/legacy-aspnet, .github/skills/legacy-aspnet and .opencode/skills/legacy-aspnet in your project.

What does Legacy Aspnet need to run?

SKILL.md names no scripts, command-line tools or credentials: Legacy Aspnet is instructions for the agent only. Compatibility (from SKILL.md): Requires classic ASP.NET on .NET Framework..

Does Legacy Aspnet access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Legacy Aspnet safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Legacy Aspnet use?

Legacy Aspnet is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Legacy Aspnet use?

About 598 tokens (SKILL.md is roughly 2.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.9k tokens, read only when the agent opens those files.

What are the alternatives to Legacy Aspnet?

Skills that share tags, products or a category with Legacy Aspnet: Migrate Dotnet8 To Dotnet9 (dotnet/skills, 5.6k stars), Migrate Dotnet9 To Dotnet10 (dotnet/skills, 5.6k stars), Migrate Dotnet10 To Dotnet11 (dotnet/skills, 5.6k stars) and Directory Build Organization (microsoft/testfx, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Legacy Aspnet?

managedcode (a GitHub organization) maintains it in managedcode/dotnet-skills, which has 486 GitHub stars. The repository holds 81 skills in this directory. The repository was last updated on October 7, 2026.

Source: managedcode/dotnet-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.