--- name: salesloft-upgrade-migration-b7b098a8b49a description: >- Migrate an existing Salesloft integration through an evidence-backed endpoint, auth, schema, scope, and behavior diff with shadow validation and rollback. Use when current contracts or application assumptions change. Trigger with "Salesloft migration", "upgrade Salesloft integration", or "Salesloft API contract change". argument-hint: "[repository-path] [migration-scope]" allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit version: 1.6.0 author: Jeremy Longshore license: MIT tags: - saas - salesloft - migration model: inherit effort: medium compatibility: Designed for Claude Code --- # Salesloft Contract Migration ## Overview This skill migrates the integration that actually exists. It does not assume a generic v1-to-v2 journey, API-key deprecation, or universal endpoint rename. ## Prerequisites - Current integration commit, dependencies, deployment topology, and owners - Complete method/path/scope/request/response inventory - Target official documentation and migration reason - Sanitized fixtures, shadow environment, rollback, and reconciliation plan ## Tool Discipline Use `Read`, `Glob`, and `Grep` to inventory callers, auth, schemas, and compatibility code. Use `WebFetch` only for current official Salesloft documentation. Use `Write` or `Edit` after the migration boundary is approved. ## Current Contract - The current public reference exposes v2 and historical v1 surfaces; compatibility is endpoint-specific. - Resource paths are documented without a universal `.json` requirement. - Auth flow choice depends on integration type; API keys remain a customer path and client credentials remain private-use only. - Rate costs and endpoint schemas can change independently of URL versioning. - Cadence import, export, and membership contracts must be verified from their own endpoint pages. ## Authentication Treat auth migration as a separate reversible workstream. Preserve tenant binding and least privilege, and do not disable the old credential until the new path is proven and rollback is viable. ## Instructions 1. Inventory every live method, path, query, content type, scope, response field, and retry assumption. 2. Diff each used contract against current official documentation and classify required changes. 3. Add failing fixtures for every intentional schema or behavior delta. 4. Implement an adapter or dual-read path instead of changing all callers at once. 5. Shadow reads and compare normalized results without duplicating writes. 6. Canary approved mutations with read-after-write and reconciliation evidence. 7. Cut over gradually, monitor rate and error signals, then remove compatibility code only after rollback expiry. ## Approval Boundaries Do not automatically fall back between API versions, convert auth flows, import cadences, or replay writes. Each live mutation and irreversible cleanup needs explicit approval. ## Output Return contract diff, affected callers, fixture results, shadow comparison, canary evidence, cutover state, rollback trigger, and cleanup date. ## Error Handling | Condition | Response | |---|---| | Undocumented behavior | Stop and obtain provider or support confirmation. | | Shadow mismatch | Keep old reads authoritative and isolate the field delta. | | Canary uncertainty | Reconcile before retry or wider rollout. | | Rate regression | Halt expansion and compare endpoint/page cost. | ## Examples The example below shows the minimum redacted evidence expected from a successful invocation of this operator workflow. ```text contracts=14; changed=3; shadow-match=100%; canary=pending; rollback=ready ``` ## Resources - [Skill-specific official documentation](references/official-docs.md) - [Salesloft API reference](https://developers.salesloft.com/docs/api/salesloft-platform/) - [Request and response format](https://developers.salesloft.com/docs/platform/api-basics/request-response-format/) --- Source attribution: jeremylongshore Original project: https://github.com/jeremylongshore/claude-code-plugins-plus-skills/blob/ab85a061f7bcc039dac13ee193de7a4cd4388571/plugins/saas-packs/salesloft-pack/skills/salesloft-upgrade-migration/SKILL.md License: MIT License information: https://opensource.org/license/mit Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice MIT License Copyright (c) 2025 Jeremy Longshore Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. # Mega AI Hub resource metadata Creator / publisher: jeremylongshore Original project: https://github.com/jeremylongshore/claude-code-plugins-plus-skills/blob/ab85a061f7bcc039dac13ee193de7a4cd4388571/plugins/saas-packs/salesloft-pack/skills/salesloft-upgrade-migration/SKILL.md Attribution basis: Source repository record Fields of work: Marketing, Sales Roles: Account Executive, Business Development, Growth Marketer, Sales Operations, Sales Development Rep (SDR) Specialties: API, Backend, Design, Frontend, Git, Mobile, Testing Tools: Salesloft Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: bdd999c05ea53e6e8d1a1f77048ee7d83d094039390b8f5b052066f12c4413af