Individual skill

fathom-reference-architecture

Reference architecture for Fathom meeting intelligence integrations. Trigger with phrases like "fathom architecture", "fathom design", "fathom integration pattern".

plugins/saas-packs/fathom-pack/skills/fathom-reference-architecture/SKILL.md

Read pinned source

Source commit 0500b275e963c027f6b410e8c49c0446945c574e

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 12, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
2,916
Repository last updated
Nov 12, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt
# Fathom Reference Architecture

## Overview

Define meeting ingestion, consent, Fathom processing, CRM/follow-up integration, redacted observability, retention, and incident boundaries as an owned system.

## Prerequisites

- A documented data/consent model, environment boundaries, integration owners, and approved data-retention policy.

## Instructions

1. Map meeting sources, identities, processing, integrations, access, and audit paths to owners.
2. Separate development/staging/production credentials and use role-limited access at every boundary.
3. Build idempotent integrations and fallback/rollback decisions before production automation.
Back to top