Turn a workflow you just ran with the AI (a prompt, or a few prompts in a row, that take some input and produce a result) into a single web page anyone can open and use, with no account and no API key
Goal: the workflow the user just ran with you becomes a link that works for anyone: they open it, fill in the input, press Run, and get the same kind of result. Visitors need no account. The page runs on a small free daily AI allowance that the page carries with it.
Everything happens through share.py in this skill's folder (Python 3, standard library). <skill> below means this skill's folder.
From the conversation, write down in 3–6 lines and show the user:
Ask the user to confirm or correct. Also ask what language the page should be in if it is not obvious.
Do not build pages that ask for passwords, payment or card details, one-time codes, or pretend to be another company or person. Do not put private data from the conversation (names, emails, internal numbers) into prompts or examples; use made-up examples.
In the user's current folder. Shape:
{
"title": "Meeting notes → follow-up email",
"description": "Paste rough notes from a meeting. Get the decisions, owners, and a short follow-up email.",
"inputs": [
{"id": "notes", "label": "Your meeting notes", "type": "textarea", "placeholder": "Messy is fine…"},
{"id": "tone", "label": "Tone", "type": "select", "options": ["Friendly", "Formal"]}
],
"steps": [
{"id": "facts", "prompt": "List the decisions, action items (owner — task — due date) and open questions. Use only what the notes say. Plain text, no Markdown.", "input": "{{notes}}", "show": true, "label": "What was decided"},
{"id": "email", "prompt": "Write a follow-up email in a {{tone}} tone, under 150 words. Plain text, no Markdown.", "input": "{{facts}}", "show": true, "label": "Follow-up email"}
],
"examples": [{"label": "Product sync", "values": {"notes": "launch moved to dec 2 bc payments bug. raj fixes bug by fri…", "tone": "Friendly"}}]
}
Rules:
type: textarea (default), text, or select (needs options). Inputs are required unless "required": false.{{id}} in prompt, system or input is replaced by an input or an earlier step's answer. Put the visitor's text in input, the instruction in prompt; an optional system sets role and rules.show: true prints that step. Hidden steps are fine for intermediate work. The last shown step streams.maxTokens per step, default 800 (the page's limit too).bold shows up as asterisks. End every shown step's prompt with "Plain text, no Markdown." and use simple dashes for lists.python3 <skill>/share.py check workflow.json
python3 <skill>/share.py try workflow.json # runs example 1 through the real AI, prints every step
Read the output as a stranger would. If a step is vague, wrong, or too long, fix the prompt and run try again. Show the user the final output of the example before publishing.
python3 <skill>/share.py build workflow.json page.html
python3 <skill>/share.py publish page.html
publish prints the public link. It saves the page id and a private edit token in .go-public.json (and adds it to .gitignore in a git repo). Tell the user:
.go-public.json is what lets them change or remove the page later, so keep it and do not share it.Do not hand-edit page.html: change workflow.json and build again.
Edit workflow.json, then build and publish again in the same folder: same link, new content. python3 <skill>/share.py delete takes it down.
publish). When a busy page runs out, it says so and works again the next day.claim_url in .go-public.json lets them claim the page. They enter an email, confirm it from their inbox, and the page then runs on that account's own allowance. Mention this only when they ask or the allowance runs out. The small "Made with OneTag · Report" mark stays on every page.Weekly roundup of top Claude Code skills, MCP servers, and AI coding tips.