fathom-local-dev-loop
Set up local development for Fathom API integrations with mock meeting data. Use when building meeting analytics tools, testing webhook handlers, or iterating on transcript processing pipelines. Trigger with phrases like "fathom dev setup", "fathom local testing", "develop with fathom", "fathom mock data". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill fathom-local-dev-loop --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 Local Dev Loop ## Project Structure ``` fathom-integration/ ├── src/ │ ├── fathom_client.py │ ├── transcript_processor.py │ └── webhook_handler.py ├── tests/ │ ├── fixtures/ │ │ ├── meeting.json │ │ └── transcript.json │ └── test_processor.py ├── .env.local └── requirements.txt ``` ## Mock Meeting Data ```python MOCK_MEETING = { "id": "mtg-123", "title": "Product Review Q1", "created_at":
What does the fathom-local-dev-loop skill do?
Set up local development for Fathom API integrations with mock meeting data. Use when building meeting analytics tools, testing webhook handlers, or iterating on transcript processing pipelines. Trigger with phrases like "fathom dev setup", "fathom local testing", "develop with fathom", "fathom mock data". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill fathom-local-dev-loop --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.