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

deliver

Skill1 starsChanged 6 days agoMITView on GitHub

Use this skill when the user wants to deliver a ready-to-send text artifact verbatim to a Telegram chat.

29 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use prune, create-issue 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.
  • matthewpSkill

    prune

    Find and remove unused CSS in a Tideway project — classes defined in stylesheets but never referenced in markup. Use whenever the user wants to prune dead CSS, find unused styles or classes, clean up or slim a stylesheet, find orphaned BEM classes, or "tree-shake" hand-written CSS.

    Also in 3 projects that use this

  • sahinSkill

    create-issue

    Also in 3 projects that use this

  • BlockSkill

    plan

    Draft a TDD, PRD, or lightweight plan in the conversation without committing it.

    Also in 5 projects that use this

  • SentrySkill

    spec

    Produce a verified spec — problem, desired outcome, and acceptance criteria — before building. Use when given a GitHub/Linear issue link, when starting from a fuzzy in-conversation idea, or asked to "figure out what to do" / "scope this" / "what should I build" — whenever the *what* isn't yet pinned down. Grills the ambiguities, checks the premise against the code, and produces acceptance criteria you sign off on — then hands to design-first.

    Also in 4 projects that use this

  • AWSSkill

    ship

    Finalize dev work on an issue branch — update docs, push, and open a PR.

    Also in 5 projects that use this

  • AWSSkill

    wait-what

    Stop. That last message did not land: re-pitch it.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

11 rules. 0 are common, 3 are distinctive, and 8 are very specific to this project.

  • 0

    Common

    Most of the 29 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 8

    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:

    Stop when supplied text artifact is missing, empty, or only whitespace.

    line 23
  5. Distinctive:

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

    line 29
  6. Distinctive:

    Stop when supplied text exceeds four thousand characters.

    line 33
  7. Very specific:

    Verify response ok field is true.

    line 41
  8. Very specific:

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

    line 46
  9. Very specific:

    Keep every language model and automation tool unnamed too.

    line 47
  10. Very specific:

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

    line 48
  11. Very specific:

    Stop after single successful sendMessage call.

    line 49

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

Body

Take message body verbatim from supplied text artifact. Previous plugin, skill, or agent hands it in. Preserve supplied text word for word, its wording and length intact. Preserve its order and language, with nothing prepended or appended. Apply no transformation beyond MarkdownV2 escaping Telegram requires. Stop when supplied text artifact is missing, empty, or only whitespace.

Escaping

Set parse_mode to MarkdownV2. Escape Telegram reserved characters in body. Leave inline code, link labels, and link URLs untouched.

Length

Stop when supplied text exceeds four thousand characters. Report actual length and cap.

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. Keep value of WITNESS_TOKEN out of every log, print, echo, and file. Stop after single successful sendMessage call.

Example

WITNESS_CHAT=-1001234567890
Supplied artifact (verbatim):
  Talk accepted! See you at JPoint 2026 in Moscow on 2026-04-09.

Body after MarkdownV2 escaping (fed via stdin):
  Talk accepted\! See you at JPoint 2026 in Moscow on 2026\-04\-09\.

POST https://api.telegram.org/bot<WITNESS_TOKEN>/sendMessage
  chat_id=-1001234567890
  parse_mode=MarkdownV2
  disable_web_page_preview=true

Response: {"ok":true,"result":{"message_id":4471}}
Stop after this single successful call.

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.