Skip to content
artifact.guru

Use case

Internal updates people open, read and act on.

Publish the weekly update, the launch brief or the incident review as a page only your team can open. People filter it to what concerns them, and you can see who has read it.

Who it’s for: Team leads, chiefs of staff, product and engineering managers

artifact.guru/tessel/week-40PrivateFull screen
Tessel week 40. The weekly update from product and engineering, covering what shipped and what needs deciding.A sample. The company and its numbers are made up.
  1. Filter to Mobile to see just that team.
  2. Turn on “Only what changed since week 39”.
  3. Hover the latency chart to read any week’s number.

Why updates get skipped

The weekly update is usually a long message in a busy channel, or an email nobody scrolls through. People read the first two lines and miss the risk in paragraph six. On Thursday you find out nobody saw the decision you needed.

A page can be read in pieces. Tessel’s product and engineering update above lets the mobile team filter to its own items, or hide everything that hasn’t changed since last week.

A weekly rhythm

  1. Let the agent draft it

    Give it the week’s closed tickets, metrics and standup notes. Ask for the same layout as last week, so people know where to look.

  2. Publish it to the team

    In a team workspace, Private means everyone in the workspace can open it, and nobody else.

  3. Post the link where people talk

    A private link pasted into Slack shows a plain card with no title, so nothing leaks into a channel with guests.

  4. Check who read it

    Views lists each teammate who opened it and when. Then you can nudge the two people whose decision is due instead of the whole channel.

Updates that work as pages

UpdateWhat the page adds
Weekly or monthly updateFilters by team, changes since last time, metric charts
Launch briefTimeline, owners, a checklist with progress
Incident reviewA timeline you can step through, with the fix and follow-ups
All-hands notesThe slides, the numbers and the Q&A in one place
Onboarding guideA path through the first week, with links to every document

Every week in one place

Publish each week as its own artifact in an Updates project, and you can find any of them by what’s inside. Search for “when did we ship live ETAs?” and you get the week it happened. Or keep one living link that always shows this week, with past weeks in its version history.

Limits

  • There are no comments or reactions on the page. Discussion stays in your chat tool, with the link at the top of the thread.
  • Views counts people who opened the link, not how far they read.

Prompt

Make your own

Have these ready, then paste the prompt into your agent:

  • This week’s shipped work
  • Metrics with last week’s values
  • Risks with owners
  • Decisions needed, with due dates
Prompt
Write this week’s team update as one self-contained HTML page, in the same
layout as last week’s (attached). Lead with a three-line summary. Then:
shipped, metrics with sparklines and week-over-week change, risks with status
and owner (expandable), decisions needed with owner and due date, and people
news. Add a team filter and a toggle that shows only what changed since last
week. Keep it calm and scannable.

Publish it privately to artifact.guru in the Updates project and give me the
link.

Common questions

Can people outside the workspace see it?

Not while it’s Private. To include someone outside, share that one update with their email address.

Can I see who hasn’t read it?

Views lists who opened a Private link. On an Email link it also lists the invited people who haven’t opened it yet.

Read next

Share safelyHow to know if someone opened your link, and whoEvery link counts its views, and links that need sign-in also show names. This covers where to look, what each number means and what a view can’t tell you.6 min readClient work and documentsHow to update a page you’ve shared without sending a new linkWhat readers see when you change a page you’ve shared, and how to make a focused edit. It also covers who changed what, rolling back, and replacing PDFs and decks.6 min readShare safelyChoose who can open your link, document by documentHow to pick a sharing mode for a proposal, a board pack or a launch page, and what each mode shows the reader and you.8 min read

More use cases

ProposalClient proposalsPublish a proposal as a page made for one client. The price and timeline change as they pick a package, and they approve it in the same place. On an Email link, you see when they opened it.See how EstimateEstimatesTurn a spreadsheet estimate into a page where the client switches parts of the scope on and off, and the price range and timeline change with them. When they ask “what if we skip Android?”, the page already has the answer.See how Website draftWebsite draftsPublish the draft site with its real content and send one link. The client reads the copy where it will live and taps through it on their phone. Each revision shows up at the same address.See how

Try it with your own file

Copy the prompt above, add your file and publish.

Start freeConnect your agent