proposal-trackerlisted

# Proposal Tracker The DocSend move, agent-native: publish the proposal as a live tracked page, then answer the question every sender actually has — "is it getting read?" — with view data instead of silence. Follow the shared flow in the root `SKILL.md`. Proposals are maximally client-facing: approval gate always on, and double-check pricing numbers at the gate. ## When to use - The user has a proposal, quote, offer, statement of work, or pitch to send to a specific recipient - The user asks about engagement on something already sent ("did they open it?") → go straight to `get_analytics` ## Steps 1. **Confirm the essentials before authoring.** Recipient (company/person), the offer's core numbers (price, timeline, scope), and the desired next step (call booked? signature? reply?). A proposal without an explicit next step is a brochure. 2. **Structure for a skimming decision-maker.** One-line summary of the offer up top; the "why us / why now" in one short section; scope and pricing in scannable tables; the call to action visible without scrolling far. Long context goes in an appendix. 3. **Author + lint + approval gate.** At the gate, read back the price, timeline, and scope numbers explicitly — a typo in a published price is the worst failure mode this skill has. Note too that the page carries a small "Published with ReportRoom" footer credit the recipient will see. 4. **Publish** with a clean slug. Return the URL and remind the user the link is tracked. When a proposal