Fathom

Connect to Fathom AI to fetch call recordings, transcripts, and summaries. Use when user asks about their meetings, call history, or wants to search past conversations.

Security Scan

The skill appears to do what it claims (talk to Fathom's API) but it fails to declare that it requires a FATHOM_API_KEY and references a user home config file (~/.fathom_api_key), which is an inconsistency you should understand before installing.

Purpose & Capability

Name/description match the code: scripts call https://api.fathom.ai to list meetings, fetch transcripts/summaries, and register webhooks. However, the registry metadata lists no required environment variables or primary credential, while the scripts and SKILL.md clearly require an API key (FATHOM_API_KEY) and optionally read ~/.fathom_api_key. The missing declaration of the API key/config path is an incoherence.

Instruction Scope

Runtime instructions and scripts stay within the described scope: they use curl/jq to call the Fathom API endpoints and provide webhook registration. They do instruct the user to store an API key in ~/.fathom_api_key (or set FATHOM_API_KEY) and to provide a public HTTPS webhook endpoint; both are reasonable for the feature set but expand required operational setup. The scripts do not access or exfiltrate other local files or send data to non-Fathom endpoints (except the provided webhook URL which is user-controlled).

Install Mechanism

There is no install spec; the skill is a collection of shell scripts and documentation. No remote downloads or package installs are performed by the skill itself, minimizing install-time risk.

Credentials

The skill requires a single API credential (FATHOM_API_KEY) to function, which is proportionate. But that credential and the config path (~/.fathom_api_key) are not declared in the registry metadata (required env vars and primary credential are empty). This mismatch is a red flag: the skill will silently fail without the key and the metadata doesn't warn users or the platform that a secret is needed. The scripts also print webhook secrets to stdout after registration, which could be exposed if the user runs them in an untrusted environment.

Persistence & Privilege

The skill does not request permanent inclusion (always: false) and does not modify other skills or system-wide configuration. It suggests storing an API key in a home file, but it does not itself write persistent files or change agent settings.

What to consider before installing

This skill's scripts appear to legitimately call Fathom's official API and implement the described features, but the registry metadata omitted the fact that the skill requires an API key and optionally reads ~/.fathom_api_key. Before installing: (1) Verify the skill source/trustworthiness (source/homepage unknown). (2) Expect to provide a FATHOM_API_KEY; prefer setting it as an environment variable rather than writing it to a file, and if you do store it in ~/.fathom_api_key keep file perms locked (chmod 600). (3) Be careful when running setup-webhook.sh: it will register a webhook that will deliver transcripts to whatever endpoint you provide — only use a trusted HTTPS endpoint and verify webhook signatures on your endpoint. (4) Note that the script prints the webhook secret to stdout; treat that output as sensitive. (5) If you need stronger assurance, run the scripts in an isolated/sandboxed environment first and inspect network traffic to confirm calls go only to api.fathom.ai. (6) Ask the publisher/registry to update metadata to declare FATHOM_API_KEY and the ~/.fathom_api_key config path so the requirement is explicit.

Fathom Skill

Connect to Fathom AI to fetch call recordings, transcripts, and summaries.

Setup

1. Get Your API Key

1. Go to developers.fathom.ai
2. Create an API key
3. Copy the key (format: v1XDx...)

2. Configure

# Option A: Store in file (recommended)
echo "YOUR_API_KEY" > ~/.fathom_api_key
chmod 600 ~/.fathom_api_key

# Option B: Environment variable
export FATHOM_API_KEY="YOUR_API_KEY"

3. Test Connection

./scripts/setup.sh

---

Commands

List Recent Calls

./scripts/list-calls.sh                    # Last 10 calls
./scripts/list-calls.sh --limit 20         # Last 20 calls
./scripts/list-calls.sh --after 2026-01-01 # Calls after date
./scripts/list-calls.sh --json             # Raw JSON output

Get Transcript

./scripts/get-transcript.sh 123456789      # By recording ID
./scripts/get-transcript.sh 123456789 --json
./scripts/get-transcript.sh 123456789 --text-only

Get Summary

./scripts/get-summary.sh 123456789         # By recording ID
./scripts/get-summary.sh 123456789 --json

Search Calls

./scripts/search-calls.sh "product launch" # Search transcripts
./scripts/search-calls.sh --speaker "Lucas"
./scripts/search-calls.sh --after 2026-01-01 --before 2026-01-15

---

API Reference

Endpoint	Method	Description
/meetings	GET	List meetings with filters
/recordings/{id}/transcript	GET	Full transcript with speakers
/recordings/{id}/summary	GET	AI summary + action items
/webhooks	POST	Register webhook for auto-sync

Base URL: https://api.fathom.ai/external/v1
Auth: X-API-Key header

---

Filters for list-calls

Filter	Description	Example
--limit N	Number of results	--limit 20
--after DATE	Calls after date	--after 2026-01-01
--before DATE	Calls before date	--before 2026-01-15
--cursor TOKEN	Pagination cursor	--cursor eyJo...

---

Output Formats

Flag	Description
--json	Raw JSON from API
--table	Formatted table (default for lists)
--text-only	Plain text (transcripts only)

---

Examples

Get your last call's summary

# Get latest call ID
CALL_ID=$(./scripts/list-calls.sh --limit 1 --json | jq -r '.[0].recording_id')

# Get summary
./scripts/get-summary.sh $CALL_ID

Export all calls from last week

./scripts/list-calls.sh --after $(date -d '7 days ago' +%Y-%m-%d) --json > last_week_calls.json

Find calls mentioning a topic

./scripts/search-calls.sh "quarterly review"

---

Troubleshooting

Error	Solution
"No API key found"	Run setup or set FATHOM_API_KEY
"401 Unauthorized"	Check API key is valid
"429 Rate Limited"	Wait and retry
"Recording not found"	Verify recording ID exists

---

Webhook Setup (Advanced)

For automatic transcript ingestion, see the webhook setup guide:

./scripts/setup-webhook.sh --url https://your-endpoint.com/webhook

Requires a publicly accessible HTTPS endpoint.