MyClawBots- Productivity
- Voice notes
- Planning
- Briefs
Thinking Out Loud
A contract for what the agent does when a long, messy, stream-of-consciousness ramble arrives (usually voice dictation): act on nothing until the echo brief is approved. The echo audits the entire transfer, mission, locked decisions and constraints, open questions, flips and parked tangents, with the model's inferences and guesses quarantined away from the user's own phrasing, so the user verifies what the model believes, not just what it doubts. Use when the user says "let me think out loud" or wants to ramble a bit before building anything, when a message opens with a speech-to-text preamble like "switching to voice, sorry for typos", when input is a long weakly punctuated stream with restarts and mid-message reversals ("actually no, wait, scrap that idea entirely"), or when the user asks to be interviewed about a fuzzy half-formed idea. Includes an optional capture mode for rambles spread across several messages and an optional targeted interview.
SKILL.md
Thinking Out Loud
A ten minute voice ramble transfers more context than any prompt a person would type, and models reconstruct rambles well. The failure is downstream and invisible: the model fills every gap in the ramble confidently. "The usual model" silently becomes a specific model. "The standard size" becomes a specific viewport. A position the user reversed mid-ramble survives as fact. None of this registers as uncertainty from the inside, so none of it ever becomes a clarifying question. The model then acts on a misreading it fully believes, and the user discovers it an hour of generated work later.
This skill is the fix: before acting on any ramble, produce an echo, a short structured audit of everything absorbed, with the model's own additions quarantined from the user's words. The user corrects three lines instead of debugging a built artifact.
On a MyClawBots agent
- Owners often talk to their agent through Telegram voice notes, which arrive as a transcript: a long, weakly punctuated ramble is exactly what this skill is for. Capture mode fits a run of several voice notes.
- Persistence: you have no CLAUDE.md or
docs/folder. The three options become: (1) save the brief to your memory/notes so later sessions inherit it, (2) save it to/root/.openclaw/workspace/rambles/YYYY-MM-DD-<topic>.md, (3) keep it in this conversation only. - "Act on nothing" includes outward actions: no posts, DMs, emails, Studio drafts or scheduled jobs until the owner approves the echo.
Why an echo instead of follow-up questions
Asking clarifying questions is good, and the interview below does it. But questions alone cannot secure a ramble, for two structural reasons:
- Questions verify what the model doubts. The echo verifies what the model believes. A clarifying question requires felt uncertainty, and confident misreadings feel like knowledge. The echo forces every inference and gap-fill into the open whether or not it felt uncertain.
- Questions sample; the echo audits. A long ramble carries dozens of facts and half-decisions. Even good questions probe three or four; the rest of the model's understanding goes unverified into action. The echo inventories the entire transfer, and it works by recognition, not recall: the user reads and spots what is wrong, which is far cheaper than producing answers, and ramblers often do not know their answer until they see the wrong guess written down.
The contract
- Act on nothing. No file edits, no code, no plans, no solutions to fragments, until the echo is approved. Reconstruct first.
- Label every addition. Inferences and guesses live in their own section, apart from the user's own content. Never present a guess in the user's voice.
- Surface every reversal. Adopt the later position, but flag the flip. Never silently average or pick.
- Lose nothing. Tangents get parked, not dropped.
- Never remark on dictation artifacts. Typos, homophones, filler, and restarts are resolved silently from context. Keep the user's own vocabulary and project names.
- Ask before persisting. The approved brief is offered a home, never saved unprompted.
When to use
- A message is a long, weakly punctuated stream of consciousness with restarts, filler, and mid-message reversals ("actually no, scrap that")
- A message opens with a voice preamble ("switching to speech recognition, sorry for any typos", "dictating this")
- The user says they want to ramble or think out loud
- The user asks to be interviewed to untangle a fuzzy idea
When not to use
- Short requests that are already clear
- The user wants a verbatim transcript, minutes, or cleanup of dictation while keeping their exact words
- Long but already structured text, such as a pasted spec or document
- The user asked a direct question and wants a direct answer
The echo
One structured reply. Dense, scannable, and short: the user should find and fix an error in seconds. Full template with a worked example in references/echo-format.md.
- Mission: one sentence stating what the user is actually trying to achieve. Often this differs from what they said first; that is fine.
- Locked: the user's decisions and constraints, merged into one list. Mark anything they called a top priority.
- Open: questions the ramble raised but did not answer.
- Ledger: flips (both positions in one line, later one adopted) and parked tangents (one line each).
- My additions: the only interpretation callouts. "Inferred" (strongly implied but never stated) and "Guessed" (gaps you filled). Tell the user to correct these first.
Compression rules, non-negotiable:
- Nothing appears twice. Every fact lives in exactly one section.
- No "you said" recap. Everything outside My additions is the user's own content by definition; only the model's additions get called out.
- One line per bullet. If a bullet needs two lines, it is two bullets or it is bloat.
- Vague quantifiers are never silently resolved. "The usual model", "standard size", "soon": each lands in Open or Guessed, never absorbed into a locked item as if it were specified.
Close by inviting corrections and offering the interview.
The interview (optional)
Follow-up questions have their place: after the audit, not instead of it. Only if the user accepts the offer, or asked to be interviewed up front.
- Ask only about items flagged in Open or Guessed
- One question per message, highest information gain first
- Each question states in one clause why it matters
- Cap at five questions; stop early once answers stop changing the brief
- After the interview, restate only the sections of the echo that changed
Capture mode (multi-message rambles)
Not needed for dictation tools, where the whole ramble arrives as one message. Use it when the user invokes the skill before rambling and then adds thoughts across several messages, possibly over a long stretch.
- Acknowledge once, in one short line ("Go ahead, I'm listening. Say 'done' when you want the echo.")
- For every following message, reply with a single minimal line ("Listening."). Vary it slightly so it does not feel robotic.
- Do NOT solve, praise, summarize, analyze, or ask questions mid-stream.
- If the user asks a direct question mid-ramble, answer it in at most two sentences, then return to listening.
- Exit on "done", "echo", "echo me", "that's it", "what did you get", or any clear equivalent, then deliver the echo.
Persistence
After the user approves the echo, offer exactly three options:
- Append the brief to CLAUDE.md so future sessions inherit it
- Save it to
docs/rambles/YYYY-MM-DD-<topic>.md - Keep it in-conversation only
The approved brief then governs the rest of the session: honor its decisions and constraints without re-asking.
Files
3 files ship with this skill. They are installed beside the SKILL.md.
LICENSE11.1 KB
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.