Agent skill · software engineering · jeremylongshore
mindtickle-upgrade-migration
Migrate a Mindtickle tenant contract, adapter, connector, identity mapping, or product configuration through compatibility and rollback gates. Use when a vendor or customer contract changes. Trigger with "migrate Mindtickle integration".
Why this skill is useful
Adds a comprehensive migration script and checklist for MindTickle API changes that are not publicly documented.
What it needs
Requires typescript installed locally. Requires mindtickle account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Controlled Mindtickle Contract Migration Overview Move from a frozen current contract to a verified target while preserving identity, data meaning, operational continuity, and a tested reversal path. Prerequisites Current and target artifacts with provenance, digests, effective dates, and vendor or customer owners Inventory of affected operations, fields, identities, mappings, reports, programs, and downstream consumers Representative sanitized fixtures, a migration window, communications, and rollback authority Tool Discipline Use Read, Glob, and Grep to inspect contracts, mappings, and consumers, WebFetch for current authorized change material, and Write or Edit for compatibility tests, migration plans, and redacted receipts. Current Contract Mindtickle may update subscription services and tenant capabilities, while customer profile fields, integrations, custom reports, and migrations can require separately scoped work. Do not infer API versioning or backward compatibility when the authorized artifacts do not state it. Authentication Validate target credential compatibility and scopes in non-production. Keep current and target credentials separately owned, prevent downgrade to broader access, and preserve revocation plans for both. Instructions 1. Freeze current and target contracts and build a semantic diff of operations, schemas, meanings, defaults, permissions, limits, and support status. 2. Trace every changed element to code, fixtures, identity mappings, reports, content, data stores, alerts, and business owners. 3. Classify changes as compatible, transformable, destructive, entitlement-dependent, or clarification required. 4. Define transformation, validation, duplicate prevention, reconciliation, retention, and rollback for each affected data set. 5. Run old fixtures against the new adapter and target fixtures against the compatibility boundary; include partial and ambiguous failures. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/mindtickle-upgrade-migration