Meetings
alirezarezvani/claude-skills
A skill your agent uses when someone wants to decide whether a meeting is worth calling, price a meeting in dollars, build a timeboxed agenda with desired outcomes, or turn messy meeting notes into…
Sync your Fathom meetings once, then search, analyze, and act on them forever — offline, at scale, without burning API quota.
$ npx skills add mvanhorn/printing-press-library --skill pp-fathom -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mvanhorn/printing-press-library pp-fathom --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cli-skills/pp-fathom .claude/skills/pp-fathom && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "pp-fathom" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-fathom into .claude/skills/pp-fathom/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-fathom", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-fathomType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mvanhorn/printing-press-library --skill pp-fathom -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mvanhorn/printing-press-library pp-fathom --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .agents/skills && cp -r skills-src/cli-skills/pp-fathom .agents/skills/pp-fathom && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pp-fathom" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-fathom into .agents/skills/pp-fathom/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-fathom", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mvanhorn/printing-press-library --skill pp-fathom -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mvanhorn/printing-press-library pp-fathom --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/cli-skills/pp-fathom .cursor/skills/pp-fathom && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "pp-fathom" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-fathom into .cursor/skills/pp-fathom/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-fathom", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mvanhorn/printing-press-library.git --path cli-skills/pp-fathom--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mvanhorn/printing-press-library --skill pp-fathom -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mvanhorn/printing-press-library pp-fathom --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/cli-skills/pp-fathom .gemini/skills/pp-fathom && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "pp-fathom" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-fathom into .gemini/skills/pp-fathom/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-fathom", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mvanhorn/printing-press-library pp-fathomInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mvanhorn/printing-press-library --skill pp-fathom -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .github/skills && cp -r skills-src/cli-skills/pp-fathom .github/skills/pp-fathom && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "pp-fathom" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-fathom into .github/skills/pp-fathom/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-fathom", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mvanhorn/printing-press-library --skill pp-fathom -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mvanhorn/printing-press-library pp-fathom --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/cli-skills/pp-fathom .opencode/skills/pp-fathom && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "pp-fathom" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-fathom into .opencode/skills/pp-fathom/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-fathom", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
pp-fathomSync your Fathom meetings once, then search, analyze, and act on them forever — offline, at scale, without burning API quota.
Pp Fathom is an agent skill from mvanhorn/printing-press-library. Sync your Fathom meetings once, then search, analyze, and act on them forever — offline, at scale, without burning API quota. Trigger phrases: what did I promise in my calls, how often has pricing come up in meetings, brief me on my Acme calls, which team members are in too many meetings, find a meeting where we discussed X, search my fathom meetings, use fathom, run fathom-pp-cli.
Its SKILL.md is about 3.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Official library of CLIs generated by the CLI Printing Press. Endorsed, tested, and community-contributed. The licence is Apache-2.0.
3 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit d9a1696. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadBashFrom allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
goclaudenpxFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
FATHOM_PP_CLI_API_KEYFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Pp Fathom loads about 3.6k tokens when it runs. Until then it costs about 103 tokens; SKILL.md has 1,459 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
allowed-tools: Read, BashAutomated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from mvanhorn/printing-press-library at commit d9a1696, republished under its Apache-2.0 licence (© mvanhorn). 1,459 words, ~3,583 tokens.
.claude/skills/pp-fathom/SKILL.md (or your agent's skills folder).<!-- GENERATED FILE — DO NOT EDIT.
This file is a verbatim mirror of library/productivity/fathom/SKILL.md,
regenerated post-merge by tools/generate-skills/. Hand-edits here are
silently overwritten on the next regen. Edit the library/ source instead.
See the repository agent guide, section "Generated artifacts: registry.json, cli-skills/". -->
This skill drives the fathom-pp-cli binary. You must verify the CLI is installed before invoking any command from this skill. If it is missing, install it first:
$HOME/.local/bin on macOS/Linux and %LOCALAPPDATA%\Programs\PrintingPress\bin on Windows:npx -y @mvanhorn/printing-press-library install fathom --cli-onlyfathom-pp-cli --version$PATH for the agent/runtime that will invoke this skill.If the npx install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.6 or newer):
go install github.com/mvanhorn/printing-press-library/library/productivity/fathom/cmd/fathom-pp-cli@latestIf --version reports "command not found" after install, the runtime cannot see the binary directory on $PATH. Do not proceed with skill commands until verification succeeds.
Use fathom-pp-cli when you need cross-meeting intelligence that the Fathom web UI and MCP servers cannot provide: commiment audits across all calls, topic trend analysis over weeks or months, pre-call account briefs, or pipeline cadence monitoring. Run sync once per day to keep the local store current, then all analysis commands run offline. Not a substitute for the Fathom web UI for reviewing individual recordings or managing your account.
These capabilities aren't available in any other tool for this API.
commitments — See every open action item you promised across all calls — grouped by meeting, assignee, and date — without opening a single recording.
Use when you need a weekly accountability audit of all meeting commitments before a 1:1 or team sync.
fathom-pp-cli commitments --assignee me --since 30d --agenttopics — Find out how often 'pricing,' 'onboarding,' or any keyword has surfaced in your meetings over the past N weeks — with week-over-week trend.
Use before a board meeting or quarterly review to synthesize what themes have been dominating customer calls.
fathom-pp-cli topics --terms pricing,onboarding --weeks 12 --agentvelocity — Track whether your meeting cadence with a key account is accelerating, stable, or stalling — month by month.
Use for pipeline health reviews: a stalling cadence with a key account is an early warning signal before the deal goes cold.
fathom-pp-cli velocity --domain stripe.com --months 6 --agentworkload — See which team members are spending the most hours in meetings per week and whether the load is worsening.
Use in 1:1 prep or team planning to identify who is in 'meeting hell' before assigning more collaborative work.
fathom-pp-cli workload --team Engineering --weeks 4 --threshold 15 --agentbrief — Get a chronological history of every meeting with a specific person or company — past topics, open action items, last contact date — before you join a call.
Use immediately before a customer call to surface prior commitments and context without opening multiple browser tabs.
fathom-pp-cli brief --domain acme.com --agentaccount — View a complete, domain-keyed history with any company: every meeting, topics discussed, action items, and cadence — in one structured output.
Use during account reviews, renewal prep, or CRM updates to get a full picture of all interactions with a company.
fathom-pp-cli account --domain notion.so --agentstale — Find recordings that were captured but have no transcript, summary, or action items synced — useful for operators debugging pipeline gaps.
Use on Monday morning to audit which recordings from last week are missing data before your team needs them.
fathom-pp-cli stale --since 7d --agentcrm-gaps — Surface CRM-matched meetings where no action items were logged — calls that touched active deals but left no paper trail.
Use in RevOps audits to find sales calls where reps talked to prospects but forgot to log next steps in the CRM.
fathom-pp-cli crm-gaps --since 30d --agentcoverage — Track how reliably a recurring meeting (weekly planning, standup, 1:1) is being recorded over time.
Use to verify that mandatory-record meetings are actually being captured before auditing team performance.
fathom-pp-cli coverage --pattern 'Weekly Planning' --weeks 10 --agentmeetings — Meeting recordings with transcripts, summaries, and action items
fathom-pp-cli meetings — List meetings with optional filters and included datarecordings — Individual recording data: transcripts and summaries
fathom-pp-cli recordings get-summary — Get AI-generated meeting summary in markdown formatfathom-pp-cli recordings get-transcript — Get full transcript for a recording with speaker attribution and timestampsteam-members — Members of your teams
fathom-pp-cli team-members — List team members, optionally filtered by team nameteams — Teams your account has access to
fathom-pp-cli teams — List all teams accessible to your accountwebhooks — Webhooks for async meeting completion notifications
fathom-pp-cli webhooks create — Create a webhook to receive meeting data on completionfathom-pp-cli webhooks delete — Delete a webhook by IDWhen you know what you want to do but not which command does it, ask the CLI directly:
fathom-pp-cli which "<capability in your own words>"which resolves a natural-language capability query to the best matching command from this CLI's curated feature index. Exit code 0 means at least one match; exit code 2 means no confident match — fall back to --help or use a narrower query.
# Export all synced meetings to JSONL (one record per line)
fathom-pp-cli db export --format jsonl --output ~/fathom-backup.jsonl
# Export as SQLite file
fathom-pp-cli db export --format sqlite --output ~/fathom-backup.db
# Restore on another machine (no API calls, no re-sync needed)
fathom-pp-cli db restore --format jsonl --input ~/fathom-backup.jsonl
fathom-pp-cli db restore --format sqlite --input ~/fathom-backup.dbPure local operation — reads from SQLite, writes to file. Run sync --full once, then export and share. On the new machine: install fathom-pp-cli, set FATHOM_PP_CLI_API_KEY, restore from the file, and all commands work offline immediately.
fathom-pp-cli search "data pipeline clearpack" --limit 5
fathom-pp-cli search "joey action items" --json --select title,date,url,snippetFull-text search across all synced transcripts, summaries, action items, and titles. Returns ranked results with highlighted snippet showing where the term matched. Searches offline — no API quota. Run sync --full first.
fathom-pp-cli brief --domain acme.com --agent --select meetings.title,meetings.date,open_action_itemsPull all history with Acme before joining a call — past topics, open commitments, last meeting date.
fathom-pp-cli commitments --since 7d --agent --select meeting_title,description,assignee.name,completedSurface every action item from last week's calls, grouped by meeting — know what's still open before Monday standup.
fathom-pp-cli topics --terms 'pricing,churn,roadmap' --weeks 12 --agentShow week-over-week frequency of key themes across all customer calls for the past quarter.
fathom-pp-cli velocity --domain acme.com --months 6 --agentSee whether your meeting cadence with Acme has been increasing, flat, or stalling — early warning for deals going cold.
fathom-pp-cli workload --team Engineering --weeks 4 --threshold 15 --agent --select name,weekly_hours,trendFind which engineers are spending over 15h/week in meetings and whether it's getting worse.
Fathom uses an API key passed via the X-Api-Key header. Generate one at fathom.video → User Settings → API Access. Set FATHOM_PP_CLI_API_KEY in your environment, then run doctor to verify.
Run fathom-pp-cli doctor to verify setup.
Add --agent to any command. Expands to: --json --compact --no-input --no-color --yes.
Pipeable — JSON on stdout, errors on stderr
Filterable — --select keeps a subset of fields. Dotted paths descend into nested structures; arrays traverse element-wise. Critical for keeping context small on verbose APIs:
fathom-pp-cli meetings --agent --select id,name,statusPreviewable — --dry-run shows the request without sending
Offline-friendly — sync/search commands can use the local SQLite store when available
Non-interactive — never prompts, every input is a flag
Explicit retries — use --idempotent only when an already-existing create should count as success, and --ignore-missing only when a missing delete target should count as success
Commands that read from the local store or the API wrap output in a provenance envelope:
{
"meta": {"source": "live" | "local", "synced_at": "...", "reason": "..."},
"results": <data>
}Parse .results for data and .meta.source to know whether it's live or local. A human-readable N results (live) summary is printed to stderr only when stdout is a terminal — piped/agent consumers get pure JSON on stdout.
When you (or the agent) notice something off about this CLI, record it:
fathom-pp-cli feedback "the --since flag is inclusive but docs say exclusive"
fathom-pp-cli feedback --stdin < notes.txt
fathom-pp-cli feedback list --json --limit 10Entries are stored locally at ~/.fathom-pp-cli/feedback.jsonl. They are never POSTed unless FATHOM_FEEDBACK_ENDPOINT is set AND either --send is passed or FATHOM_FEEDBACK_AUTO_SEND=true. Default behavior is local-only.
Write what surprised you, not a bug report. Short, specific, one line: that is the part that compounds.
Every command accepts --deliver <sink>. The output goes to the named sink in addition to (or instead of) stdout, so agents can route command results without hand-piping. Three sinks are supported:
| Sink | Effect |
|---|---|
stdout | Default; write to stdout only |
file:<path> | Atomically write output to <path> (tmp + rename) |
webhook:<url> | POST the output body to the URL (application/json or application/x-ndjson when --compact) |
Unknown schemes are refused with a structured error naming the supported set. Webhook failures return non-zero and log the URL + HTTP status on stderr.
A profile is a saved set of flag values, reused across invocations. Use it when a scheduled agent calls the same command every run with the same configuration - HeyGen's "Beacon" pattern.
fathom-pp-cli profile save briefing --json
fathom-pp-cli --profile briefing meetings
fathom-pp-cli profile list --json
fathom-pp-cli profile show briefing
fathom-pp-cli profile delete briefing --yesExplicit flags always win over profile values; profile values win over defaults. agent-context lists all available profiles under available_profiles so introspecting agents discover them at runtime.
| Code | Meaning |
|---|---|
| 0 | Success |
| 2 | Usage error (wrong arguments) |
| 3 | Resource not found |
| 4 | Authentication required |
| 5 | API error (upstream issue) |
| 7 | Rate limited (wait and retry) |
| 10 | Config error |
Parse $ARGUMENTS:
help, or --help → show fathom-pp-cli --help outputinstall → ends with mcp → MCP installation; otherwise → see Prerequisites above--agent)go install github.com/mvanhorn/printing-press-library/library/productivity/fathom/cmd/fathom-pp-mcp@latestclaude mcp add fathom-pp-mcp -- fathom-pp-mcpclaude mcp listwhich fathom-pp-cli
If not found, offer to install (see Prerequisites at the top of this skill).--agent flag:fathom-pp-cli <command> [subcommand] [args] --agentfathom-pp-cli <command> --help.© mvanhorn, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in cli-skills/pp-fathom of mvanhorn/printing-press-library.
Open the folder on GitHubat commit d9a1696
Pp Fathom next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Pp Fathom this skillmvanhorn/printing-press-library | 2.1k | — | ~3.6k | Automated safety check: Notes | Apache-2.0 | |
| Meetingsalirezarezvani/claude-skills | 28k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Meeting Minutesgithub/awesome-copilot | 40k | 2 repos | ~2k | Automated safety check: Pass | MIT | |
| Meeting Action ItemsNousResearch/hermes-agent | 252k | — | ~950 | Automated safety check: Pass | MIT | |
| Meeting Notesoutline/outline | 41k | — | ~551 | Automated safety check: Pass | Custom licence | |
| Int Sync Meetingsevolution-foundation/evo-nexus | 545 | — | ~1.9k | Automated safety check: Pass | Custom licence |
alirezarezvani/claude-skills
A skill your agent uses when someone wants to decide whether a meeting is worth calling, price a meeting in dollars, build a timeboxed agenda with desired outcomes, or turn messy meeting notes into…
github/awesome-copilot
Generate concise, actionable meeting minutes for internal meetings.
NousResearch/hermes-agent
Turn meeting notes into cited decisions, owners, tickets. An agent skill from NousResearch/hermes-agent.
outline/outline
Create meeting notes in Outline from a template; use when the user wants an agenda, notes, or a follow-up document for a meeting.
evolution-foundation/evo-nexus
Sync meetings from Fathom — fetch new recordings, save JSON, generate transcripts and summaries, update indexes.
phuryn/pm-skills
Summarize a meeting transcript into structured notes with date, participants, topic, key decisions, summary points, and action items.
mvanhorn/printing-press-library
Desktop automation through the real Rust agent-desktop CLI, published in Printing Press through a small bridge.
mvanhorn/printing-press-library
Search, browse, and download Google Fonts from the terminal via the gfonts CLI.
mvanhorn/printing-press-library
The free, offline Trigger phrases: search 1688 for, find a factory on 1688 for, wholesale price on 1688 for, who is the cheapest supplier on 1688 for, compare 1688 suppliers for, use 1688, run 1688.
mvanhorn/printing-press-library
Inspect known Activity Japan plan IDs or URLs, compare dated prices and sessions, check language-sitemap coverage, and hand off to canonical booking pages.
mvanhorn/printing-press-library
Every Admin By Request portal action, plus a local SQLite mirror of audit, events, inventory and requests for ad-hoc...
mvanhorn/printing-press-library
macOS screen capture, window recording, GIF conversion, and agent evidence bundles from the terminal.
Sync your Fathom meetings once, then search, analyze, and act on them forever — offline, at scale, without burning API quota. Pp Fathom is an agent skill from mvanhorn/printing-press-library. Sync your Fathom meetings once, then search, analyze, and act on them forever — offline, at scale, without burning API quota.
Pp Fathom fits situations like: phrases: what did I promise in my calls; how often has pricing come up in meetings; brief me on my Acme calls; which team members are in too many meetings.
Run `npx skills add mvanhorn/printing-press-library --skill pp-fathom -a claude-code`. Or copy the skill folder (cli-skills/pp-fathom in mvanhorn/printing-press-library) into .claude/skills/pp-fathom in your project. Claude Code loads it when a task matches its description.
Run `npx skills add mvanhorn/printing-press-library --skill pp-fathom -a codex`. Or copy the skill folder (cli-skills/pp-fathom in mvanhorn/printing-press-library) into .agents/skills/pp-fathom in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mvanhorn/printing-press-library --skill pp-fathom -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pp-fathom, .gemini/skills/pp-fathom, .github/skills/pp-fathom and .opencode/skills/pp-fathom in your project.
Going by SKILL.md and its folder, Pp Fathom needs the command-line tools its instructions call (go, claude and npx) and credentials named FATHOM_PP_CLI_API_KEY. Our summary lists: Node.js; A credential in FATHOM_PP_CLI_API_KEY. Its frontmatter pre-approves these tools: Read, Bash.
SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Pp Fathom is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.6k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Pp Fathom: Meetings (alirezarezvani/claude-skills, 28k stars), Meeting Minutes (github/awesome-copilot, 40k stars), Meeting Action Items (NousResearch/hermes-agent, 252k stars) and Meeting Notes (outline/outline, 41k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
mvanhorn (a GitHub user) maintains it in mvanhorn/printing-press-library, which has 2,056 GitHub stars. The repository holds 506 skills in this directory. The repository was last updated on October 9, 2026.
Source: mvanhorn/printing-press-library on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.