Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From plaud-pipeline
This skill should be used when the user explicitly mentions 'plaud', 'плод', 'плауд', 'plaud status', 'pipeline status', 'pipeline health', 'plaud classify', 'classify pending', or references _inputs/Plaud/. Provides 3 MCP tools for local pipeline operations on already-synced recordings. Do NOT trigger on generic 'recording', 'transcript', or 'meeting' without explicit Plaud mention. For raw recording access (list, transcript, audio), use the official @plaud-ai/mcp tools instead.
npx claudepluginhub dkushnikov/plaud-pipeline --plugin plaud-pipelineHow this skill is triggered — by the user, by Claude, or both
Slash command
/plaud-pipeline:plaudThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Local pipeline operations on Plaud voice recordings already synced to disk as `source.md` files.
Creates p5.js generative art with seeded randomness, noise fields, and interactive parameter exploration. Use for algorithmic art, flow fields, or particle systems.
Share bugs, ideas, or general feedback.
Local pipeline operations on Plaud voice recordings already synced to disk as source.md files.
| Tool | What it does |
|---|---|
plaud_status | Pipeline overview — counts by stage (synced/extracted/processed); verbose mode lists per-recording table |
plaud_classify | Classify recordings by category + sensitivity using configured rules (dry-run available; write-back not yet implemented) |
plaud_health | Integrity checks — duplicate IDs, ghost folders (no source.md) |
@plaud-ai/mcp insteadFor raw recording access (Plaud server-side data), use the official Plaud MCP tools:
| User intent | Use official tool |
|---|---|
| "show / list / find my recordings" | list_files |
| "get transcript of " | get_transcript |
| "get AI summary / notes" | get_note |
| "show recording details" | get_file |
| "download audio of " | get_file → presigned URL |
| "log me into Plaud" | login |
This pipeline plugin only reads local files that have already been synced — it does not call Plaud's API.
| Category | Description |
|---|---|
work-meeting | Group meetings recorded on Note or matched to work calendar |
work-1on1 | 1-1 meetings (detected by "1-1", "1on1" patterns) |
personal-diary | Solo recordings on Pin — journal, reflections |
personal-conversation | Multi-speaker Pin recordings with personal keywords |
voice-memo | Short recordings (< 3 min solo) or unclassified |
interview | Recordings with "interview" in title |
| Level | Where it goes |
|---|---|
work | Shared / work context |
personal | Personal context only |
private | HOLD — user decides |
unknown | HOLD — awaits classification |
~/Atlas/bin/plaud-sync.py (server cron) pulls new recordings via plaud CLI → creates source.md (immutable)plaud_classify assigns category + sensitivity from config rulesextract.md metadata card (interactive, user-driven)PLAUD_DATA_DIR environment variable (required) — path to the recordings root directoryplaud.yaml in data dir for devices + classification rules (optional)Plaud API auth is handled by the official @plaud-ai/cli and @plaud-ai/mcp (OAuth tokens in ~/.plaud/tokens.json). This plugin no longer reads PLAUD_TOKEN.