speak-upgrade-migration
Upgrade Speak SDK versions, migrate between language learning platforms, and handle API version changes. Use when implementing upgrade migration features, or troubleshooting Speak language learning integration issues. Trigger with phrases like "speak upgrade migration", "speak upgrade migration". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill speak-upgrade-migration --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Speak Upgrade & Migration ## Overview Upgrade Speak SDK versions, migrate between language learning platforms, and handle API version changes. ## Prerequisites - Completed `speak-install-auth` setup - Valid API credentials configured - Understanding of Speak API patterns ## Instructions ## Current State !`npm list @speak/language-sdk 2>/dev/null || echo 'Speak SDK not installed'` ### Step 1: Che
What does the speak-upgrade-migration skill do?
Upgrade Speak SDK versions, migrate between language learning platforms, and handle API version changes. Use when implementing upgrade migration features, or troubleshooting Speak language learning integration issues. Trigger with phrases like "speak upgrade migration", "speak upgrade migration". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill speak-upgrade-migration --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
