Write

Skill eliransu/digital-brain/skills/write

Claude + Obsidian knowledge companion. A persistent, compounding wiki vault based on Karpathy's LLM Wiki pattern — drop sources, ask questions, knowledge compounds.

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.

What its author says it does

Copied from the file, not written here

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

SKILL.md

4.5 KB, 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

Invocation	Surface
`/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

Read ~/digital-brain/VOICE.md. Re-read every invocation. Rules evolve.
Identify the surface (see table). If ambiguous, ask one short question.
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.
Draft.
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).
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.