Shareable doc template
Turn scattered notes, links, and decisions into one current page people can revisit.
A good shareable doc does one job: turn scattered information into a polished page people can revisit. The format matters, but the useful part is the thinking behind it. Readers need the context, the recommendation, the proof, and the next step without having to reverse engineer your intent.
Claude can turn notes, links, files, decisions, context, examples, and next steps into a clear first version. Send turns that version into a live page you can share, track, and revise as the conversation changes.
What to include in the shareable doc
- The purpose of the doc and who it is for.
- Context, background, and important links.
- Main content, examples, decisions, or resources.
- Open questions, owners, and dependencies.
- Next steps and how to respond.
Prompt to use in Claude
Search the registry for the Send connector. Once connected, use their "send/shareable-doc" skill.
How to create it with Send
Give Claude notes, links, files, decisions, context, examples, and next steps, plus any constraints, examples, or audience notes that matter. Ask it to create the shareable doc with the Send connector so the output becomes a page instead of another loose document.
After you share it, Send helps you see whether clients, teammates, and stakeholders open it, come back to it, or share it internally. You can update the same link when details change.
Shareable doc structure
Purpose
Why the doc exists and who should read it.
Context
Background, links, references, and assumptions.
Content
Main points, resources, decisions, and examples.
Follow-up
Open questions, owners, next steps, and response path.
Why send a shareable doc as a page
A shareable doc is useful when it stays current and easy to find. Send gives you one link instead of a pile of attachments or copied notes.