How do I install the Meeting Transcriber skill?

Run npx skillmds@latest add tomevault-io/meeting-transcriber in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Meeting Transcriber safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Meeting Transcriber?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Meeting Transcriber free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Meeting Transcriber?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Meeting Transcriber by tomevault-io

Name: Meeting Transcriber
Author: tomevault-io

File contents

Meeting Transcriber — shell-driven inspection

The dev build of Meeting Transcriber can run an embedded debug RPC server. When it's running, prefer mt-cli over asking the user "kannst du screenshot machen" / "ist das im Menü sichtbar".

When to use

You want to know what's in the speaker DB right now → mt-cli state
You want to verify the app is alive after a code change → mt-cli healthz
You want to see what the user sees → mt-cli screenshot /tmp/x.png, then Read it
You're debugging a UI bug and would otherwise have to ask the user to describe state
You're verifying a fix end-to-end after editing code

Don't use it for production debugging — RPC is #if !APPSTORE only.

How to enable

Either persistent (preferred for repeated dev sessions):

Settings → Advanced → toggle Local Automation API on. The server starts immediately and survives app relaunches.

Or per-session (one-shot, e.g. for scripts/test_rpc.sh):

MEETINGTRANSCRIBER_DEBUG_RPC=1 ./scripts/run_app.sh

The app writes a 64-hex bearer token to ~/Library/Application Support/MeetingTranscriber/.rpc-token (chmod 0600). mt-cli reads it automatically — no config needed on your side.

Endpoints

HTTP	mt-cli	Returns
`GET /healthz`	`mt-cli healthz`	"ok"
`GET /state`	`mt-cli state`	Pipeline + speaker DB JSON
`GET /screenshot`	`mt-cli screenshot`	PNG of frontmost window

Build mt-cli

From the repo root:

cd tools/mt-cli && swift build
.build/debug/mt-cli state | jq .

Failure modes

"app is not running on http://127.0.0.1:9876" → either the dev app isn't running, or the toggle / env flag was off when it launched. Ask the user to enable Settings → Advanced → Local Automation API, or relaunch with MEETINGTRANSCRIBER_DEBUG_RPC=1 ./scripts/run_app.sh.
"RPC token not found" → same as above; the token is created on first successful start.
HTTP 401 → token rotated. Restart the app or delete the token file.
HTTP 403 with Origin header → You're hitting it from a browser. Use curl or mt-cli instead.

Security model

Loopback bind (127.0.0.1 only) + Origin reject + bearer token. Two-layer defense against browser CSRF and cross-user access on shared Macs. See app/MeetingTranscriber/Sources/DebugRPCServer.swift for the threat model.

Source: pasrom/meeting-transcriber — distributed by TomeVault.

---name: meeting-transcriberdescription: Use when working on the Meeting Transcriber repo and you need to inspect or drive the running dev app from the shell instead of asking the user for screenshots.---# Meeting Transcriber — shell-driven inspectionThe dev build of Meeting Transcriber can run an embedded debug RPC server.When it's running, prefer `mt-cli` over asking the user "kannst du screenshotmachen" / "ist das im Menü sichtbar".## When to use- You want to know what's in the speaker DB right now → `mt-cli state`- You want to verify the app is alive after a code change → `mt-cli healthz`- You want to see what the user sees → `mt-cli screenshot /tmp/x.png`, then Read it- You're debugging a UI bug and would otherwise have to ask the user to describe state- You're verifying a fix end-to-end after editing codeDon't use it for production debugging — RPC is `#if !APPSTORE` only.## How to enableEither persistent (preferred for repeated dev sessions):- Settings → Advanced → toggle **Local Automation API** on. The server starts immediately and survives app relaunches.Or per-session (one-shot, e.g. for `scripts/test_rpc.sh`):```bashMEETINGTRANSCRIBER_DEBUG_RPC=1 ./scripts/run_app.sh```The app writes a 64-hex bearer token to`~/Library/Application Support/MeetingTranscriber/.rpc-token` (chmod 0600).`mt-cli` reads it automatically — no config needed on your side.## Endpoints| HTTP | mt-cli | Returns || ------------------- | ------------------- | ---------------------------------- || `GET /healthz` | `mt-cli healthz` | "ok" || `GET /state` | `mt-cli state` | Pipeline + speaker DB JSON || `GET /screenshot` | `mt-cli screenshot` | PNG of frontmost window |## Build mt-cliFrom the repo root:```bashcd tools/mt-cli && swift build.build/debug/mt-cli state | jq .```## Failure modes- **"app is not running on http://127.0.0.1:9876"** → either the dev app isn't running, or the toggle / env flag was off when it launched. Ask the user to enable Settings → Advanced → Local Automation API, or relaunch with `MEETINGTRANSCRIBER_DEBUG_RPC=1 ./scripts/run_app.sh`.- **"RPC token not found"** → same as above; the token is created on first successful start.- **HTTP 401** → token rotated. Restart the app or delete the token file.- **HTTP 403 with Origin header** → You're hitting it from a browser. Use curl or `mt-cli` instead.## Security modelLoopback bind (`127.0.0.1` only) + Origin reject + bearer token. Two-layerdefense against browser CSRF and cross-user access on shared Macs. See`app/MeetingTranscriber/Sources/DebugRPCServer.swift` for the threat model.---> Source: [pasrom/meeting-transcriber](https://github.com/pasrom/meeting-transcriber) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions

Meeting Transcriber