otter-fetch
Skill166 starsChanged 5 months agoMITView on GitHub
Fetch Otter.ai transcript data. Sub-skill used by cache-notes and fill-participants when Notes: contains an Otter URL.
In this repository29 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .agents/skills/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/qmd-search.mdcCursor rule
- .cursor/rules/skill-conventions.mdcCursor rule
- .cursor/rules/skill-registry.mdcCursor rule
- cache-notesSkill
- commitSkill
- defuddleSkill
- fill-participantsSkill
- followup-todosSkill
- json-canvasSkill
- last-1on1Skill
- mail-transcriptsSkill
- meetingSkill
- migrate-tagsSkill
- note-statusSkill
- obsidian-basesSkill
- obsidian-cliSkill
- obsidian-markdownSkill
- onboard-personSkill
- organize-meetingsSkill
- people-stubsSkill
- qmdSkill
- recapSkill
- sprint-retroSkill
- sync-upstream-obsidianosSkill
- vault-healthSkill
- workspace-modeSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 17
cache-notes: When caching a meeting that has https://otter.ai/u/{otid} in Notes: — need callout markdown to embed.
- Distinctive: line 18
fill-participants: When resolving participants for a meeting that only has Otter links (no Google Doc) — need speaker names from the …
- Very specific: line 51
Always extract otid from the share URL (query params like ?utm_source=copy_url can be ignored).
- Very specific: line 52
If the user doesn't have the JSON, they can open the Otter meeting page while signed in, open DevTools → Network, reload, and copy the …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Otter Fetch
Single place for obtaining Otter.ai transcript data. No direct slash command — other skills invoke this when they encounter an Otter.ai URL (e.g. in Notes: frontmatter).
Usage
This skill has no slash command. It's a sub-skill: /cache-notes and /fill-participants invoke its workflow (and run parse_otter.js) when a meeting's Notes: contains an https://otter.ai/u/... URL.
When to use
- cache-notes: When caching a meeting that has
https://otter.ai/u/{otid}inNotes:— need callout markdown to embed. - fill-participants: When resolving participants for a meeting that only has Otter links (no Google Doc) — need speaker names from the transcript.
How to get the data
Otter has no public API. Use user-pasted JSON:
- Extract
otidfrom the URL:https://otter.ai/u/aBcDeFgHiJkLmNoPqRsT→otid = aBcDeFgHiJkLmNoPqRsT. - Ask the user to copy the JSON response from
GET https://otter.ai/forward/api/v1/speech?otid={otid}(e.g. from DevTools → Network while signed in, or from a signed-in request). - User pastes the JSON; the agent (or script) parses it.
Outputs (same JSON, different consumers)
The pasted JSON has speech with:
| Use case | What to use | How |
| cache-notes | Callout markdown | Run parse_otter.js with JSON on stdin → stdout is ## 🤖 AI Notes / ### Otter block with [!otter_notes]-, [!otter_todos]-, [!otter_transcript]-. |
| fill-participants | Speaker names | From speech.speakers: array of { speaker_name }. Use those names with people-resolver to build Participants:. |
So one paste can serve both skills if needed (e.g. cache-notes runs the script; fill-participants reads speech.speakers from the same JSON or from the cached transcript callout).
Script: parse_otter.js
In this folder: parse_otter.js reads the full Otter speech JSON from stdin and writes callout markdown to stdout (for cache-notes).
node .agents/skills/otter-fetch/parse_otter.js < pasted.jsonOutput is the exact block to append under ## 🤖 AI Notes (including ### Otter and the three callouts). Caller appends it to the note and sets NotesCached:.
Important notes
- Always extract
otidfrom the share URL (query params like?utm_source=copy_urlcan be ignored). - If the user doesn't have the JSON, they can open the Otter meeting page while signed in, open DevTools → Network, reload, and copy the response body of the
speech?otid=...request.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

