{"id":94850,"plugin_id":"plugin_asdk_app_6ac4a55535548191baa5b230057d5b0e","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-13T12:12:30.368Z","digest":"35191cae45afe5f2022ac7da15a19862fa3a5835af2fcc46d7ec55b9b451170e","against":null,"payload":{"description":"Publish a UiChemy project as a fast Astro site in the user's own Cloudflare account on a free workers.dev address, with or without the EmDash CMS, then check, update or take it down. Use when the user asks for Cloudflare, workers.dev, EmDash, a site a client can edit in a CMS, or to host on their own Cloudflare. For a UiChemy-hosted link use publish-live-site.","included_files":[],"name":"publish-to-cloudflare","skill_md_contents":"---\nname: publish-to-cloudflare\ndescription: Publish a UiChemy project as a fast Astro site in the user's own Cloudflare account on a free workers.dev address, with or without the EmDash CMS, then check, update or take it down. Use when the user asks for Cloudflare, workers.dev, EmDash, a site a client can edit in a CMS, or to host on their own Cloudflare. For a UiChemy-hosted link use publish-live-site.\n---\n\nUse this skill when the user wants the site on their own Cloudflare account.\n\nSteps:\n1. Identify the project with `uichemy_list_projects` if the user did not name it. Run `uichemy_validate` and offer to fix faults first.\n2. Ask what to publish, in plain words:\n   - Astro with EmDash: the site comes with an editable admin area so the user or their client can change text, images, pages and blog posts. It is required if the site has a blog.\n   - Astro frontend: static pages only.\n3. Say: \"I will publish this project to your own Cloudflare account.\" Wait for a clear yes. For Astro with EmDash call `uichemy_publish_emdash` (if it returns a jobId, check it with `uichemy_emdash_status`). For the Astro frontend call `uichemy_deploy_to_cloudflare`.\n4. The first time, the user must connect their Cloudflare account on Cloudflare's sign-in screen and approve every permission it shows. Give them the link the tool returns and wait. Never ask for a Cloudflare password or token in the chat.\n5. Report the live address and status only from what the tool returns. For EmDash sites, the admin area is locked behind a one-time setup link after the first publish: get it with `uichemy_open_cms_admin` and give it only to the user. After setup the admin is at the site address followed by `/_emdash/admin` and signs in with a passkey (Touch ID, Windows Hello or their phone).\n6. To update after design changes, call the same tool again. EmDash updates keep the CMS content and users.\n7. For an Astro frontend site, `uichemy_site_versions` lists every published version, and `uichemy_restore_site_version` puts an earlier one back online. Name the version and wait for a clear yes before restoring.\n8. To take the site down, name it, ask for confirmation, then call `uichemy_unpublish_cloudflare`. For EmDash it keeps the CMS content by default. Only pass `deleteData` after the user clearly agrees that the CMS content and logins will be deleted for good.\n\nRules:\n- The site lives in the user's own Cloudflare account. Cloudflare's own limits and charges apply; a free workers.dev address is not a promise of unlimited hosting.\n- Custom domains are not available through this plugin. Say so if asked.\n- If the tool says Cloudflare publishing is not available, offer `export-astro-project` instead.\n- Do not describe prices or plans. If the account cannot publish, say that and link https://app.uichemy.com/support.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}