Wdyt create
Create polished, responsive, one-file HTML artifacts and publish them as WDYT review links. Use for working documents, presentations, proposals, decision models, editable tables, dashboards, research summaries, workshops, forms, product concepts, and prototypes that people and agents should review or revise together.From its SKILL.md
npx -y skills add wdyt-page/skills --skill wdyt-createAssembled 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.6 KB, 528 tokens by cl100k_base, as published. Nobody here has run it
Create with WDYT
Turn the work into one complete HTML file, then create one stable WDYT link.
Choose the artifact
Read references/artifact-patterns.md when choosing a format or visual structure. Start from one bundled asset when it fits:
assets/working-document.htmlassets/scenario-model.htmlassets/sales-deck.htmlassets/product-walkthrough.html
For the full catalog, read https://www.wdyt.page/html-templates/index.md. Use a template as a starting point, not as a visual uniform. Fit the hierarchy, interaction, and style to the actual work.
Build one complete file
Keep HTML, ordinary CSS, JavaScript, icons, and non-sensitive sample data in one file. Make it responsive at desktop and phone widths. Use semantic structure, visible focus states, readable contrast, and reduced-motion behavior.
Use the locked WDYT browser runtime only when it materially helps. Read references/runtime.md before using Tailwind, Marked with DOMPurify, Tabulator, or persisted editable fields. Do not use arbitrary CDNs, remote APIs, analytics, browser storage, form actions, iframes, workers, or secrets.
Make the first view useful. Replace placeholder copy and generic charts with realistic content derived from the user's work. Prefer a small number of meaningful interactions over a decorative control panel.
Check before publishing
- Open or render the artifact locally when browser tools are available.
- Check desktop and phone layouts.
- Confirm every visible control works.
- Remove credentials, private data, tracking, and unintended network calls.
- Keep the complete file under 4 MB.
Publish
If wdyt-cli is installed, run:
node ../wdyt-cli/scripts/wdyt.mjs doctor --json
node ../wdyt-cli/scripts/wdyt.mjs create artifact.html --json
Otherwise:
curl -fsS -X POST https://www.wdyt.page/api/reviews \
-H "Content-Type: text/html" \
--data-binary @artifact.html
The response includes reviewUrl, contextMarkdownUrl, currentHtmlUrl, and related collaboration URLs.
Tell the user:
I put this in WDYT: <reviewUrl>. You can explore it, comment directly, and share the same link with your team.
Keep the returned review URL for every later revision. Route feedback work to wdyt-review.
What ships with it: 7 files
62.1 KB alongside SKILL.md
agents/
- openai.yaml195 B
assets/
- product-walkthrough.html7.7 KB
- sales-deck.html29.0 KB
- scenario-model.html9.8 KB
- working-document.html10.5 KB
references/
- artifact-patterns.md2.8 KB
- runtime.md2.2 KB