mindtickle-upgrade-migration
Upgrade Migration for MindTickle. Trigger: "mindtickle upgrade migration".
Best use case
mindtickle-upgrade-migration is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Upgrade Migration for MindTickle. Trigger: "mindtickle upgrade migration".
Teams using mindtickle-upgrade-migration should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/mindtickle-upgrade-migration/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How mindtickle-upgrade-migration Compares
| Feature / Agent | mindtickle-upgrade-migration | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Upgrade Migration for MindTickle. Trigger: "mindtickle upgrade migration".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
SKILL.md Source
# MindTickle Upgrade & Migration
## Overview
MindTickle is a sales enablement and readiness platform with APIs for managing courses, quizzes, user progress, and coaching sessions. The API exposes endpoints for content management, learner analytics, and CRM integration. Tracking API changes is essential because MindTickle evolves its content schema (course structures, quiz question types, scoring rubrics), user progress tracking fields, and SSO/SCIM provisioning models — breaking integrations that sync training completion data to Salesforce or automate onboarding workflows.
## Version Detection
```typescript
const MINDTICKLE_BASE = "https://api.mindtickle.com/v2";
async function detectMindTickleVersion(apiKey: string): Promise<void> {
const res = await fetch(`${MINDTICKLE_BASE}/users`, {
headers: { Authorization: `Bearer ${apiKey}`, "Content-Type": "application/json" },
});
const version = res.headers.get("x-mt-api-version") ?? "v2";
console.log(`MindTickle API version: ${version}`);
// Check for deprecated course fields
const coursesRes = await fetch(`${MINDTICKLE_BASE}/courses?limit=1`, {
headers: { Authorization: `Bearer ${apiKey}` },
});
const data = await coursesRes.json();
const knownFields = ["id", "title", "modules", "status", "created_at", "assigned_users"];
if (data.courses?.[0]) {
const actual = Object.keys(data.courses[0]);
const newFields = actual.filter((f) => !knownFields.includes(f));
if (newFields.length) console.log(`New course fields: ${newFields.join(", ")}`);
}
}
```
## Migration Checklist
- [ ] Review MindTickle release notes for API schema changes
- [ ] Audit codebase for hardcoded course status enums (`draft`, `published`, `archived`)
- [ ] Verify quiz question type support — new types may require parser updates
- [ ] Check user progress response for new completion metric fields
- [ ] Update SCIM provisioning payload if user attribute schema changed
- [ ] Test coaching session API for new rubric scoring fields
- [ ] Validate CRM sync field mappings (Salesforce/HubSpot) after API update
- [ ] Check if module ordering mechanism changed (position vs. sort_order)
- [ ] Update webhook handlers for course completion and quiz score events
- [ ] Run learner analytics export to verify report format compatibility
## Schema Migration
```typescript
// MindTickle course progress: flat completion → structured module-level tracking
interface OldProgress {
user_id: string;
course_id: string;
completed: boolean;
score: number;
completed_at?: string;
}
interface NewProgress {
user_id: string;
course_id: string;
status: "not_started" | "in_progress" | "completed" | "expired";
overall_score: number;
modules: Array<{
module_id: string;
status: string;
score: number;
attempts: number;
time_spent_seconds: number;
}>;
certifications: Array<{ cert_id: string; issued_at: string; expires_at?: string }>;
completed_at?: string;
}
function migrateProgress(old: OldProgress): NewProgress {
return {
user_id: old.user_id,
course_id: old.course_id,
status: old.completed ? "completed" : "not_started",
overall_score: old.score,
modules: [],
certifications: [],
completed_at: old.completed_at,
};
}
```
## Rollback Strategy
```typescript
class MindTickleClient {
private apiVersion: "v1" | "v2";
constructor(private apiKey: string, version: "v1" | "v2" = "v2") {
this.apiVersion = version;
}
async getCourses(limit = 50): Promise<any> {
try {
const res = await fetch(`https://api.mindtickle.com/${this.apiVersion}/courses?limit=${limit}`, {
headers: { Authorization: `Bearer ${this.apiKey}` },
});
if (!res.ok) throw new Error(`MindTickle ${res.status}`);
return await res.json();
} catch (err) {
if (this.apiVersion === "v2") {
console.warn("Falling back to MindTickle API v1");
this.apiVersion = "v1";
return this.getCourses(limit);
}
throw err;
}
}
}
```
## Error Handling
| Migration Issue | Symptom | Fix |
|----------------|---------|-----|
| Course status enum expanded | `400` creating course with unrecognized status value | Fetch valid statuses from `/courses/statuses` endpoint |
| Quiz question type unsupported | Quiz import fails with `unknown_question_type` | Add parser support for new question types (drag-drop, hotspot) |
| SCIM attribute renamed | User provisioning fails with `invalid attribute` | Update SCIM payload to match current user schema from `/schemas` |
| Progress field restructured | Code crashes accessing `progress.completed` (now `progress.status`) | Update to check `status === "completed"` instead of boolean |
| Webhook signature algorithm changed | Webhook verification fails on all events | Update HMAC verification to use new algorithm from MindTickle docs |
## Resources
- [MindTickle Integrations](https://www.mindtickle.com/platform/integrations/)
- [MindTickle API Documentation](https://developers.mindtickle.com/)
## Next Steps
For CI pipeline integration, see `mindtickle-ci-integration`.Related Skills
workhuman-upgrade-migration
Workhuman upgrade migration for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman upgrade migration".
wispr-upgrade-migration
Wispr Flow upgrade migration for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr upgrade migration".
windsurf-upgrade-migration
Upgrade Windsurf IDE, migrate settings from VS Code or Cursor, and handle breaking changes. Use when upgrading Windsurf versions, migrating from another editor, or handling configuration changes after updates. Trigger with phrases like "upgrade windsurf", "windsurf update", "migrate to windsurf", "windsurf from cursor", "windsurf from vscode".
windsurf-migration-deep-dive
Migrate to Windsurf from VS Code, Cursor, or other AI IDEs with full configuration transfer. Use when migrating a team to Windsurf, transferring Cursor rules, or evaluating Windsurf against other AI editors. Trigger with phrases like "migrate to windsurf", "switch to windsurf", "windsurf from cursor", "windsurf from copilot", "windsurf evaluation".
webflow-upgrade-migration
Analyze, plan, and execute Webflow SDK upgrades (webflow-api v1 to v3) with breaking change detection, API v1-to-v2 migration, and deprecation handling. Trigger with phrases like "upgrade webflow", "webflow migration", "webflow breaking changes", "update webflow SDK", "webflow v1 to v2".
webflow-migration-deep-dive
Execute major Webflow migrations — from other CMS platforms to Webflow CMS, between Webflow sites, or large-scale content re-architecture using the Data API v2 bulk endpoints, strangler fig pattern, and data validation. Trigger with phrases like "migrate to webflow", "webflow migration", "import into webflow", "webflow replatform", "move content to webflow", "webflow bulk import", "wordpress to webflow".
vercel-upgrade-migration
Upgrade Vercel CLI, Node.js runtime, and Next.js framework versions with breaking change detection. Use when upgrading Vercel CLI versions, migrating Node.js runtimes, or updating Next.js between major versions on Vercel. Trigger with phrases like "upgrade vercel", "vercel migration", "vercel breaking changes", "update vercel CLI", "next.js upgrade on vercel".
vercel-migration-deep-dive
Migrate to Vercel from other platforms or re-architecture existing Vercel deployments. Use when migrating from Netlify, AWS, or Cloudflare to Vercel, or when re-platforming an existing Vercel application. Trigger with phrases like "migrate to vercel", "vercel migration", "switch to vercel", "netlify to vercel", "aws to vercel", "vercel replatform".
veeva-upgrade-migration
Veeva Vault upgrade migration for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva upgrade migration".
veeva-migration-deep-dive
Veeva Vault migration deep dive for enterprise operations. Use when implementing advanced Veeva Vault patterns. Trigger: "veeva migration deep dive".
vastai-upgrade-migration
Upgrade Vast.ai CLI, migrate API versions, and handle breaking changes. Use when upgrading vastai CLI, detecting deprecations, or migrating between API versions. Trigger with phrases like "upgrade vastai", "vastai migration", "vastai breaking changes", "update vastai CLI".
vastai-migration-deep-dive
Migrate GPU workloads to or from Vast.ai, or between GPU providers. Use when switching from AWS/GCP/Azure GPU instances to Vast.ai, migrating between GPU types, or re-platforming ML infrastructure. Trigger with phrases like "migrate to vastai", "vastai migration", "switch to vastai", "vastai from aws", "vastai from lambda".