Amp already writes good HTML: refactor plans, investigation notes, dependency audits and postmortems. 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 Amp never sees.
tossithere fixes that. Amp 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 Amp reads every comment, fixes the page and publishes v2 on the same link.
Set it up
You do this once, in the terminal and your editor.
- Install the CLI and sign in:
npm install -g tossithere
toss login
- Install the tossithere skill. Ask Amp:
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 at the root of your repository. Amp reads it at the start of every thread.
That's it. Amp now knows how to publish, share, read comments and push new versions.
Publish your first page
Ask Amp for something you'd normally get as a wall of text:
Audit our dependencies for anything unmaintained and publish a page with what to replace.
Amp writes the HTML and publishes it:
toss docs:push dependency-audit.html --json
# -> https://tossithere.com/d/dependency-audit-8fa2
The 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 Amp to share it, or publish straight into a team workspace:
toss docs:share <docId> --visibility public --allow comment
toss docs:push dependency-audit.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 Amp fix it
Tell Amp: "Read the comments and fix the page." It runs:
toss comments:list <docId> --unresolved --json
toss docs:push dependency-audit.html --id <docId> --note "what changed"
Every comment arrives with the exact markup it points at, so Amp 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 Amp
- Amp threads are shareable, but the result often belongs on its own page. Publishing gives reviewers something to comment on line by line.
- Subagents can each publish a page. Ask the main thread to collect the links.
- Because
AGENTS.mdis a shared format, the same instructions work for teammates on other agents.