Analyze, plan, and execute Clay SDK upgrades with breaking change detection. Use when upgrading Clay SDK versions, detecting deprecations, or migrating to new API versions. Trigger with phrases like "upgrade clay", "clay migration", "clay breaking changes", "update clay SDK", "analyze clay version".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill clay-upgrade-migration74
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Guide for upgrading Clay SDK versions and handling breaking changes.
npm list @clay/sdk
npm view @clay/sdk versionopen https://github.com/clay/sdk/releasesgit checkout -b upgrade/clay-sdk-vX.Y.Z
npm install @clay/sdk@latest
npm testUpdate import statements, configuration, and method signatures as needed.
| SDK Version | API Version | Node.js | Breaking Changes |
|---|---|---|---|
| 3.x | 2024-01 | 18+ | Major refactor |
| 2.x | 2023-06 | 16+ | Auth changes |
| 1.x | 2022-01 | 14+ | Initial release |
// Before (v1.x)
import { Client } from '@clay/sdk';
// After (v2.x)
import { ClayClient } from '@clay/sdk';// Before (v1.x)
const client = new Client({ key: 'xxx' });
// After (v2.x)
const client = new ClayClient({
apiKey: 'xxx',
});npm install @clay/sdk@1.x.x --save-exact// Monitor for deprecation warnings in development
if (process.env.NODE_ENV === 'development') {
process.on('warning', (warning) => {
if (warning.name === 'DeprecationWarning') {
console.warn('[Clay]', warning.message);
// Log to tracking system for proactive updates
}
});
}
// Common deprecation patterns to watch for:
// - Renamed methods: client.oldMethod() -> client.newMethod()
// - Changed parameters: { key: 'x' } -> { apiKey: 'x' }
// - Removed features: Check release notes before upgradingFor CI integration during upgrades, see clay-ci-integration.
22fc789
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.