Build Walkthrough

Readout
Skill Build

Updated: July 2, 2026· Version 1

How the readout skill came to be: an MDX-authored successor to the artifact skill whose documents are published to readout.ssscribe.app, where teammates leave anchored comments the agent reads back into the session.

01What it is

Artifact v2, rebuilt around sharing instead of local files.

02Architecture

One PocketBase does three jobs: static host, comments API, version store.

flowchart LR
A[agent writes slug.mdx] --> B[compile.mjs
MDX to themed HTML]
B --> C[publish.mjs]
C -->|rsync| D[PocketBase pb_public
readout.ssscribe.app]
C -->|POST version + mdx| E[(readout_versions)]
F[reviewer browser] -->|anchored pins| G[(readout_comments)]
G -->|read-comments.mjs| A
Info

Comments need no keys or injected config — the widget talks to its own origin and no-ops when the page is opened from disk.

Success

Anchors are compile-time (data-anchor per section/block), so threads survive republishing as long as section titles are stable.

Warning

Comment posting is public-with-the-link; field length limits and superuser-only deletes are the whole moderation story for now.

03What replaced what

v1 conventions carried over where they earned it; the rest moved server-side.

v1 (artifact)v2 (readout)
hand-written HTML with class vocabularyMDX + JSX components, compiled
local git repo as version historyreadout_versions collection (full MDX snapshot per publish)
file:// as a design constraintserver-first; local open still works incidentally
share by sending a fileshare a URL; comments come back to the agent

04Try the comments

This section exists so you can test the loop.

Hover any block on this page and click the pin. Leave a comment — then in a Claude session run the reader and it will show up, anchored to this section as s-try-the-comments.

Bash
node ~/.claude/skills/readout/scripts/read-comments.mjs claude-skills/readout-skill-build