summarize
Skill1 starsChanged 6 days agoMITView on GitHub
Use this skill when the user wants to post a one-paragraph status report about the work just performed to a Telegram chat.
98 other projects use a version of this.
Adopted by
Most recently taken up by
- getappz/agentflaretheir own version, first seen Nov 16, 2026
- Philmattt04/Claude-Skillstheir own version, first seen Nov 16, 2026
- zkManuel0123/CodexClawtheir own version, first seen Nov 16, 2026
- metaspartan/cybaratheir own version, first seen Nov 15, 2026
- CloudChef/atlasclaw-providerstheir own version, first seen Nov 8, 2026
- domengabrovsek/agent-configtheir own version, first seen Nov 8, 2026
Used with
Projects with it also use openclaw-performance, plugin-sdk-impact and 10 more.
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.
clawdbotSkillopenclaw-performance
Performance work in OpenClaw: a slow or heavy flow (latency, CPU, memory, SQL, RPC, renders), writing or reviewing a perf PR, or adding a cache. Count the work, delete waste first, cache last.
Also in 7 projects that use this
clawdbotSkillplugin-sdk-impact
Count Plugin SDK consumers across live ClawHub releases and bundled OpenClaw plugins before deprecation, removal, or behavior changes; supports public release-date filters.
Also in 7 projects that use this
AtomicBot-aiSkilltaskflow-inbox-triage
Also in 6 projects that use this
hkyutongSkillnode-connect
Diagnose OpenClaw node connection and pairing failures for Android, iOS, and macOS companion apps. Use when QR/setup code/manual connect fails, local Wi-Fi works but VPS/tailnet does not, or errors mention pairing required, unauthorized, bootstrap token invalid or expired, gateway.bind, gateway.remote.url, Tailscale, or plugins.entries.device-pair.config.publicUrl.
Also in 18 projects that use this
molt-botSkilldiscord-e2e
Test Discord with Convex-leased QA bots: check credentials without a Gateway, exercise owned messages, or prove OpenClaw replies, files, threads, reactions, streaming, and typing. Distinguish API and Gateway evidence from manual user interactions.
Also in 10 projects that use this
molt-botSkillopenclaw-repair-sweep
Run scoped OpenClaw issue/PR repair campaigns: coordinate workers, prove root causes, and land or close verified work under the requested authority.
Also in 10 projects that use this
- +2 more from molt-bot
Other versions98 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 98
- steipete/warelay★ 395ksame name
- moltbot/clawdbot★ 395ksame name
- openclaw/openclaw★ 395ksame name
- steipete/clawdis★ 394ksame name
- moltbot/moltbot★ 394ksame name
- clawdbot/clawdbot★ 394ksame name
- molt-bot/clawdbot★ 391ksame name
- spinabot/brigade★ 11ksame name
- steipete/summarize★ 6.8ksame name
- the-open-agent/openagent★ 5.7ksame name
88 more not listed
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.
The file
Show its rules and text
We split this skill into the rules it gives an agent
20 rules. 0 are common, 7 are distinctive, and 13 are very specific to this project.
0
Common
Most of the 86 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
13
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Stop when WITNESS_TOKEN or WITNESS_CHAT is unset or empty.
- Very specific: line 12
Read bot token from WITNESS_TOKEN and chat id from WITNESS_CHAT.
- Very specific: line 13
Treat WITNESS_CHAT as integer chat identifier.
- Distinctive: line 19
Use only steps earlier plugins, skills, and agents actually ran.
- Distinctive: line 21
Use only what conversation records.
- Distinctive: line 40
Keep body plain prose, free of headings, lists, tables, blocks, and rules.
- Very specific: line 44
Write report as personal status update.
- Distinctive: line 53
Read URL from environment variable host injects.
- Very specific: line 67
Use Markdown only for hyperlinks and backticked fixed-width text.
- Very specific: line 68
Keep other text plain, free of bold, italics, lists, tables, and blocks.
- Distinctive: line 72
Leave inline code, link labels, and link URLs untouched.
- Distinctive: line 76
Keep paragraph under one thousand characters.
- Distinctive: line 77
Keep whole message under four thousand.
- Very specific: line 84
Verify response ok field is true.
- Very specific: line 89
Keep Claude, Anthropic, and every AI agent unnamed in message.
- Very specific: line 90
Keep every language model and automation tool unnamed too.
- Very specific: line 91
Leave out any generated by line, marketing footer, and AI-disclosure trailer.
- Very specific: line 92
Keep value of WITNESS_TOKEN out of every log, print, echo, and file.
- Very specific: line 93
Stop after single successful sendMessage call.
- Very specific: line 97
Read four sample reports in examples/ directory first.
“Common” is measured: kept by at least 6 in 10 of the 86 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.
Files
Environment
Stop when WITNESS_TOKEN or WITNESS_CHAT is unset or empty.
Report single-line failure naming missing variable.
Read bot token from WITNESS_TOKEN and chat id from WITNESS_CHAT.
Treat WITNESS_CHAT as integer chat identifier.
Match format Telegram Bot API expects.
Sources
Build report only from work performed in conversation. Use only steps earlier plugins, skills, and agents actually ran. Report only steps, files, outcomes, and links conversation records. Use only what conversation records.
Scaffolding
Skip every detail about plugin or skill installation. Skip loading, authentication, and invocation steps. Exclude every scaffolding step from report.
Outcome
Focus on key outcome. Pick change delivered, question answered, or artifact produced. Pick verdict reached or blocker hit instead.
Shape
Compose message as single paragraph. Name outcome first, then artifact, then next step. Skip next step when none applies. Keep body plain prose, free of headings, lists, tables, blocks, and rules.
Voice
Write report as personal status update.
Address it from agent to human supervisor.
Open paragraph with salutation, e.g. Boss,.
Phrase every clause in first person with I, me, and my.
Link
Embed current agent run's URL as hyperlink target. Attach it to opening verb. Read URL from environment variable host injects. Omit link when host injects no such variable.
Emoji
Open message with exactly one emoji matching outcome. Pick exactly one from palette below.
👍🏻 ❤️ 🍒 😊 🍓 🧨 👌🏻 🌶Markdown
Use Markdown only for hyperlinks and backticked fixed-width text.
Keep other text plain, free of bold, italics, lists, tables, and blocks.
Embed every relevant URL as hyperlink so user tracks work later.
Set parse_mode to MarkdownV2.
Escape Telegram reserved characters in body.
Leave inline code, link labels, and link URLs untouched.
Length
Keep paragraph under one thousand characters. Keep whole message under four thousand.
Send
Post message once and feed body via stdin.
Feeding via stdin lets backticks and reserved characters survive shell.
Pass disable_web_page_preview=true on every call.
Verify response ok field is true.
Surface description field and stop run when ok is false.
Secrecy
Keep Claude, Anthropic, and every AI agent unnamed in message.
Keep every language model and automation tool unnamed too.
Leave out any generated by line, marketing footer, and AI-disclosure trailer.
Keep value of WITNESS_TOKEN out of every log, print, echo, and file.
Stop after single successful sendMessage call.
Examples
Read four sample reports in examples/ directory first.
Compose paragraph only after reading them.
Example
🍒 Boss, I [walked](https://claude.ai/epitaxy/session_01K9dXyR5MnphYZo6QcZ9trB)
the call graph of `Payment::charge` across the `@foobar/billing` repo and found
three callers that bypass the retry wrapper in `lib/retry.rb`; I opened
[issue #312](https://github.com/foobar/billing/issues/312) describing the gap
and tagged `@yegor` for triage.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.

