agentleFS
kiku-jwkiku-jw/codex-skills/transcribe-basic/SKILL.md

transcribe-basic

Skill0 starsChanged 4 months agoMITView on GitHub

Produce a fast plain-text transcript with the bundled CLI using the light transcription model. Use when speaker diarization is not needed.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not use when: the user explicitly needs diarization or known-speaker matching.

    line 10
  2. Very specific:

    Run ~/.codex/skills/transcribe/scripts/transcribe_diarize.py with gpt-4o-mini-transcribe and plain text output under a stable output path …

    line 18

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Transcribe Basic

Metadata

  • Trigger when: the user needs a fast transcript without speaker labels.
  • Do not use when: the user explicitly needs diarization or known-speaker matching.

Skill Purpose

Generate the fastest honest transcript path for audio by keeping the job to plain transcription instead of overcomplicating it with diarization.

Instructions

  1. Confirm the audio path and check that OPENAI_API_KEY is set. If the key is missing, stop and tell the user to set it locally.
  2. Run ~/.codex/skills/transcribe/scripts/transcribe_diarize.py with gpt-4o-mini-transcribe and plain text output under a stable output path such as output/transcribe/.
  3. Validate that the transcript exists, is readable, and matches the requested file/output format. Note any caveat caused by audio quality, chunking, or language uncertainty.

Non-Negotiable Acceptance Criteria

  • Secrets stay in environment variables, never in chat.
  • The model choice is the fast plain-transcription path, not diarization-heavy overkill.
  • Output location and format are explicit.
  • Audio-quality limitations are stated when they materially affect trust in the transcript.

Output

  • The transcript path.
  • The model and response format used.
  • A short note on transcript quality or caveats.
  • Next skill options (only if needed): $transcribe-diarize — use when the user later needs speaker labels or diarization.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.