fathom-upgrade-migration
Handle Fathom API changes and version migrations. Trigger with phrases like "upgrade fathom", "fathom api changes", "fathom migration".
What this skill does
# 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
## Next Steps
For CI pipeline integration, see `fathom-ci-integration`.
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.