live-transcribe-read

Included with Lifetime

$97 forever

Read the latest real-time transcription. Use when user asks to see, read, or show a transcription that was captured via live-transcribe. Triggers on: 'תקריא תמלול', 'מה תמללתי', 'התמלול האחרון', 'show transcription', 'what did I say', 'read the transcript', 'מה נכתב בתמלול', 'תראה לי את התמלול'. Also use when user references transcription content without being explicit — e.g. 'summarize what I said', 'translate the transcription'.

Writing & Docs

What this skill does


# Live Transcribe — Read

Read the most recent transcription file from a live-transcribe session.

## Finding the latest transcription

The real-time transcript lives in the **log file**, not the .txt file. The log updates continuously during recording.

```bash
# Primary source — real-time log (updates live during recording)
cat /tmp/realtime-transcribe.log 2>/dev/null

# Extract only the spoken text (strip metadata lines)
grep '^\[committed\]' /tmp/realtime-transcribe.log 2>/dev/null | sed 's/^\[committed\] //'
```

The `.txt` file (`/tmp/transcribe-*.txt`) may contain a final dump but does NOT update in real-time. Always prefer the log file.

## Check if transcription is still active

```bash
if test -f /tmp/realtime-transcribe.pid && kill -0 $(cat /tmp/realtime-transcribe.pid) 2>/dev/null; then
  echo "ACTIVE — file is still being updated"
else
  echo "FINISHED — file is complete"
fi
```

## Read the file

Use `grep` to extract committed text from the log, stripping `[committed]` prefixes. Skip the first JSON status line and `[session started]` markers.

## What to tell the user

1. The transcription text
2. Whether it's still being updated or finished
3. If still active: they can check again later for more content
4. If no files found: tell them no transcription has been recorded yet

## Working with the transcription

The user may ask to do things with the text beyond just reading it:
- Summarize, translate, extract action items, format, etc.
- The text is available in the main context after reading — proceed with whatever the user asks

Files: 1

Size: 2.1 KB

Complexity: 9/100

Category: Writing & Docs

Source: https://github.com/aviz85/claude-skills-library/tree/main/plugins/live-transcribe/skills/live-transcribe-read

Related in Writing & Docs

jax-development

Included

Use this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.

Writing & Docsscripts

nature-article-writer

Included

Drafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.

Writing & Docsscripts

deckrd

Included

Document-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.

Writing & Docsscripts

clinical-decision-support

Included

Generate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.

Writing & Docsscripts

handling-sf-data

Included

Salesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).

Writing & Docsscripts

accelint-ac-to-playwright

Included

Convert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.

Writing & Docsscripts