Share HTML from Codex or Claude Code with an agent skill

AI coding agents are excellent at making the first useful version of a webpage. They can produce a project dashboard, a client-ready report, a landing page mockup, or a visual explanation as a single HTML file. The last mile is usually less elegant: someone needs to open the file and see the rendered result.

The ViewHTML Share Skill gives an agent a focused handoff workflow. Instead of treating a quick HTML artifact like a full production deployment, it checks that the file is suitable for public sharing, sends it to ViewHTML, verifies the resulting preview page, and returns a shareable link.

What the ViewHTML Share Skill is for

Use the skill when the work is already a self-contained HTML file and the next task is simply to let a teammate, client, or reviewer open it in a browser. It is a good fit for temporary prototypes, generated reports, design handoffs, interactive mockups, and HTML artifacts created in a coding session.

• A standalone index.html generated by Codex, Claude Code, Cursor, or another agent
• A small prototype that needs feedback before it becomes a real product page
• A rendered report or dashboard that is easier to review as a link than as source code
• A browser-ready HTML file where images, CSS, and scripts are already inline or publicly hosted

It is not a substitute for a real deployment. If the page depends on a backend, private APIs, a login session, a build pipeline, local assets, or a custom domain, deploy the project through its normal hosting workflow instead.

Install the skill

The skill is published as a public npx skills package. Install it globally for Codex with:

npx skills add Enivel/viewhtml-share-skill -g -y -a codex

The same repository works with other supported coding agents. Change the agent target, or omit the global flag when the skill should live only inside the current project.

Ask your agent to share a page

Once installed, be explicit about the file and the fact that the result is meant to be public. A good request removes the two risky assumptions: which artifact to upload and whether it is safe to share.

Use $viewhtml-share to publish /absolute/path/to/index.html.
Check that it contains no private data, then return the public preview link.

The skill expects a single HTML file smaller than 2 MB. Relative files such as ./chart.png or ./styles.css are not uploaded with it, so use inline assets or public HTTPS URLs before sharing.

Keep public previews deliberate

A ViewHTML share link is public and does not expire automatically. Before asking an agent to publish, remove API keys, access tokens, customer data, internal URLs, local paths, private prompts, and accidental notes from the source file. Check the live preview as well: a page can look fine on your machine while still depending on a local image or browser session that nobody else can access.

For a prototype or review artifact, that small check is usually enough. For durable product pages and anything sensitive, use the hosting and access controls designed for the job.

A smaller handoff loop

The useful pattern is simple: generate the HTML, preview it, publish the rendered result, and send one normal link. ViewHTML handles the preview link; the Share Skill makes that workflow available from the same agent that created the page.