Warp already writes good HTML: incident timelines, log analyses, runbooks and infrastructure reports. The hard part is what happens next. A file on your laptop doesn't open properly on a phone, and feedback ends up in a chat thread that Warp never sees.
tossithere fixes that. Warp runs one command, and the HTML is live at a private link that opens anywhere. People comment on the exact element or sentence they mean, and Warp reads every comment, fixes the page and publishes v2 on the same link.
Set it up
You do this once, in Warp's agent mode.
- Install the CLI and sign in:
npm install -g tossithere
toss login- Install the tossithere skill. Ask Warp:
Install the tossithere skill from https://tossithere.com/skill.md and use it whenever you make HTML for me.
Prefer to keep it in the repository? Copy the instructions from this page instead. Paste the instructions into AGENTS.md (or WARP.md) at the root of your project, or save them as a rule in Warp so every agent conversation has them.
That's it. Warp now knows how to publish, share, read comments and push new versions.
Publish your first page
Ask Warp for something you'd normally get as a wall of text:
Read the last hour of the API logs, find what caused the 500s, and publish an incident page.
Warp writes the HTML and publishes it:
toss docs:push incident-api-500s.html --json
# -> https://tossithere.com/d/incident-api-500s-8fa2The page is private to you. Open it on your laptop or your phone.
Share it and collect comments
When someone else should see it, ask Warp to share it, or publish straight into a team workspace:
toss docs:share <docId> --visibility public --allow comment
toss docs:push incident-api-500s.html --team <slug>Reading needs no account. Commenting takes a Google sign-in, so every comment has a name on it. Reviewers click any element or highlight any text and type.
Let Warp fix it
Tell Warp: "Read the comments and fix the page." It runs:
toss comments:list <docId> --unresolved --json
toss docs:push incident-api-500s.html --id <docId> --note "what changed"Every comment arrives with the exact markup it points at, so Warp edits the right line instead of guessing. The new version goes to the same link, and older versions stay readable with their own comments.
Tips for Warp
- Warp's agent lives in the terminal, so publishing is the most natural step: it already runs the commands.
- Incident pages are a good fit. Teammates comment on the timeline, and the agent updates the same link as you learn more.
- Save the instructions as a Warp rule to use them outside a repository.
