Individual skill
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".
skills/.curated/mindtickle-upgrade-migration/SKILL.md
Source commit 0500b275e963c027f6b410e8c49c0446945c574e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 12, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 2,916
- Repository last updated
- Nov 12, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai Repository topic
- automation Repository topic
- claude-code Repository topic
- devops Repository topic
- mcp Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- claude-code-plugins Repository topic
- developer-tools Repository topic
- llm Repository topic
- saas Declared skill tag
- mindtickle Declared skill tag
- migration Declared skill tag
- compatibility Declared skill tag
- rollback Declared skill tag
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 4,319 bytes
Read excerpt
# 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.