converse
Skill14 starsChanged 20 days agoMITView on GitHub
Sticky auto-speak mode for the current session: after every assistant reply, rewrite it into a short spoken explainer and play it via the same TTS pipeline as /speak, until turned off. Use when the user runs /converse, /converse on, /converse off, /converse status, or says "start converse mode", "converse on", "stop converse", "converse off", "stop auto speak", "stop speaking every reply", or wants hands-free listen-back for the whole session without typing /speak each time. Sticky and session-wide: for one reply read aloud once, use speak.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- boyscout99/skillstheir own version, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- boyscout99/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository32 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/llms-full.txtllms.txt
- docs/llms.txtllms.txt
- adjudicateSkill
- agent-councilSkill
- f-archive-searchSkill
- f-archiveSkill
- f-blueprintSkill
- f-boardSkill
- f-cardSkill
- f-catchupSkill
- f-complySkill
- f-contextSkill
- f-distillSkill
- f-dreamSkill
- f-greploopSkill
- f-inspectSkill
- f-night-shiftSkill
- f-plancheckSkill
- f-scheduleSkill
- f-searchSkill
- f-setupSkill
- f-shiftSkill
- f-signoffSkill
- f-sketchSkill
- f-statusSkill
- f-surveySkill
- model-councilSkill
- orca-pi-connectSkill
- pack-reviewSkill
- speakSkill
- xreviewSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 6 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
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
- Distinctive: line 46
Write or clear this file whenever you change mode so status and later turns can check it.
- Very specific: line 60
If the user runs /converse with no args → on.
- Very specific: line 64
Write scratch/converse-mode with contents on (and optional timestamp line).
- Distinctive: line 66
Run the speak pipeline (below) on that confirmation so they hear that mode started.
- Very specific: line 71
Delete scratch/converse-mode, or write a single line off.
- Distinctive: line 73
Do not speak that confirmation (mode is already off).
- Very specific: line 77
Read scratch/converse-mode.
- Very specific: line 89
Do not wait for the user to re-run /converse or /speak.
- Distinctive: line 104
No code, no file paths, no markdown, no headings, no bullet lists read aloud, natural sentences only.
- Distinctive: line 106
If the reply was already short, smooth it for speech.
- Very specific: line 110
Write the rewritten explainer to scratch/speak-input.txt (overwrite).
- Distinctive: line 112
If the script errors, add a one-line note under the visible reply.
- Very specific: line 120
Prefer /converse off over telling the user to "ignore speak" when they want silence.
≈ “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.
Files
Converse
Sticky conversation listen-back: once on, every finished assistant reply in this session
is spoken aloud (rewrite → TTS → play), until the user turns it off. No per-message /speak.
Uses the same engine as /speak (scripts/speak.ts, Grok Voice by default). Does not
replace a dictation tool for voice input, it only automates voice output.
Usage
/converse # turn ON (default)
/converse on # turn ON
/converse off # turn OFF
/converse status # report whether mode is onNatural-language equivalents (treat the same as the slash forms):
- ON: "start converse", "converse on", "auto speak from now on", "speak every reply"
- OFF: "stop converse", "converse off", "stop auto speak", "stop speaking every reply"
State file
Persist mode in the repo root's scratch/ working folder (keep scratch/ gitignored):
- Path:
scratch/converse-mode - ON contents: a single line
on(optionally a second line with ISO timestamp) - OFF / absent: mode is off
Write or clear this file whenever you change mode so status and later turns can check it.
Instructions
1. Parse intent
| User intent | Action |
/converse, /converse on, or ON phrases | Enable mode |
/converse off or OFF phrases | Disable mode |
/converse status | Report mode from the state file; do not change it |
If the user runs /converse with no args → on.
2. Turn ON
- Write
scratch/converse-modewith contentson(and optional timestamp line). - Reply with a short confirmation, e.g.
🔊 Converse on, every reply will be spoken until you say /converse off. - Run the speak pipeline (below) on that confirmation so they hear that mode started.
- Stay sticky for the rest of this conversation (see § Sticky duty).
3. Turn OFF
- Delete
scratch/converse-mode, or write a single lineoff. - Reply with a short confirmation, e.g.
Converse off, replies are silent again. Use /speak when you want one-off audio. - Do not speak that confirmation (mode is already off).
4. Status
Read scratch/converse-mode. If missing or not starting with on → off. Report in one line. No TTS.
5. Sticky duty (the whole point)
While converse is on (state file is on, or you turned it on earlier this conversation and have not turned it off):
For every subsequent assistant turn that produces a real reply to the user:
- Produce the normal visible reply first (full substance, do not collapse to only
🔊like bare/speak). - Then run the speak pipeline on that reply (rewrite + play).
- You may append a trailing
🔊after the visible reply; optional.
Do not wait for the user to re-run /converse or /speak. Re-check the state file if unsure; if it says on, keep speaking every reply.
Skip the speak pipeline only when:
- Mode is off
- The turn is tool-only with no user-facing message
- The user is mid-turn only approving a dangerous action and you are asking a one-line confirm (still prefer speaking short confirms when mode is on)
- TTS already failed twice in a row this session, note once, keep replying in text, do not spam retries every turn
6. Speak pipeline (same rules as /speak)
Rewrite, do not read the reply verbatim:
- Plain, conversational tone, sharp friend over coffee. Warm, casual, not verbose.
- Gist and why in simple terms. Drop jargon, or define it in a few words if it matters.
- No code, no file paths, no markdown, no headings, no bullet lists read aloud, natural sentences only.
- Tight: ~20–60 seconds (~60–180 words). Key points only. Hard cap ~4000 characters.
- If the reply was already short, smooth it for speech; do not pad.
Then:
- Write the rewritten explainer to
scratch/speak-input.txt(overwrite). - Run:
npx tsx scripts/speak.ts scratch/speak-input.txt - If the script errors, add a one-line note under the visible reply. Do not dump the rewritten explainer text unless the user asks.
Unlike bare /speak, the visible chat reply stays the full answer. Audio is an add-on.
7. Interaction with /speak
/speakwhile converse is on: still works as a one-shot of whatever source/speakuses; then continue auto-speaking future replies./speakwhile converse is off: unchanged (one-shot only).- Prefer
/converse offover telling the user to "ignore speak" when they want silence.
Voice setup
Same as /speak, see .claude/skills/speak/SKILL.md (or its .agents/skills/ mirror):
SPEAK_PROVIDER,grok(default) orhumeSPEAK_GROK_VOICE,eve|ara|rex|sal|leo(default)- Hume:
SPEAK_VOICE_IDviascripts/speak-setup.ts
What this is not
- Not hands-free mic input (dictation / push-to-talk / always-listen tooling stays separate).
- Not multi-session routing.
- Not a permanent global preference across new sessions, each session starts off unless the user turns converse on again (stale
scratch/converse-modefrom a prior session: if the file saysonat the start of a new conversation, treat it as off until the user explicitly re-enables, and clear or rewrite the file when they choose).
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
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.

