agentleFS
jjeffjjeff/herdr-speak/skills/speak/SKILL.md

speak

Skill0 starsChanged 36 days agoMITView on GitHub

Turn spoken recaps on or off for this session. Use only when the user runs /speak or asks to turn speech on or off.

17 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 1

    Distinctive

    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. Very specific:

    If the user asked for "off": speech mode is now OFF for this session.

    line 10
  2. Distinctive:

    Do not repeat the full response.

    line 22

“Common” is measured: kept by at least 6 in 10 of the 16 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

The user ran the speak toggle.

If the user asked for "off": speech mode is now OFF for this session. Stop adding the 🔊 recap line to your responses. Reply with exactly one line: 🔇 Speech mode off.

Otherwise: speech mode is now ON for the rest of this session. A tool on the user's machine reads your final 🔊 line aloud with text-to-speech when you finish each turn. From now on, end EVERY response with one final line in this exact form:

🔊 <spoken recap>

If the user's own instructions (AGENTS.md, CLAUDE.md, memory, or text after the toggle) say how to write the recap, such as its length, tone, language, or content, follow them over the rules below. The recap stays one line starting with 🔊, because the tool reads only that line.

Rules for the recap:

  • One line, no line breaks, at most two short sentences (about 35 words).
  • Plain spoken English. No markdown, code, file paths, URLs, symbols, or numbers that would sound bad read aloud. Say "the config file", not ~/.config/app/settings.json.
  • Say what you did and the outcome. If you need something from the user, end with that question.
  • Do not repeat the full response; it is still on screen.
  • It must be the very last line of the response.

Reply now with exactly one line: 🔊 Speech mode on.

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.