agentsclimarketplace

Write

Skill eliransu/digital-brain/skills/write

Draft text in your voice. Applies the rules from VOICE.md (do/don't list) to anything you will send or publish - Slack messages, DMs, internal emails, external emails, Reddit/LinkedIn posts, replies to inbound messages, or rewrites of existing drafts. Triggers on: "/write", "draft this for me", "rewrite in my voice", "reply to this", "send a slack to X", "email Y about Z", "post about X".From its SKILL.md

Install
npx -y skills add eliransu/digital-brain --skill write

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

4.5 KB, 942 tokens by cl100k_base, as published. Nobody here has run it

write: Draft in your Voice

Whenever you is going to send or publish something, drafts go through VOICE.md. If the user just says "write X" or "draft X" without invoking this skill, still apply VOICE.md.

Style sources

  • ~/digital-brain/VOICE.md - canonical do/don't list.
  • ~/digital-brain/wiki/meta/Voice.md - long reference with examples and registers.
  • ~/digital-brain/wiki/entities/people/_index.md - who knows whom, used to pick language (Hebrew/English) and tone.

Always read VOICE.md before drafting. If the draft is short, the rules are still binding.

Surfaces

InvocationSurface
/write <free text>Infer surface from content. If ambiguous, ask.
/write slack <message>Slack public channel.
/write dm <name> <message>Slack DM. Hebrew if recipient is Israeli, English otherwise.
/write email <recipient> <topic>Email. Infer internal vs external from recipient domain.
/write post <topic>Long-form public (Reddit, LinkedIn, blog).
/write reply <pasted> <intent>Reply matching the surface of the pasted message.
/write rewrite <pasted draft>Rewrite an existing draft to comply with VOICE.md.

If empty $ARGUMENTS, list the seven forms and ask.

Workflow

  1. Read ~/digital-brain/VOICE.md. Re-read every invocation. Rules evolve.
  2. Identify the surface (see table). If ambiguous, ask one short question.
  3. If a name was given, look up the person in wiki/entities/people/_index.md to set tone. All output is English regardless of recipient.
  4. Draft.
  5. Self-check against the don'ts in VOICE.md. The high-frequency ones:
    • Em-dashes (replace with hyphens, commas, parentheses, or a new sentence).
    • Emojis in drafted output (drop them).
    • Parallel constructions, three-beat rhythms, "not X but Y" patterns (rephrase plain).
    • Marketing verbs and hollow superlatives (delete or replace with a concrete verb).
    • Fake intimacy openers, self-dialogue, heavy connectives, tagline closers (delete).
    • "things"/"stuff"/"lots"/"many" where a concrete number or name exists (replace).
    • Title in email signature (remove).
    • "Dear team", "Hope this finds you well" (rewrite opener).
  6. Show only the final draft. Do not preface with "Here is your draft" or similar. Do not narrate the rules applied unless asked.

Surface notes

Slack public. Lowercase fine, terse, optional fyi closer, @-tag the smallest set who can act. Status broadcasts go verb-first. Backticks for env names, payloads, ticket IDs.

Slack DM. English regardless of recipient. Sequential one-liners for instructions, not paragraphs. No Hebrew slang or transliterations in drafted output.

Internal email. "Hi Name," opener, listy when there are multiple items, sign "you" with no title. For forwarding: "Hi team. Please see the message below and let me know if you want me to connect. the user".

External email. "Hi Name," opener. Acknowledge their move, position Your Organization, then ask. Sign "Best regards, you".

Long-form public. Finding-first, concrete numbers, plain prose. Bury self-promo mid-post. Close with reader agency, not a tagline.

Reply. Match the surface and length of the pasted message. Reply is always English even if the inbound was Hebrew.

Rewrite. Keep the user's intent and facts. Strip every rule in the don't list. Show before and after only if the user asks; otherwise show only the rewrite.

Don'ts for this skill itself

  • Do not add commentary, preface, or postscript to the draft.
  • Do not narrate which rules were applied unless asked.
  • Do not switch register unless the user changes the invocation.
  • Do not invent facts, numbers, or quotes you has not said.
  • Do not over-pad short asks. A two-line ask stays two lines.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most docs writing skills give in 942 tokens

Counted across 1,951 of the 3,904 authors here whose files we hold, read 2026-09-06

  • Use third-person for skill descriptionsin 54 of 1951, across 35 files
  • Start descriptions with Use whenin 43 of 1951, across 29 files
  • Run baseline scenarios before writing any skillin 40 of 1951, across 26 files
  • Use active voicein 40 of 1951, across 36 files
  • Map file responsibilities before defining tasksin 36 of 1951, across 29 files
  • Use checkbox syntax for tracking stepsin 35 of 1951, across 27 files
  • Ask one question at a timein 35 of 1951
  • Offer execution options after saving the planin 33 of 1951, across 24 files
  • Include complete code in every stepin 33 of 1951, across 27 files
  • Design units with clear boundaries and interfacesin 31 of 1951, across 23 files
  • Announce the skill usage at the startin 30 of 1951
  • Verify agent compliance after adding the skillin 29 of 1951, across 17 files

Said here and by no other author read

  • Identify the communication surface
  • Look up recipient details for tone
  • Draft content in English
  • Self-check draft against VOICE.md prohibitions
  • Show only the final draft
  • Use verb-first for status broadcasts

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 611,811. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.