audio-tools-workflow

Use the RUDI audio-tools stack to transcribe, enrich, index, and query speech from local audio/video files, direct media URLs, supported video-page URLs, or base64 media input. Trigger when the user asks to process audio, video-linked speech, voice memos, meeting recordings, interviews, podcasts, clips, transcripts, transcript search, transcript enrichment, or audio-derived notes with the audio-tools stack.

Ir a la instalación

Repositorio: learnrudi/registry
Última actividad en el origen: 1 de agosto de 2026 a las 21:27
Idioma detectado de SKILL.md: inglés
Estrellas: 0
Forks: 0

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

npx skills add https://github.com/learnrudi/registry --skill audio-tools-workflow

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Explorador de archivos

2 archivos

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

Volver a la búsqueda Volver a la instalación

horizontal-engineering-review

Assess repository-wide architectural coherence across multiple changes, assign evidence-backed dispositions to semantic duplication and shared-contract drift, and plan or execute authorized consolidation. Use for horizontal architecture reviews, repeated mechanisms, consolidation obligations, or cross-module drift; do not use for ordinary single-change code review or Git worktree cleanup.

2026-08-26

map-change-impact

Map the exact repository paths a proposed feature, fix, refactor, migration, or remediation will affect and print the ordered actions, risks, dependencies, and verification needed before implementation. Use when a user asks what file paths will be impacted, what needs to change, what has already been implemented, what remains to do, what the blast radius is, or wants an implementation-ready change map without starting the edits.

2026-08-20

rudi-chief-of-staff

Coordinate complex single- or multi-project objectives from the initiating agent through an acceptance-led task graph, exact provider/model routing, durable run lifecycle, resource and review limits, explicit handoffs, bounded workers, and evidence-backed integration with human oversight. Use when the user asks to delegate dependent work, run a crew, act as a chief of staff or first mate, coordinate multiple agents or desktop tasks, or keep a long-running project moving predictably across worktrees, projects, or hosts.

2026-08-11

Ver todos los de este repositorio

Audio Tools Workflow

Use the local audio-tools MCP stack for speech-to-text workflows. The stack provides audio_transcribe, audio_enrich, audio_sync, audio_stats, and audio_query.

Workflow

Identify the source shape:

local file path: pass file
HTTP(S) direct media or supported video page: pass url
base64 media: pass data and filename

Call audio_transcribe first. It writes JSON and Markdown outputs under ~/.rudi/output/audio-tools/transcripts/YYYY/MM/DD/.

Preserve the returned transcript JSON path. Use it for enrichment and indexing.

Call audio_enrich only when the user needs metadata such as title, summary, tags, topics, people, sentiment, keywords, or action items.

Call audio_sync after transcription or enrichment when query/search/index results matter.

Use audio_stats for a quick collection overview.

Use audio_query for focused analysis across the SQLite transcript index.

Guardrails

Treat transcripts as private user data.

Do not include credentials, API keys, or raw secret values in prompts, outputs, config files, or stack packages.

Only pass HTTP(S) URLs to URL input. The stack rejects other URL schemes.

Prefer read-only SELECT queries with audio_query. Do not run destructive SQL unless the user explicitly asks for database modification.

If enrichment fails because no prompt template is configured, report that transcription completed and name the missing configuration requirement.

If a private source requires authorization, use the host connector to obtain the source file or URL before invoking the stack.

If audio_transcribe reports a missing binary or Whisper model, treat that as a runtime provisioning issue in the MCP/plugin environment. Do not assume a successful manual shell command means the MCP server can see the same dependency.

Useful Files

Connector hints: connectors/host-provided.json

Environment and secret requirements: secrets/required.json

MCP launch contracts: mcp/servers.json

Transcript JSON schema: outputs/schemas/transcript-record.schema.json

Query examples: references/query-examples.md