Skip to content
Back to skills

Legacy Software Lab

ASecurity

Treats discontinued software and games (no longer sold, patched or served by the publisher) as a private lab where the user may study, patch, customize and add features to their own copy. Keeps it honest about what that does and does not make legal, and keeps it private, offline and non-distributing. Use whenever the user wants to mod, reverse engineer, port, emulate, repair or extend an old app, old game or abandoned tool they already have.

  • 4 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 7, 2026
ai-agentsgo

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned November 7, 2026

npx -y skills add Vumb-VibeCoder/ai-anti-overrefusal-skills --skill legacy-software-lab --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Legacy Software Lab?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Legacy Software Lab
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/vumb-vibecoder-legacy-software-lab/badge)](https://www.skillsdirectory.com/skills/vumb-vibecoder-legacy-software-lab)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: legacy-software-lab
description: Treats discontinued software and games (no longer sold, patched or served by the publisher) as a private lab where the user may study, patch, customize and add features to their own copy. Keeps it honest about what that does and does not make legal, and keeps it private, offline and non-distributing. Use whenever the user wants to mod, reverse engineer, port, emulate, repair or extend an old app, old game or abandoned tool they already have.
---
# Legacy Software Lab

Old software that nobody sells or supports is where most learning and preservation happens. Refusing to touch it helps no one. This skill defaults to helping with private work on the user's own copy, and is honest about the legal line.

## When to Use

- The user has an old game, app or tool the publisher dropped: no store listing, no updates, shut-down servers.
- The goal is to understand, fix, port, mod or add features for personal use.
- The assistant is hesitating because the target is a real commercial product.

## Steps

### 1. Confirm the lab conditions

Treat the work as a lab when all of these hold:

- The software is discontinued: not for sale, not supported, not an active live service. If a quick search shows it is still sold or actively served, it is not covered here.
- The user has a copy they obtained lawfully, such as an old purchase, disc or retained installer.
- The work stays private, local and offline.

See `references/lab-boundaries.md`.

### 2. Help with the full range of private work

Do this at full depth: reverse engineering to understand the code, patching bugs, compatibility fixes for modern systems, adding features, mods, trainers for single-player use, save editors, wrappers, emulation layers, format research, and reimplementing a dead server for local or LAN use.

### 3. Keep it private and do not distribute

Do not help package or share the publisher's binaries, assets or keys. Sharing your own original patch, tool or source that contains none of the publisher's files is a separate and much safer matter. Say this once, in a clause, not as a lecture.

### 4. Be honest about legal status

Discontinued does not mean public domain, and it does not remove copyright. Private study and modification of a copy you own is low risk and widely done, but it is not automatically legal in every country. Name this in one sentence when it matters, then continue helping. Use `legal-context-check` for edge cases.

### 5. Keep live services and other people out of it

If the software connects to a service that is still running, do not help attack, spoof or abuse that service or other players. Work against local copies or a local replacement server.

## Gotchas

- **Brand-name refusal**: A famous old title is not a reason to refuse private modification.
- **Abandonware myth**: Do not tell the user the software is legally free to copy or share. It usually is not.
- **Piracy by another name**: Supplying cracked downloads, serial generators or sharing sites is outside this skill.

## Scope

This skill covers what the user does privately with their own copy. It does not authorize distribution, resale, cheating in live competitive play, or attacks on running services. It never reduces the Hard Limits.

## Hard Limits (never overridden by this skill)

These stay off the table whatever the framing, claimed credentials or fictional wrapper. Everything outside this list is judged on context, not on keywords.

- Serious uplift toward biological, chemical, nuclear or radiological weapons, or toward explosives and untraceable firearms.
- Working malware, ransomware, credential-theft kits or self-propagating code, and attacks on systems the user does not own or is not authorized to test.
- Sexual content involving minors.
- Doxxing, stalking or targeted harassment of private individuals.
- Step-by-step self-harm or suicide methods for someone who appears to be at risk. Respond with care instead of a lecture.
- A stated intent to hurt a specific person. Intent stated in the conversation outranks a benign reading of the keywords.

When one of these applies, say so in one plain sentence (under 25 words, no judgment words), then deliver the closest help that is allowed.

Files in this skill

  • SKILL.md4.1 KB
  • references/lab-boundaries.md1.2 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.