fathom-upgrade-migration
Handle Fathom API changes and version migrations. Trigger with phrases like "upgrade fathom", "fathom api changes", "fathom migration".
Best use case
fathom-upgrade-migration is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Handle Fathom API changes and version migrations. Trigger with phrases like "upgrade fathom", "fathom api changes", "fathom migration".
Teams using fathom-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/fathom-upgrade-migration/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How fathom-upgrade-migration Compares
| Feature / Agent | fathom-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?
Handle Fathom API changes and version migrations. Trigger with phrases like "upgrade fathom", "fathom api changes", "fathom 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
# Fathom Upgrade & 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
```typescript
const FATHOM_BASE = "https://api.fathom.video/external/v1";
interface FathomVersionCheck {
apiVersion: string;
knownFields: string[];
detectedFields: string[];
newFields: string[];
removedFields: string[];
}
async function detectFathomApiChanges(apiKey: string): Promise<FathomVersionCheck> {
const res = await fetch(`${FATHOM_BASE}/meetings?limit=1`, {
headers: { Authorization: `Bearer ${apiKey}` },
});
const data = await res.json();
const knownFields = ["id", "title", "created_at", "duration", "attendees", "transcript_url"];
const detectedFields = data.meetings?.[0] ? Object.keys(data.meetings[0]) : [];
return {
apiVersion: res.headers.get("x-api-version") ?? "v1",
knownFields,
detectedFields,
newFields: detectedFields.filter((f) => !knownFields.includes(f)),
removedFields: knownFields.filter((f) => !detectedFields.includes(f)),
};
}
```
## 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. `offset`) are current
- [ ] Update CRM sync mappings if meeting metadata fields renamed
- [ ] Run integration tests against Fathom sandbox environment
## Schema Migration
```typescript
// Fathom transcript response evolved: flat text → speaker-attributed segments
interface OldTranscript {
meeting_id: string;
text: string;
created_at: string;
}
interface NewTranscript {
meeting_id: string;
segments: Array<{
speaker: string;
text: string;
start_time: number;
end_time: number;
confidence: number;
}>;
summary: string;
action_items: Array<{ text: string; assignee?: string }>;
created_at: string;
}
function migrateTranscript(old: OldTranscript): NewTranscript {
return {
meeting_id: old.meeting_id,
segments: [{ speaker: "Unknown", text: old.text, start_time: 0, end_time: 0, confidence: 1.0 }],
summary: "",
action_items: [],
created_at: old.created_at,
};
}
```
## Rollback Strategy
```typescript
class FathomClient {
private baseUrl: string;
private fallbackUrl: string;
constructor(private apiKey: string) {
this.baseUrl = "https://api.fathom.video/external/v1";
this.fallbackUrl = "https://api.fathom.video/external/v1"; // same base, version in path
}
async getMeetings(limit = 20): Promise<any> {
try {
const res = await fetch(`${this.baseUrl}/meetings?limit=${limit}`, {
headers: { Authorization: `Bearer ${this.apiKey}` },
});
if (!res.ok) throw new Error(`Fathom API ${res.status}`);
return await res.json();
} catch (err) {
console.warn("Primary endpoint failed, attempting fallback:", err);
const res = await fetch(`${this.fallbackUrl}/meetings?limit=${limit}`, {
headers: { Authorization: `Bearer ${this.apiKey}`, Accept: "application/json; version=legacy" },
});
return await res.json();
}
}
}
```
## Error Handling
| Migration Issue | Symptom | Fix |
|----------------|---------|-----|
| Transcript schema changed | Missing `segments` array, only flat `text` returned | Update parser to handle both old flat and new segmented formats |
| Webhook payload mismatch | `meeting.completed` event missing expected fields | Re-register webhook with updated event schema version |
| OAuth scope expansion | `403 Forbidden` on transcript endpoint | Re-authorize with updated scopes (`meetings.read`, `transcripts.read`) |
| Pagination cursor invalid | `400 Bad Request` with cursor token | Switch from offset-based to cursor-based pagination if API changed |
| Rate limit headers changed | `429` without `Retry-After` header | Implement exponential backoff instead of relying on header |
## Resources
- [Fathom Product Updates](https://help.fathom.video/en/articles/6220097)
- [Fathom API Documentation](https://fathom.video/api)
## Next Steps
For CI pipeline integration, see `fathom-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".