Shihui Web Link Publishing

Problem

When local HTML, courseware, static sites, or frontend build output needs to be shared as a stable URL, sending files is usually not enough. Pages may contain file:///... paths that only work on one machine, multiple unrelated HTML files may share one directory with no clear entry point, and repeated publishing can create duplicate links while the old one becomes stale. This skill turns static-content publishing into a repeatable workflow: create or update a project, return a public URL, and store id, url, and token in .openurl.json for later update, deletion, or listing.

Core Capabilities

• Static hosting only: supports HTML, CSS, JS, images, fonts, PDFs, and .ggb files; React/Vue dist/ or build/ output should be uploaded after build, not source trees or node_modules.
• Create or update: if .openurl.json exists or the same /p// link was already shared, prefer updating the existing project; create a new project only when no record exists or the user explicitly asks for a new link.
• Auth and lifecycle: anonymous publishing requires no account but links usually stop being accessible after 3 days; account publishing supports persistent storage, updates, deletion, and authentication via phone/password, session, or long-lived API Key.
• Pre-publish checks: the script checks for file:/// references, pure redirect pages, and truncated HTML; the service also runs AI safety review on each HTML page and blocks phishing, fake login, credential theft, malicious scripts, or fraudulent redirects.
• Entry constraints: folder publishing should include a root index.html; one link should serve one clear entry point, and unrelated content should be published separately or organized through a navigation page.

Limits and Caveats

It is not suitable for Node/Python backends, SSR, WebSocket services, or server-side persistence. Files are limited to 25 MB, projects to 200 MB or 800 files. Links are public, so sensitive data should not be uploaded. If the user explicitly requests Vercel, Netlify, GitHub Pages, or another platform, this skill should not be used as the default route.