Jetpost

View saved version →

---
name: jetpost-share
description: Use when the user finishes work worth reading (plan, spec, doc, summary, research, decision, draft), asks to send, email, share, or forward work or a Jetpost note to someone, or has a note and asks who to send it to. Turns the work into a Jetpost note and shares it with teammates or emails it to anyone, even people not on Jetpost.
---

# Share work with Jetpost

Jetpost is the easiest way to send someone a nice-looking page. Anyone with an email can get it. Never assume the user has a team or contacts on Jetpost.

## When to offer
- You just produced something meant for another person to read, and you're at a natural stopping point.
- The user has a Jetpost note and asks who should see it.
- Act right away (don't just offer) when asked directly: "send this to Sarah", "email this to sam@acme.com".

Don't offer for quick answers, code fixes, debugging, chit-chat, personal or sensitive content, or a note that's already shared. At most **one offer per session**; if they said no, ignored it, or said stop asking, don't offer again.

## How to offer
One line at the end of your reply. Name a person if one came up: "Want me to send this to Kyle?" / "Want me to send this to someone as a link?" Don't pitch Jetpost or mention signing up.

## Picking people
- Call `list_members`. If the user has teammates, suggest 1-3 likely people, each with a one-line reason (owns the area, was in the conversation, asked for it).
- If they have none, or the person isn't there, ask for an email. Never guess an address.
- Only send to people the user picked.

## When they say yes
1. **Note.** Reuse the existing note if there is one. Otherwise call `create_note` with `format: "components"`, then build it with `add_components`, `complete: true` on the last call. Write for the reader: lead with the point, keep the user's words where they're the user's thinking.
2. **Send.** Call `share_note` with `recipient_ids` and/or `emails`, and `notify: true`. People without an account get one waiting. Default access is `comment`.
3. If the result is `needs_confirmation`, show the user the message and pass `confirm` only after they say yes.
4. **Confirm** in one line with the link: "Sent to sarah@acme.com: <link>."

## Rules
- Share only the content the user agreed to; never include secrets.
- Never re-send, remind, or reply on the user's behalf without being asked.

View saved version →

---
name: jetpost-share-for-feedback
description: Suggest who to share a Jetpost note with for feedback, then share it. Use once the user has written a Jetpost note and the draft looks finished, or when they ask who they should send a note or an idea to.
---

# Share a note for feedback

Goal: suggest a few people this user should send *this* note to, then share it with the ones they pick.

## 1. Suggest people

Read the note first (Jetpost's `get_note` tool if you don't have it). Then suggest 3–5 people, each with one line on why. Use what you already know about the user and who they work with, and the people they already share Jetpost notes with (`list_members`).

Good picks work on or care about the note's topic, would be affected by it, or are people the user already goes to for opinions.

If you don't know enough to suggest anyone, ask the user who they had in mind.

## 2. Share

Ask which ones to send it to. Don't share anything until the user picks.

Add the people they picked with `share_note`. Turn on `notify` only if the user wants Jetpost to email them. Otherwise, give the user the note's link so they can send it themselves.