agentleFS
yegor256yegor256/witness/skills/summarize/SKILL.md

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

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.
  • clawdbotSkill

    openclaw-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

  • clawdbotSkill

    plugin-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-aiSkill

    taskflow-inbox-triage

    Also in 6 projects that use this

  • hkyutongSkill

    node-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-botSkill

    discord-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-botSkill

    openclaw-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

    1. steipete/warelay★ 395ksame name
    2. moltbot/clawdbot★ 395ksame name
    3. openclaw/openclaw★ 395ksame name
    4. steipete/clawdis★ 394ksame name
    5. moltbot/moltbot★ 394ksame name
    6. clawdbot/clawdbot★ 394ksame name
    7. molt-bot/clawdbot★ 391ksame name
    8. spinabot/brigade★ 11ksame name
    9. steipete/summarize★ 6.8ksame name
    10. 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.

  • In this repository2 other files it gives its agents.

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

    Stop when WITNESS_TOKEN or WITNESS_CHAT is unset or empty.

    line 10
  2. Very specific:

    Read bot token from WITNESS_TOKEN and chat id from WITNESS_CHAT.

    line 12
  3. Very specific:

    Treat WITNESS_CHAT as integer chat identifier.

    line 13
  4. Distinctive:

    Use only steps earlier plugins, skills, and agents actually ran.

    line 19
  5. Distinctive:

    Use only what conversation records.

    line 21
  6. Distinctive:

    Keep body plain prose, free of headings, lists, tables, blocks, and rules.

    line 40
  7. Very specific:

    Write report as personal status update.

    line 44
  8. Distinctive:

    Read URL from environment variable host injects.

    line 53
  9. Very specific:

    Use Markdown only for hyperlinks and backticked fixed-width text.

    line 67
  10. Very specific:

    Keep other text plain, free of bold, italics, lists, tables, and blocks.

    line 68
  11. Distinctive:

    Leave inline code, link labels, and link URLs untouched.

    line 72
  12. Distinctive:

    Keep paragraph under one thousand characters.

    line 76
  13. Distinctive:

    Keep whole message under four thousand.

    line 77
  14. Very specific:

    Verify response ok field is true.

    line 84
  15. Very specific:

    Keep Claude, Anthropic, and every AI agent unnamed in message.

    line 89
  16. Very specific:

    Keep every language model and automation tool unnamed too.

    line 90
  17. Very specific:

    Leave out any generated by line, marketing footer, and AI-disclosure trailer.

    line 91
  18. Very specific:

    Keep value of WITNESS_TOKEN out of every log, print, echo, and file.

    line 92
  19. Very specific:

    Stop after single successful sendMessage call.

    line 93
  20. Very specific:

    Read four sample reports in examples/ directory first.

    line 97

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

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.