Skip to content

feat: add Step 0 upgrade check — remove legacy v1/v2 scripts on skill download - #7

Open
IRONICBo wants to merge 2 commits into
memovai:mainfrom
IRONICBo:feat/skill-upgrade-cleanup
Open

feat: add Step 0 upgrade check — remove legacy v1/v2 scripts on skill download#7
IRONICBo wants to merge 2 commits into
memovai:mainfrom
IRONICBo:feat/skill-upgrade-cleanup

Conversation

@IRONICBo

@IRONICBo IRONICBo commented Apr 7, 2026

Copy link
Copy Markdown
Member

Summary

  • Adds a Step 0 to SKILL.md (and synced public/skill.md) that runs before registration
  • Detects legacy shell scripts written by v1/v2 of the skill (setup.sh, play.sh, keep-alive.sh, multi-agent.sh) in ~/.agentcasino/skills/agentcasino/scripts/ and ~/.agentcasino/
  • Removes them and reports what was cleaned up, or confirms nothing to clean
  • Cleans up the now-empty legacy scripts directory if applicable

Why

v1/v2 SKILL.md told agents to write auto-play scripts to disk. v3 explicitly bans scripts — every decision must be made interactively by the model. If an agent upgrades to v3 but still has old scripts on disk, those scripts can:

  • Be accidentally re-run, bypassing the v3 one-decision-at-a-time rule
  • Cause confusion about which version of the skill is active
  • Result in timeout kicks if the auto-play loop is broken

Test plan

  • Run Step 0 on a machine with no prior install → prints ✓ No legacy scripts found
  • Run Step 0 on a machine that ran v1/v2 → detects and removes the legacy files, prints confirmation
  • Verify public/skill.md and skills/poker/SKILL.md are identical after change

@vercel

vercel Bot commented Apr 7, 2026

Copy link
Copy Markdown

@IRONICBo is attempting to deploy a commit to the memov Team on Vercel.

A member of the Team first needs to authorize it.

@vercel

vercel Bot commented Apr 7, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
agentcasino Ready Ready Preview, Comment Apr 7, 2026 4:36am

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant