Skip to main content
prompt CX Codex GP ChatGPT

delivery-contract.proactive — Claude Code prompt: setup and install

The delivery-contract.proactive Claude Code prompt sets rules for sending updates and final replies through SkyDot. It applies when configuring Proactive mode to distinguish progress messages from the final answer.

MIT ★ 189 updated 2026-11-16

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/commands/delivery-contract.proactive.md
Open on GitHub

What delivery-contract.proactive does

The prompt defines how Proactive mode delivers user-facing messages: they go through mcp__skydot__send_message, not the SDK’s ordinary final text. Use the progress role for interim updates and final for the last substantive reply.

Each successful call sends a separate message; progress does not merge with the final reply. Use send_image or send_file for artifacts. A delivery error must not be routed through another channel. The SkyDot tools, including mcp__skydot__send_message, are required.

What it helps with

  • send progress updates and the final answer as separate messages
  • mark the last substantive message with the final role
  • deliver images and files through SkyDot tools
  • avoid repeating content already sent to the user

Example prompts for the agent

  • Configure Proactive mode to send updates with mcp__skydot__send_message as progress and the result as final.
  • Set rules for delivering images and files in Proactive mode.
  • Send the acknowledgement and final result as separate SkyDot messages.

How to install delivery-contract.proactive

Manually: put the files in place

.claude/commands/delivery-contract.proactive.md

Questions about delivery-contract.proactive

How do I install delivery-contract.proactive in Claude Code?

Place the prompt file at .claude/commands/delivery-contract.proactive.md.

What does delivery-contract.proactive do?

It sets message-delivery rules for Proactive mode. Interim updates and final replies use separate roles, while images and files go through dedicated delivery tools.

What does delivery-contract.proactive need to work?

It requires the SkyDot tools, including mcp__skydot__send_message; send_file and send_image handle file and image delivery.

Source text

delivery-contract.proactive.md · MIT
## Proactive reply mode

The current Workspace uses **Proactive mode**. This is a delivery contract,
not an identity or personality instruction.

- The framework does not publish your ordinary final SDK Assistant text.
- `mcp__skydot__send_message` is the only way for you to say something
  visible to the user. Framework-owned system and failure notices are separate.
- Each successful call immediately sends one independent message. You may send
  zero, one, or many messages during a turn, and may continue reasoning or using
  tools after every send.
- Set `delivery_role=progress` on acknowledgements and interim updates. Set
  `delivery_role=final` on the last substantive answer. The role does not merge
  messages in Proactive mode; it gives the delivery-recovery layer an exact
  completion signal so it can avoid both missing and duplicate final replies.
- Never label a complete answer as `progress`. If a message contains the
  conclusion, result, confirmation phrase, final status, or next actions the
  user needs, it is `final` even if you may continue internal housekeeping
  afterwards. After a successful `progress` call, you must make a successful
  `final` call before ending unless the turn intentionally has no final answer.
- Decide when speaking is useful. A natural pattern for longer work is to
  acknowledge the request, work, share a meaningful update, continue working,
  and then send the result. Do not create noisy status messages without value.
- `delivery_role` does not combine proactive messages: every call is delivered
  separately using the current channel's native conversational presentation.
- For ordinary conversation, use `send_message`. Do not route around a delivery
  error with a card tool or raw channel API, and do not sleep and retry. The
  framework owns user-visible delivery-failure notices.
- Never place user-visible content only in the final SDK text. After the last
  useful `send_message(delivery_role=final)`, end the internal turn immediately.
  Do not produce an SDK-final acknowledgement, summary, completion phrase,
  invitation, or any repetition of the delivered messages.
- Use `send_image` or `send_file` for artifacts. They deliver to the native
  message address and bot account already validated for the current turn —
  never guess or rewrite the target id. Their success response is the delivery
  acknowledgement; never claim delivery after a tool error.

© 2SinceJuly · MIT · 2SinceJuly/SkyDot

Similar prompts

All prompts for Agent setup: memory, context, orchestration →

From the same set3

Project sponsors

Companies that keep this analytics open