skills/transcribe/SKILL.md
Transcribe audio and video files using Audetic whisper service. Use when: (1) User wants to transcribe an audio or video file (2) User has a recording and needs a text transcript (3) User wants transcript analysis (gaps, speech rate, silence detection) (4) User wants to transcribe all media files in a directory Triggers: "transcribe", "transcription", "transcript", "speech to text", "audio to text", "transcribe audio", "transcribe video", "transcribe recording"
npx skillsauth add silvabyte/skills transcribeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Transcribe any audio or video file using the Audetic whisper service, producing a JSON transcript, readable markdown, and signal analysis.
Environment variables (optional, have defaults):
| Variable | Purpose | Default |
|----------|---------|---------|
| AUDETIC_API_URL | Audetic transcription service URL | https://audio.audetic.link |
All paths are relative to this skill's directory. Run with bun run.
| Command | Purpose |
|---------|---------|
| scripts/transcribe.ts <media-file> | Transcribe a single audio or video file — produces JSON + markdown transcript + analysis alongside the file |
| scripts/transcribe.ts <directory> | Transcribe all media files in a directory — produces merged JSON + markdown transcript + analysis in the directory |
| Type | Extensions | |------|------------| | Audio | mp3, wav, flac, ogg, m4a, aac, wma | | Video | mp4, mkv, mov, webm, ts |
bun run scripts/transcribe.ts <media-file>
Compresses audio to MP3, uploads to the Audetic transcription service, and produces three files alongside the media file:
.json — transcription result (structured data with word-level timestamps)-transcript.md — readable transcript table-analysis.md — transcript with signal flags (gaps, speech rate)The transcript markdown is a numbered table of segments with timestamps and text. The analysis adds signal flags:
| Flag | Meaning |
|------|---------|
| gap:Xs | Silence of X seconds before this segment |
| slow | Fewer than 0.5 words/second (typing, long pauses, dead air) |
| silence | Zero words detected in segment |
See references/signal-interpretation.md for detailed signal guidance.
bun run scripts/transcribe.ts <directory>
Finds all supported media files, transcribes each one, and produces merged output in the directory:
transcript.json — merged transcript with source field on each segmenttranscript.md — merged readable table with Source columnanalysis.md — merged analysis with Source column (gap detection resets at file boundaries)| Output | Pattern |
|--------|---------|
| Transcript JSON | <name>.json |
| Transcript MD | <name>-transcript.md |
| Analysis MD | <name>-analysis.md |
| Output | Pattern |
|--------|---------|
| Transcript JSON | transcript.json |
| Transcript MD | transcript.md |
| Analysis MD | analysis.md |
tools
Weekend Business Shared Drive: Browse, search, upload, and manage files. Triggers: 'weekend business drive', 'wb drive', 'upload to brand', 'shared drive', 'WB shared drive', 'list WB files', 'find in drive'
documentation
--- name: unglaze description: Rewrite glazy, eye-glazing generated content into a tight, scannable, bullet-tight engineering voice. Use when the user says "unglaze", "ungloss this", "punch this up", "tighten this", "less glazy", "eyes glaze", "make my eyes not glaze", "cut the fluff", "rewrite punchier", "make it sharper", "less corporate", "de-fluff", "less LLM-flavored". Also auto-triggers on dissatisfaction signals like "ugh too long", "tldr this", "this is boring", "too much". Applies to PR
development
Testing Trophy philosophy for JS/TS. Use when: writing tests, deciding what/how to test, reviewing tests, choosing unit/integration/E2E, mocking decisions. Triggers: "write tests", "what should I test", "test this component", "review my tests", "testing strategy", "mock this", "test setup".
tools
Drive a UI flow with chrome-devtools, capture a screenshot per step, then render a self-contained HTML report (report.html) showing each step with status pills, full console log, and full network log per step. Use when: (1) User asks to "QA this flow", "walk through X with screenshots", "verify [feature] end-to-end with a report" (2) User wants screenshot-backed evidence that a multi-step UI flow worked (3) User wants a single artifact they can attach to a PR or share as proof of a manual walkthrough Do NOT use for one-off "open this page and check console", for automated regression testing (a Playwright/Cypress suite is the right tool), or for single-screenshot bug repros. Triggers: "QA this flow", "qa flow report", "walk through X with screenshots", "verify end-to-end with a report", "screenshot-backed evidence", "manual QA report"