Pattern for safely removing an obsolete package/distribution surface without breaking the surviving release path.
53
—
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Use this when a repo has replaced one publish/install surface with another, but old package directories or workflow steps still linger.
packages/excel-*-skill directories.release.yml populate/upload/publish steps.Build-AgentSkills.ps1 and scripts/pre-commit.ps1 so they only validate the surviving ZIP artifact.publish-plugins.yml and the sbroenne/mcp-server-excel-plugins marketplace flow intact.b268be5
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.