{"id":39907,"plugin_id":"plugin_asdk_app_6a06f62b2f50819181136d58192063d1","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T12:50:07.837Z","digest":"df6f29600da338a11cca263e44cabd251ef9eda8a61aedd67964d946f402d2cc","against":null,"payload":{"description":"Publish a page, report, dashboard, slide deck, document, portfolio or small web app at a ShipStatic link anyone can open, with no account needed and optional built-in password protection. Use when the user asks to publish something, put it online or get a link others can open. Not for HTML the user only wants to see, download or keep as a file.","included_files":[],"name":"publish-online","skill_md_contents":"---\nname: publish-online\ndescription: Publish a page, report, dashboard, slide deck, document, portfolio or small web app at a ShipStatic link anyone can open, with no account needed and optional built-in password protection. Use when the user asks to publish something, put it online or get a link others can open. Not for HTML the user only wants to see, download or keep as a file.\n---\n\n# Publish online\n\nThe user's own instructions come first. Where they say something different\nfrom this workflow, follow them.\n\nPublish what the user wants online with `deployments_upload`: a report, a\npage, a dashboard, a slide deck, a document, a portfolio or a small web app.\nPublish when the user has asked for it to be online. If they want to see a draft\nfirst, show it and publish when they say so. Publishing needs no account, so\ndon't ask the user to sign in or connect anything first.\n\n## Make the files\n\n- Make it as HTML, with CSS, JavaScript, images and fonts as needed. It runs in\n  the browser. There is no server, so no backend code, database or server-side\n  form handling.\n- Put the start page at `index.html`, at the root of the files you send. Link\n  pages and files to each other with relative paths.\n- A report or a single page can be one `index.html` with its CSS and\n  JavaScript inside it, unless the user wants separate files. Charts and\n  tables can be drawn with inline SVG, HTML and CSS.\n- Send text files (HTML, CSS, JavaScript, JSON, SVG) as plain text. Use\n  `encoding: \"base64\"` only for binary files such as images and fonts.\n- Use only content the user gave you or that you can make yourself. Don't link\n  to images or files at addresses you guessed.\n- Don't publish passwords, keys, government ID numbers, health records or\n  payment card numbers, even behind a password. Offer a version with those\n  left out or replaced by made-up examples.\n\n## Publish\n\n- Send all the files in one upload for each version.\n- If the user wants it private or behind a password, pass `password`. That is\n  ShipStatic's built-in password protection, checked before any file is\n  served. Don't build a password page or script into the HTML. Make up a new\n  password that is hard to guess, unless the user chose one. Never ask for a\n  password the user already uses somewhere else.\n\n## Tell the user\n\nUse what the upload returned:\n\n- The link.\n- Without an account, it stays up for 3 days. Show the claim link too:\n  opening it and signing in keeps it in the user's ShipStatic account.\n- The password, if you set one. A password the user never sees locks them out.\n\nKeep the reply short. The links matter more than a summary of the files.\n\n## When the user wants changes\n\nSomething published doesn't change. To change it, publish again: the user gets\na new link, and the earlier one keeps working until it expires. Say which link\nis the new one, and that the claim link of the version they want to keep is\nthe one to open.\n\n## When to stop or decline\n\n- If the request needs a server (an API, a database, sign-in for the people\n  who open the link), say that ShipStatic publishes static files such as HTML,\n  and offer a static version if one would do the job.\n- If the upload is refused, tell the user what the message says. Fix what you\n  can, for example a file type that isn't allowed or files that are too large,\n  and publish once more.\n\n## With a connected account\n\nIf the user has connected a ShipStatic account, what they publish goes to that\naccount, with no claim link and no 3-day limit. It stays until they delete it,\nunless they asked for it to expire. Bring up an account only when the user asks\nto see or manage what they have published, or to use their own domain.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}