Draft message

Skill sumitaich1998/jarvisvr/skills/communication/draft-message

An AI agentic operating system for mixed reality on the Meta Quest 3 — your own J.A.R.V.I.S. Multi-agent orchestration, multimodal perception (sight/hearing/gaze), 42 holographic widgets, 20 LLM providers.

Install

npx -y skills add sumitaich1998/jarvisvr --skill draft-message

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 a message, email, or reply in the user's voice and show it for review before anything is sent. Use for "text Sarah that I'm running late", "draft an email to the team", "reply saying yes", or composing a note to someone. Triggers: text, message, email, reply, draft, tell them, send a note, write to.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.8 KB, as published. Nobody here has run it

Draft Message

Compose a clear, appropriately-toned message and present it for the user to review. Drafting is safe; sending is a gated action — never send without an explicit confirmation tap.

Steps

Capture intent: recipient, channel (text/email/chat), key points, and desired tone (casual/formal). Infer tone from the relationship if unstated.
Compose a concise draft in the user's voice. For email include a subject; for chat keep it short.
Render the draft on a panel (show_panel) with the recipient + body so the user can read it back.
Offer to send via a confirmation notification_toast (notify) with Send / Edit / Cancel. Only a confirm_send tap triggers an actual send (integration permitting); otherwise it stays a draft to copy.
Revise on "make it shorter / friendlier" and re-render.

Output

Draft (show_panel → panel):

{ "widget_type": "panel",
  "props": { "title": "Draft → Sarah (text)",
             "body": "Hey Sarah — running ~15 min late, be there soon!",
             "sections": [ { "heading": "To", "text": "Sarah" }, { "heading": "Channel", "text": "SMS" } ] },
  "interactions": ["tap","grab","resize"] }

Send confirmation (notify → notification_toast):

{ "widget_type": "notification_toast",
  "props": { "title": "Send this message?", "body": "To Sarah · SMS", "severity": "info",
             "actions": [ { "id": "confirm_send", "label": "Send" },
                          { "id": "edit", "label": "Edit" }, { "id": "cancel", "label": "Cancel" } ],
             "auto_dismiss_ms": 0 } }

agent.speech: { "text": "Here's a draft to Sarah — want me to send it?", "final": true }

Edge cases

No integration to send → present the draft and say it's ready to copy/send manually; don't claim it was sent.
Missing recipient → ask who (clarify-intent).
Sensitive content (money, commitments) → always confirm; reflect the user's wording, don't overstate.
Wrong tone → revise on request; default to matching the recipient's formality.
Long email → use a document_viewer for very long bodies; keep the panel for short messages.