agentleFS
GerardoRdz96GerardoRdz96/claude-skills/skills/talk/SKILL.md

talk

Skill0 starsChanged 4 months agoMITView on GitHub

Use when Gera wants to TALK with Servy by voice on his Mac — a live spoken session where he speaks and hears Servy speak back, including English-practice sessions. Triggers — "let's talk", "voice session", "talk to me", "let's practice English by voice", "I want to speak", "/talk", "talk english mode". The core is natural voice conversation; English coaching is one mode. Runs an in-session push-to-turn loop using scripts/talk-record.sh (mic), scripts/transcribe.sh (whisper STT), and scripts/speak.sh (TTS).

11 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use review.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • SentrySkill

    review

    Fixture review skill.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 2 are distinctive, and 7 are very specific to this project.

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 7

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Record: run talk-record.sh --out <tmp.wav>.

    line 42
  2. Very specific:

    Transcribe: run transcribe.sh <tmp.wav>.

    line 45
  3. Distinctive:

    Keep replies conversational and brief.

    line 57
  4. Very specific:

    When in english mode, layer this onto the loop (read english-mode.md in this skill folder for the full coaching contract):

    line 62
  5. Distinctive:

    After his turn, if he made a mistake, recast briefly: "you said X — more natural is Y", then continue the conversation.

    line 66
  6. Very specific:

    Write/append the full transcript to voice/sessions/<date>-<slug>.md.

    line 79
  7. Very specific:

    If english mode: give an end-of-session recap — top 3 recurring patterns from voice/english-log.md, each with the correct form and one …

    line 80
  8. Very specific:

    If turns are frequently mis-heard, switch to SERVY_WHISPER_MODEL=small.en.

    line 90
  9. Very specific:

    All transcripts and the mistake log stay in the gitignored voice/ dir — private.

    line 91

“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “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

/talk — Live voice session with Servy

Gera speaks into his Mac mic; Servy hears him (whisper) and speaks back (say). This skill runs inside the live Claude Code session, so you are Servy — you are the brain. No claude -p; you read the transcript and reply directly, voicing your reply with speak.sh.

The point is natural voice conversation to stay close to Servy and get comfortable speaking. English practice is one mode, invoked with "english mode" — not the default.

Tools this skill drives

StepCommand
Capture a turnscripts/talk-record.sh --seconds <N> --out <wav> (default N=12)
Transcribescripts/transcribe.sh <wav> → text on stdout
Speak a replyscripts/speak.sh "<your reply text>" (plays to speakers)

Voice is swappable: SERVY_TTS_VOICE (default Samantha), SERVY_TTS_ENGINE (default say). Whisper model: SERVY_WHISPER_MODEL (default base.en; use small.en for better accuracy if turns are mis-heard).

Start of session

  1. Confirm mode: free chat (default) or english (say "english mode" to switch).
  2. Tell Gera the turn length (default ~12s) and that he can say "stop talking", "end session", or "switch to english mode" at any time.
  3. Pick a session slug; you'll save the transcript to voice/sessions/<YYYY-MM-DD>-<slug>.md (gitignored, private).
  4. Speak a short greeting with speak.sh so Gera confirms audio works, then start the loop.

The turn loop

Repeat until Gera ends the session:

  1. Record: run talk-record.sh --out <tmp.wav>. Tell him "Go ahead" first so he knows it's listening. (Default 12s window; pass --seconds 20 if he wants longer turns.)
  2. Transcribe: run transcribe.sh <tmp.wav>. If the text is empty or clearly garbled, say (and speak) "I didn't catch that, try again" and re-record — don't guess.
  3. Understand control words in the transcript first:
    • "stop talking" / "end session" / "that's enough" → go to End of session.
    • "switch to english mode" / "free chat" → change mode, confirm by voice, continue.
  4. Reply as Servy: respond naturally in your voice (warm, plain, per references/voice.md). Keep spoken replies short — 1-3 sentences (long monologues are tiring to listen to). Then voice it: speak.sh "<reply>".
  5. Append the exchange (Gera: … / Servy: …) to the session transcript file.
  6. Loop.

Keep replies conversational and brief. This is talking, not writing — favor short turns and let Gera carry half the conversation.

English mode

When in english mode, layer this onto the loop (read english-mode.md in this skill folder for the full coaching contract):

  • Converse naturally at Gera's level; keep it flowing.
  • After his turn, if he made a mistake, recast briefly: "you said X — more natural is Y", then continue the conversation. One or two highest-value fixes per turn, not every error.
  • Log each recurring mistake to voice/english-log.md with a category tag (article / preposition / tense / word-choice / phrasing).
  • Scope honesty: you grade grammar, vocabulary, and fluency — not accent or pronunciation. Whisper transcribes words, not phonetics, so never invent a pronunciation score. If asked about pronunciation, say plainly what you can and can't hear.

End of session

  1. Speak a short closing.
  2. Write/append the full transcript to voice/sessions/<date>-<slug>.md.
  3. If english mode: give an end-of-session recap — top 3 recurring patterns from voice/english-log.md, each with the correct form and one example. Keep it encouraging.
  4. Offer next time: "want me to start the next session in english mode?"

Notes

  • First run needs mic permission: macOS System Settings → Privacy & Security → Microphone → enable Terminal (or your Claude Code app). If talk-record.sh produces silence, that permission is the usual cause — tell Gera.
  • If turns are frequently mis-heard, switch to SERVY_WHISPER_MODEL=small.en.
  • All transcripts and the mistake log stay in the gitignored voice/ dir — private.

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.