html-comms ยท Proposal for review
Host generated artifacts and return a link
Build a small Astro app hosted on Cloudflare Pages. Then extend html-comms so it can publish an artifact there and give you its link when it is ready.
The first milestone is one generated HTML document that you can open through a hosted URL.
The intended workflow
- 1. GenerateThe skill creates the HTML artifact.
- 2. PublishThe skill sends it to the hosting setup.
- 3. VerifyThe skill checks that the artifact is available.
- 4. DeliverYou receive the link in the conversation.
If publishing fails, the skill should report the failure and provide the local file. A successful upload alone should not count as a ready artifact.
Keep the first build small
- Establish the hosting app. Create the Astro project, deploy it to Cloudflare Pages, and make one sample HTML artifact accessible at a known URL.
- Add publishing to html-comms. Give the skill a repeatable way to publish a generated file, check the result, and return its URL.
- Test through real use. Generate documents you actually need. Use the results to decide which improvements belong in the next iteration.
An artifact library, search, and a management dashboard can wait. The initial proposal only needs the generate, publish, and open workflow.
Decisions before implementation
| Decision | What needs to be settled |
|---|---|
| Viewer access | Who can open an artifact link, and whether sign-in is required. Privacy remains an open implementation decision. |
| Destination | Which Cloudflare project and hostname will serve the artifacts. |
| Publishing method | How the skill will submit files and authenticate. Choose the smallest method that supports the required access rules. |
| Revisions | Whether revising a document updates its existing URL or creates a new version. |
What a working MVP should prove
- A real request produces an HTML artifact and a working hosted link.
- The intended reader can open the document under the chosen access rules.
- The skill checks availability before reporting the artifact as ready.
- A failed publish leaves you with the local document and a clear explanation.
How this document relates to the skill upgrade
The current html-comms skill produces this local HTML document. You review the proposal and decide whether to implement it. If you choose to proceed, a later version of the skill gains publishing support.
This document does not depend on that upgrade. Astro and Cloudflare Pages are your proposed platform choices. The publishing mechanism and access configuration still need technical verification before implementation.