plaud
vv29by nexaedge · author: Jaison Erick
Turn Plaud.ai voice recordings into text inside the repository you are working in: find the recording, transcribe it, bring the transcript down with the speakers it recognises already named. Where that transcript then gets filed is read from the repository's own.plaud.json, never assumed, so the same skill serves a knowledge base and a client project without knowing either.
What plaud does, in the publisher's words
Plaud.ai records the meeting; this plugin is how that audio becomes text inside a repository.
It stops at the transcript. Turning it into a note, naming the file, choosing where it goes: that is the repository's business, declared in.plaud.json at its root. The same skill then serves a knowledge base that indexes every recording it has ever seen and a client project that only wants the occasional call, without knowing anything about either.
From the project README, punctuation lightly normalized · Open the README on GitHub
- Skills
- 1
- MCP servers
- 0
- Stars
- 1
- License
- n/a
- Repo created
- 2026-03-05
- Last pushed
- 2026-09-16
- Publisher type
- Organization
- Version
- v29
Links
Skills · 1
- plaud
- Work with Plaud.ai voice recordings: find a recording, bring its transcript into the current repository, keep a set of recordings in sync, and say who is speaking. Where the transcript lands, what it is called and what describes it are read from the repository's own `.plaud.json`, never assumed. Tr…
Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.
Category
Integrations & APIs. Assigned by this directory. Agent Plugins 1.0.0 has no category field, so no manifest declares one.
Keywords
plaud · recording · transcript · meeting
Related by publisher and keywords
Publish a self-contained HTML file as a shareable artifact on artifacts.nexaedge.com. Sign in with any Google Workspace account: the artifact belongs to that account's domain, and only that domain can open it. Also issues expiring links for people outside the domain.
Manage Cloudflare DNS zones and records through Terraform in the nexaedge/infrastructure repository. Automates the full workflow: edit Terraform files, open PR, review plan, merge, watch apply, and verify.
Turn finished analysis results into a self-contained interactive HTML report: charts, cohort heatmaps, sortable tables and stat tiles, all inline in one file that opens by double-click with no network. Carries no brand of its own: it derives a theme from a brand color, or lifts one verbatim out of a report it built earlier.
Spec-driven project execution pipeline backed by Linear. Same skills and agents as spec-plugin, but writes specs, stories and validation to Linear via GraphQL while keeping reasoning artifacts on disk.
Read any Miro board you can open in your browser, then work out what it says. Miro's public API cannot reach a board you were invited to in someone else's team, and the canvas is WebAssembly so there is nothing in the page to scrape; this reads the board through your own signed-in session instead, opening Chrome once and then talking to Miro's realtime gateway directly. Extraction and interpretation are kept apart on purpose: the scripts measure geometry, colour, containment and edge alignment and never conclude anything, offering overlapping candidate groupings with the evidence behind each, because what a board means lives in how it was arranged and only reading the text can settle it.
Front end for the nexaedge marketplace that works the same on Claude Code, Codex and Antigravity. Detects which agent is running, translates to that agent's native install path, and keeps everything at user scope so a plugin is installed once per machine rather than copied into each repository.
[](https://agentpluginsdirectory.com/plugins/plaud)✓ Verified . We fetched the manifest from GitHub and checked it against the official Agent Plugins 1.0.0 schema at agent-plugins.org.