From clari-pack
Handles Clari API version changes and export schema migrations, including v3 to v4 migration, schema change detection, and database migration.
How this skill is triggered — by the user, by Claude, or both
Slash command
/clari-pack:clari-upgrade-migrationThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Handle Clari API changes: version migrations, export schema updates, and Copilot API adoption.
Handle Clari API changes: version migrations, export schema updates, and Copilot API adoption.
# v4 is the current version
curl -s -H "apikey: ${CLARI_API_KEY}" \
https://api.clari.com/v4/export/forecast/list | jq .
# If using v3 (deprecated), migrate to v4
def detect_schema_changes(
current_export: dict, expected_fields: set[str]
) -> dict:
if not current_export.get("entries"):
return {"status": "empty", "changes": []}
actual_fields = set(current_export["entries"][0].keys())
new_fields = actual_fields - expected_fields
removed_fields = expected_fields - actual_fields
return {
"status": "changed" if new_fields or removed_fields else "compatible",
"new_fields": list(new_fields),
"removed_fields": list(removed_fields),
}
# Track expected schema
EXPECTED_FIELDS = {
"ownerName", "ownerEmail", "forecastAmount", "quotaAmount",
"crmTotal", "crmClosed", "adjustmentAmount", "timePeriod"
}
-- Add new columns when Clari adds export fields
ALTER TABLE clari_forecasts ADD COLUMN IF NOT EXISTS new_field_name VARCHAR;
-- Backfill historical data
UPDATE clari_forecasts SET new_field_name = 'default' WHERE new_field_name IS NULL;
Keep the previous client version alongside the new one until migration is verified:
# Pin client to specific behavior
client_v4 = ClariClient(ClariConfig(api_key=api_key, base_url="https://api.clari.com/v4"))
For CI integration, see clari-ci-integration.
npx claudepluginhub pw00kt/fuzzy-sniffle --plugin clari-pack2plugins reuse this skill
First indexed Jul 18, 2026
Handles Clari API version changes and export schema migrations, including v3 to v4 migration, schema change detection, and database migration.
Upgrades klaviyo-api SDK versions and migrates between Klaviyo API revisions, handling breaking changes from legacy v1/v2 APIs to the current REST API.
Guides MindTickle upgrade and migration (trigger: 'mindtickle upgrade migration'), including API version detection, schema changes, and integration updates for courses, quizzes, user progress, and coaching sessions.