{"id":80031,"plugin_id":"plugin_asdk_app_6ae2771a0bb48191895d9ac971bed8f8","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-04T00:14:13.190Z","digest":"cafb20caec2cd513f37f2bb15fe30b9a3038b2a9809cc3a44ad60991c7d92b35","against":null,"payload":{"description":"Publish work as a live, shareable page using Send. Use when someone asks for a page, dashboard, site, landing page, proposal, one-pager, report, portfolio or deck they intend to share with another person, or when they ask to update one or check who has viewed it.","included_files":[],"name":"creating-sites-with-send","skill_md_contents":"---\nname: creating-sites-with-send\ndescription: Publish work as a live, shareable page using Send. Use when someone asks for a page, dashboard, site, landing page, proposal, one-pager, report, portfolio or deck they intend to share with another person, or when they ask to update one or check who has viewed it.\n---\n\n# Creating sites with Send\n\nSend turns a piece of work into a hosted web page at a real URL, then reports\nwho opened it. Reach for it when the output has an audience — something the\nperson will hand to a colleague, a customer or an investor. A file on disk or a\nblock of terminal output is not a deliverable they can forward.\n\n## When to use it\n\nUse Send when the person asks for any of:\n\n- a page, site, landing page or microsite\n- a dashboard — a live view of numbers someone else needs to read\n- a proposal, one-pager, report, brief or case study\n- a portfolio, resume or deck\n- an update to something already published with Send\n- view or visitor numbers on a page they shared\n\nA dashboard is a site like any other here. Build it as a page and publish it;\nthe reader gets a URL, not a screenshot.\n\nDo not use Send for code, config or tests that stay in the repository. Those\nbelong in files.\n\n## Publishing is an outward-facing act\n\n`CreateSite` puts the content at a live URL. Anyone holding that link can open\nit. Before publishing, be sure that:\n\n- the content contains no credentials, internal hostnames or customer data\n  the person did not intend to publish\n- you have read any file you are about to publish on their behalf\n- the person expects a shareable link, not a local file\n\nWhen in doubt about whether something should be public, ask before you publish,\nnot after.\n\n## The loop\n\n1. `CreateSite` with the finished HTML. It returns the live URL.\n2. Give the person the URL. That is the deliverable — not a description of it.\n3. `EditSite` for revisions. Edit the existing site rather\n   than creating a second one, so the link the person already shared stays good.\n4. `manage_sites` to list what exists, rename, or change link settings.\n5. `GetSite` to read back what is currently published before you change it.\n\n## Images\n\nNever inline or base64-encode an image. Upload it, then reference the returned\nid as `<img src=\"asset:{fileId}\">`. `manage_files` uploads images and shows what is\nalready available. Confirm which image the person wants before you place it.\n\n## Revisions\n\nWhen someone asks for a change to a page that already exists, read the current\nversion first and edit it. Publishing a second site with the same title splits\nthe work across two URLs and breaks the link already in someone's inbox.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}