菜单
Secure Fathom API keys and handle meeting data privacy. Trigger with phrases like "fathom security", "fathom api key safety", "fathom privacy".
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/jeremylongshore/claude-code-plugins-plus-skills --skill fathom-security-basics命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Implement user sign-up and sign-in flows with Clerk. Use when building authentication UI, customizing sign-in experience, or implementing OAuth social login. Trigger with phrases like "clerk sign-in", "clerk sign-up", "clerk login flow", "clerk OAuth", "clerk social login".
Implement session management and middleware with Clerk. Use when managing user sessions, configuring route protection, or implementing token refresh and custom JWT templates. Trigger with phrases like "clerk session", "clerk middleware", "clerk route protection", "clerk token", "clerk JWT".
Configure enterprise SSO, role-based access control, and organization management. Use when implementing SSO integration, configuring role-based permissions, or setting up organization-level controls. Trigger with phrases like "clerk SSO", "clerk RBAC", "clerk enterprise", "clerk roles", "clerk permissions", "clerk organizations".
正在显示 SKILL.md
基于 SOC 职业分类
| name | fathom-security-basics |
| description | Secure Fathom API keys and handle meeting data privacy. Trigger with phrases like "fathom security", "fathom api key safety", "fathom privacy". |
| allowed-tools | Read, Write, Edit, Grep |
| version | 1.6.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| tags | ["saas","meeting-intelligence","ai-notes","fathom"] |
| compatibility | Designed for Claude Code |
Fathom records and transcribes meetings, producing transcripts and action items that contain participant PII (names, emails, spoken content), confidential business decisions, and potentially sensitive negotiations. API keys are per-user and grant access to all meetings the user recorded or that were shared to their team. Protect recording consent workflows, transcript storage, and any analytics pipeline touching meeting content.
function createFathomClient(): { apiKey: string; baseUrl: string } {
const apiKey = process.env.FATHOM_API_KEY;
if (!apiKey) {
throw new Error("Missing FATHOM_API_KEY — store in secrets manager, never in code");
}
// Fathom keys are per-user — never share across team members
console.log("Fathom client initialized (key hash:", apiKey.slice(-4), ")");
return { apiKey, baseUrl: "https://api.fathom.video/v1" };
}
import crypto from "crypto";
import { Request, Response, NextFunction } from "express";
function verifyFathomWebhook(req: Request, res: Response, next: NextFunction): void {
const signature = req.headers["x-fathom-signature"] as string;
const secret = process.env.FATHOM_WEBHOOK_SECRET!;
const expected = crypto.createHmac("sha256", secret).update(req.body).digest("hex");
if (!signature || !crypto.timingSafeEqual(Buffer.from(signature), Buffer.from(expected))) {
res.status(401).send("Invalid signature");
return;
}
next();
}
import { z } from "zod";
const MeetingQuerySchema = z.object({
meeting_id: z.string().uuid(),
include_transcript: z.boolean().default(false),
date_from: z.string().regex(/^\d{4}-\d{2}-\d{2}$/).optional(),
date_to: z.string().regex(/^\d{4}-\d{2}-\d{2}$/).optional(),
participant_email: z.string().email().optional(),
});
function validateMeetingQuery(data: unknown) {
return MeetingQuerySchema.parse(data);
}
const FATHOM_PII_FIELDS = ["participant_email", "participant_name", "phone_number", "transcript_text"];
function redactFathomLog(record: Record<string, unknown>): Record<string, unknown> {
const redacted = { ...record };
for (const field of FATHOM_PII_FIELDS) {
if (field in redacted) redacted[field] = "[REDACTED]";
}
// Also scrub emails from transcript snippets
if (typeof redacted.summary === "string") {
redacted.summary = (redacted.summary as string).replace(/[\w.+-]+@[\w-]+\.[\w.-]+/g, "[REDACTED_EMAIL]");
}
return redacted;
}
| Vulnerability | Risk | Mitigation |
|---|---|---|
| Leaked API key | Access to all user meetings and transcripts | Secrets manager + key regeneration |
| Unredacted transcripts in logs | Participant PII exposure | Field-level redaction pipeline |
| Missing recording consent | Legal liability under two-party consent laws | Consent verification before processing |
| Unencrypted transcript storage | Bulk meeting data breach | Encryption at rest + access controls |
| Overly broad meeting sharing | Confidential content exposed to wrong teams | Per-meeting permission scoping |
See fathom-prod-checklist.