Wdyt review
Collaborate through an existing wdyt.page review by reading comments and drawings, downloading current HTML, applying requested changes, replying precisely, waiting for human review, and uploading complete replacement versions to the same link. Use whenever the user provides a WDYT review URL or asks to act on WDYT feedback.From its SKILL.md
npx -y skills add wdyt-page/skills --skill wdyt-reviewAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 24 days oldThe repository was created 24 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.4 KB, 489 tokens by cl100k_base, as published. Nobody here has run it
Review with WDYT
Treat the supplied WDYT link as the shared source of truth. Keep it unchanged.
Start with context
If wdyt-cli is installed:
node ../wdyt-cli/scripts/wdyt.mjs context "<review-url>" --json
For /r/<review-id> links, the direct context is:
https://www.wdyt.page/api/reviews/<review-id>/context.md
The context provides the current version ID, comment threads, drawings, clean editable HTML URL, annotated reference URL, and exact upload URL.
If comments are still being added and the human has not asked you to act, wait. Do not make speculative changes.
Apply feedback
- Download
current.html, not the annotated export. Current HTML includes persisted editable-field values. - Inspect
annotated.htmlonly when pins, drawings, scenes, or spatial placement need interpretation. - Implement the requested changes in the complete HTML document.
- Preserve unrelated behavior and content.
- Check the result locally when browser tools are available.
- Upload the complete replacement to the same review.
With the CLI:
node ../wdyt-cli/scripts/wdyt.mjs download "<review-url>" --output current.html
node ../wdyt-cli/scripts/wdyt.mjs upload "<review-url>" updated.html --json
The CLI automatically sends the current base-version header. If the response reports staleBase: true, tell the human another version arrived while you worked. Both versions are preserved; do not claim they were merged.
Comment and draw
Use comments or drawings when they clarify the collaboration: acknowledge a completed action, ask a precise question, or point to a visual area. Do not add status noise.
node ../wdyt-cli/scripts/wdyt.mjs comment "<review-url>" \
--body "Updated this section; is this the emphasis you wanted?" \
--author "Maya's Agent" --x 420 --y 260 --json
Read references/review-api.md for exact comment, reply, drawing, waiting, and raw API payloads.
Finish clearly
Tell the human the next version is ready at the same link and summarize the meaningful changes briefly. Do not create a second review.
What ships with it: 2 files
2.2 KB alongside SKILL.md
agents/
- openai.yaml203 B
references/
- review-api.md2.0 KB