Agent skill · software engineering · jeremylongshore
fathom-upgrade-migration
Handle Fathom API changes and version migrations.
Why this skill is useful
Adds executable scripts for detecting API changes and migrating data structures that are not publicly documented.
What it needs
Requires typescript installed locally. Requires fathom account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Fathom Upgrade & Migration Prerequisites Current/target version inventory, compatibility notes, synthetic fixtures, acceptance criteria, and rollback owner. Instructions 1. Inventory configuration, credentials, CRM mappings, access, retention, and consent behavior. 2. Test the target in development/staging with synthetic meetings and records. 3. Compare aggregate quality, delivery, error, access, and policy results before a bounded canary. 4. Pause or roll back on regression and retain the prior configuration until sign-off. Output A staged upgrade record with evidence, owner, observation window, and rollback revision. Examples Upgrade the integration in staging, run mock/unit and synthetic workflow checks against prior and target versions, and compare aggregate sync/follow-up behavior. Roll back on consent, access, mapping, or reliability regression; do not replay customer meetings to validate a migration. Overview Fathom is an AI meeting assistant that records, transcribes, and summarizes meetings. The API operates under /external/v1 and exposes endpoints for meetings, transcripts, and action items. Tracking API changes is important because Fathom iterates rapidly on transcript schema fields (speaker attribution, sentiment data, highlight clips) and breaking changes to response shapes can silently corrupt downstream integrations that consume meeting data for CRM sync or analytics pipelines. Version Detection Migration Checklist [ ] Review Fathom product updates for API changes and deprecations [ ] Audit all endpoints referencing /external/v1 in codebase [ ] Verify meeting list response schema matches current field expectations [ ] Check transcript endpoint for new speaker attribution fields [ ] Validate action item extraction format (structured vs. plain text) [ ] Update OAuth token refresh flow if auth endpoints changed [ ] Test webhook payloads for meeting completion events [ ] Verify pagination parameters (cursor vs. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/fathom-upgrade-migration