Goose already writes good HTML: automation reports, data pulls, meeting prep and status pages. 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 Goose never sees.
tossithere fixes that. Goose 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 Goose reads every comment, fixes the page and publishes v2 on the same link.
Set it up
You do this once, in the desktop app and the CLI.
- Install the CLI and sign in:
npm install -g tossithere
toss login
- Install the tossithere skill. Ask Goose:
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 a .goosehints file in your project, or into ~/.config/goose/.goosehints to use them everywhere.
That's it. Goose now knows how to publish, share, read comments and push new versions.
Publish your first page
Ask Goose for something you'd normally get as a wall of text:
Pull last week's support tickets, group them by theme, and publish a page with the top five.
Goose writes the HTML and publishes it:
toss docs:push support-themes.html --json
# -> https://tossithere.com/d/support-themes-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 Goose to share it, or publish straight into a team workspace:
toss docs:share <docId> --visibility public --allow comment
toss docs:push support-themes.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 Goose fix it
Tell Goose: "Read the comments and fix the page." It runs:
toss comments:list <docId> --unresolved --json
toss docs:push support-themes.html --id <docId> --note "what changed"
Every comment arrives with the exact markup it points at, so Goose 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 Goose
- Goose connects to many tools through extensions. Let it gather data from them, then publish one page with the result.
- Recipes that end with a publish step give you a link every time they run.
- Use the same link for a recurring report: push with
--idand each run becomes the next version.