For people working with agents

Install once.
Use when it helps.

wdyt gives people and agents one shared page for the work, exact feedback, and every revision. The toolkit teaches your agent when that surface is useful, then routes it to one focused workflow instead of stuffing the whole playbook into every chat.

1. Give your agent the landing-page setup prompt

The copied prompt is permission to install the official toolkit. Your agent should install it, verify the inventory, and tell you whether a restart is needed. It should never call a hosted web read an installation.

npx --yes skills add wdyt-page/skills -y
npx --yes skills list --json

2. Let one-line skill descriptions do the day-to-day routing

wdyt should appear for reviewable work—not every answer.

wdytRecognize a useful wdyt moment and route to the smallest relevant workflow.

wdyt-createCreate and share documents, strategies, roadmaps, decks, models, dashboards, and prototypes.

wdyt-reviewRead comments and drawings, implement feedback, and publish the next version to the same link.

wdyt-live-reviewCollect precise feedback on a real website through the wdyt Chrome extension.

wdyt-collaborateComment, reply, draw, wait, and coordinate people and agents on one shared page.

wdyt-accessConnect authenticated MCP for history, workspace/private pages, invitations, and access management.

wdyt-cliDiagnose and run deterministic public-link operations from an agent shell.

3. Start free, without an account

Ask for a strategy, roadmap, working document, sales deck, model, dashboard, prototype, or other artifact you want people to react to. The agent creates one complete HTML file, publishes it, and returns the stable review link. Anyone with that link can comment.

Create a decision-ready launch strategy in wdyt so I can comment and share it.

Turn this sales narrative into a concise wdyt deck for customer feedback.

Make an interactive comparison in wdyt, then give me the review link.

4. Keep the first attempt alive when the agent's network is blocked

The agent should return the finished HTML file rather than discarding the work or telling you to run curl. Open the no-account browser publisher, choose the file, and continue in wdyt.

Publish an agent-made HTML file →

5. Connect MCP only when the account adds value

Authenticated MCP is for page history, owned workspace/private pages, invitations, collaborators, and giving the agent access to pages shared with your account. It is not required for a first public link. Use the exact instructions for Codex, Claude Code, Conductor, Cursor, VS Code/Copilot, or OpenClaw.

Open platform-specific MCP setup →

6. Bring feedback back to the agent

Give the same clean wdyt link to the agent. It reads comments and drawings, changes the current artifact or the real product code, and publishes the next version without breaking the link.

Read the feedback on this wdyt page, implement it, and publish the next version to the same link: https://www.wdyt.page/r/<page-key>