Pattern for safely removing an obsolete package/distribution surface without breaking the surviving release path.
53
60%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.squad/skills/retire-legacy-distribution-surface/SKILL.mdUse 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.798c3c7
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.