skills/integrations/fathom/fathom-get-transcript/SKILL.md
Fetch full transcript from Fathom using a meeting/recording ID. Load when user says "get transcript", "fetch transcript for [ID]", "fathom transcript", "download meeting transcript", or has a meeting ID and wants the full conversation text.
npx skillsauth add beam-ai-team/beam-next-skills fathom-get-transcriptInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Fetch the complete transcript for a specific Fathom meeting using its recording ID.
Retrieves the full speaker-attributed transcript from a Fathom recording. Use this when you have a meeting ID (from fathom-fetch-meetings or direct input) and need the complete conversation text for processing.
Requirements: Fathom API key in .env
# Add to .env
FATHOM_API_KEY=your-api-key-here
Get your API key: Fathom Settings → API
fathom-get-transcript/
├── SKILL.md # This file
└── scripts/
└── get_transcript.py # Fetch transcript by recording ID
Accept recording ID from:
fathom-fetch-meetings (recording_id field)Enter recording ID (or paste Fathom URL):
> abc123-def456-789
python scripts/get_transcript.py --recording-id {ID}
API Call:
curl -s --request GET \
--url 'https://api.fathom.ai/external/v1/recordings/{RECORDING_ID}/transcript' \
--header 'X-Api-Key: {FATHOM_API_KEY}'
Raw Response:
{
"transcript": [
{
"speaker": {
"display_name": "John Smith",
"matched_calendar_invitee_email": "[email protected]"
},
"text": "Let's start with the agenda...",
"timestamp": "00:01:23"
}
]
}
Formatted Output:
TRANSCRIPT: Meeting Title
Duration: 45 minutes
Speakers: John Smith, Jane Doe
---
[00:01:23] John Smith:
Let's start with the agenda...
[00:01:45] Jane Doe:
Thanks John. First item is the technical review...
Returns structured transcript data for downstream skills:
# Fetch transcript by ID
python scripts/get_transcript.py --recording-id abc123-def456
# Fetch and save to file
python scripts/get_transcript.py --recording-id abc123 --output transcript.md
# Get JSON output for processing
python scripts/get_transcript.py --recording-id abc123 --json
{
"recording_id": "abc123-def456",
"duration_seconds": 2700,
"speakers": ["John Smith", "Jane Doe"],
"transcript": [
{
"timestamp": "00:01:23",
"speaker": "John Smith",
"email": "[email protected]",
"text": "Let's start with the agenda..."
}
],
"full_text": "John Smith: Let's start...\n\nJane Doe: Thanks John..."
}
| Error | Cause | Solution | |-------|-------|----------| | 401 Unauthorized | Invalid API key | Check FATHOM_API_KEY in .env | | 404 Not Found | Invalid recording ID | Verify ID from fathom-fetch-meetings | | 403 Forbidden | No access to recording | Ensure you have access in Fathom |
fathom-fetch-meetings - Get recording IDs by filtering meetingscreate-meeting-minutes - Process transcript into formatted minutesprocess-client-meeting - Full meeting workflowVersion: 1.0 Integration: Fathom API Owner: Hassaan Ahmed
development
--- name: taste-skill type: skill version: '1.0' author: Leonxlnx (packaged by Zhichao Li) category: general tags: - frontend - design - anti-slop - landing-page updated: '2026-06-11' visibility: public description: Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check. license: MIT.
development
Use when communicating quantitative information in any form — Slack updates, emails, reports, decks, dashboards, landing pages, product UI, public talks. Covers two integrated layers: (1) making numbers semantically meaningful (translation, anchoring, simplification, story-pairing) and (2) showing numbers cleanly (chart vs table vs prose, chart-by-message, pre-attentive emphasis, color discipline, decluttering). Distilled and integrated from *Show Me the Numbers* (Stephen Few) and *Make Numbers Count* (Chip Heath & Karla Starr). Not for raw data analysis or statistics — this is about communication of numbers, not their derivation.
development
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
tools
Stateful multi-session tutor adapted for Beam — teach a stakeholder to understand, trust, and operate a specific agent, or teach a Solution Engineer a client's business process for delivery. Grounds every lesson in Knowledge Hub sources (real agent graphs, real tasks, transcripts, Linear) before any web resource. Also works for any general topic. Trigger on "teach me", "beam teach", "教我", "onboard <person> on <agent>", "help <stakeholder> understand the agent", "learn this client's process".