input-branching
Skill535 starsChanged 7 months agoApache-2.0View on GitHub
Route voice input from the realtime voice agent pipeline based on message tags.
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 28
No tags. Process as a normal voice event.
- Very specific: line 44
[voice-instruction]is the primary input: When present, use it over [transcript]. - Very specific: line 45
[HANDLED]→ alwaysNO_REPLY, and never act on it: No exceptions. Even if the reply seems wrong, incomplete, or claims something was … - Distinctive: line 54
Keep routing and tool planning in the provider's native thinking channel.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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
Input Branching
Voice input passes through a realtime voice agent before reaching you. The agent handles chit-chat directly and delegates everything else. Message tags tell you which path was taken.
Message Formats
Delegated with instruction
[voice-instruction] Play jazz music on Spotify
[transcript] play some jazz please on spotify[voice-instruction]— the realtime agent's clean summary of what the user wants. Use this as the primary input.[transcript]— raw STT transcript. Often inaccurate — STT is locked to one language while the user may speak another. Treat as noisy supplementary context only, never as the source of truth.
Delegated without instruction (fallback)
turn on the lightsNo tags. Process as a normal voice event.
Handled (history entry)
[HANDLED] Hey, how's it going?
[REPLY] I'm doing great! How about you?[HANDLED]— the user's original message, already answered via TTS.[REPLY]— what the realtime agent said. The user already heard it.
This is a history entry only. The conversation already happened. You are being notified, not asked to respond.
Rules
[voice-instruction]is the primary input. When present, use it over[transcript].[HANDLED]→ alwaysNO_REPLY, and never act on it. No exceptions. Even if the reply seems wrong, incomplete, or claims something was done that wasn't — the user already heard it. Do not correct, echo, paraphrase, add to, finish or redo it.- Log context from
[HANDLED]silently — memory/mood/wellbeing only. If the exchange reveals mood, intent, or information worth tracking (fatigue, stress, preferences), update memory/mood/wellbeing. Never record names or identities from it. No device, camera, face, voice-enrollment or messaging calls, even when a skill you loaded earlier (e.g. face-enroll) is mid-flow. A pending task resumes only on a live (non-[HANDLED]) message, including one marked[realtime-handoff]. - Never echo tags.
[voice-instruction],[transcript],[HANDLED],[REPLY]are routing metadata, not user-facing text. Interpret routing, transcript differences, and speaker metadata silently. Assistant reply text is spoken aloud: start with any required HW markers and the user-facing answer, without narrating which input or skill you chose. - No prefix = normal voice event. Process the message as-is.
- Compound instructions: execute EVERY clause. A
[voice-instruction]often carries several actions plus a question ("Rotate to the right, hold that position, then describe what you see"). Handle each clause, in order, with the skill it belongs to — and never confirm a clause you did not actually perform. Answering the question half while silently skipping the movement (or vice versa) is the worst outcome: the user hears "done" for something that never happened.
Spoken delivery
Keep routing and tool planning in the provider's native thinking channel; do not copy a reasoning summary into ordinary text before/after tools or the final reply. If unavailable, omit analysis. For a simple voice command, give one short confirmation after the required action, including a failure or essential next step when applicable. For a question, lead with the answer and use only the detail needed; longer explanations, stories and requested readbacks remain valid. Brevity must not drop clauses from compound instructions, required consent, or important safety information. Use available context and avoid redundant skill reads or repeated checks merely to refine phrasing.
Examples
Delegated — use instruction, ignore noisy transcript:
[voice-instruction] Set brightness to 50%
[transcript] set the brightness to like half→ Process "Set brightness to 50%". Route to LED skill.
Delegated — transcript in wrong language (user spoke Vietnamese, STT is English):
[voice-instruction] Turn off the light and play some relaxing music
[transcript] ton of delay and play some relate music→ Process the [voice-instruction]. The transcript is gibberish because STT tried to transcribe Vietnamese as English.
Delegated — transcript garbled by accent/noise:
[voice-instruction] What is the weather like tomorrow
[transcript] what is the wetter like to morrow→ Process the [voice-instruction]. The transcript has misheard words.
Delegated without instruction:
play some jazz music→ Process as-is. Route to music skill.
Handled — silent:
[HANDLED] What time is it?
[REPLY] It's 3:15 PM.→ NO_REPLY.
Handled — log mood:
[HANDLED] I'm so tired today
[REPLY] That sounds rough. Maybe take a short break?→ Log fatigue via mood/wellbeing. NO_REPLY.
Other versions2 projects use a version of this.
Word for word · 2
- autonomous-ai/autonomous-os★ 535100% same
- autonomous-ai/Physical-AI-Operating-System★ 535100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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 repository34 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/architecture.mdcCursor rule
- .cursor/rules/docs-on-code-change.mdcCursor rule
- .cursor/rules/multi-ide.mdcCursor rule
- .cursor/rules/testing.mdcCursor rule
- agent-managementSkill
- audioSkill
- cameraSkill
- claude-buddySkill
- computer-useSkill
- connectorsSkill
- displaySkill
- emotionSkill
- environmentSkill
- face-enrollSkill
- faqSkill
- guardSkill
- habitSkill
- harness-useSkill
- led-controlSkill
- moodSkill
- musicSkill
- music-suggestionSkill
- sceneSkill
- sensingSkill
- sensing-trackSkill
- servo-controlSkill
- servo-trackingSkill
- skill-creatorSkill
- speaker-recognizerSkill
- user-emotion-detectionSkill
- voiceSkill
- wellbeingSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

