fathom-reference-architecture
Reference architecture for Fathom meeting intelligence integrations. Trigger with phrases like "fathom architecture", "fathom design", "fathom integration pattern". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill fathom-reference-architecture --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Fathom Reference Architecture ## Architecture ``` ┌──────────────┐ ┌─────────────────┐ ┌──────────────────┐ │ Fathom AI │────▶│ Webhook │────▶│ Meeting DB │ │ (Recordings)│ │ Handler │ │ (PostgreSQL) │ └──────────────┘ └─────────────────┘ └────────┬─────────┘ │ ┌─────────────────┐ ┌────────▼─────────┐ │ Action Item │ │ CRM Sync │ │ Extractor │────▶│ (Salesforce/ │ └─────────────────┘ │ HubSpot)
What does the fathom-reference-architecture skill do?
Reference architecture for Fathom meeting intelligence integrations. Trigger with phrases like "fathom architecture", "fathom design", "fathom integration pattern". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill fathom-reference-architecture --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.