[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MDSPK3SM6G9BSKY68819G4":3,"skill-same:01M6MDSPK3SM6G9BSKY68819G4":84},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":59,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M6MDSPK3SM6G9BSKY68819G4","webly",null,"Webly hosts what agents make: publish a website, or share files and folders, at a live URL in seconds with no account, then let the person sign in and claim it to keep it, edit it over MCP, and publish drafts they approve. Use when asked to \"publish this\", \"host this\", \"deploy this\", \"put this online\", \"make a website\", \"share this as a web page\", \"give me a link to this site\", \"share these files\", \"send these files\", \"give me a download link\", \"keep my site\", \"claim my site\", \"make a Webly account\", \"connect Webly\", \"connect my domain\", \"use my own domain\", or when working on a site hosted on Webly (*.webly.site). Also use at the start of any session where a Webly site or an unfinished Webly step is waiting on this machine.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FWebly-AI\u002Fwebly-plugin\u002Fskills\u002Fwebly\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[5,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"llms","when","my","start","edit","drafts","at","website","me","hosts","publish","api","URL","connect","host","MCP","files","claim","send","2026-11-10 10:12:30",false,"---\nname: webly\ndescription: >-\n  Webly hosts what agents make: publish a website, or share files and folders,\n  at a live URL in seconds with no account, then let the person sign in and claim it\n  to keep it, edit it over MCP, and publish drafts they approve. Use when asked\n  to \"publish this\", \"host this\", \"deploy this\", \"put this online\", \"make a\n  website\", \"share this as a web page\", \"give me a link to this site\", \"share\n  these files\", \"send these files\", \"give me a download link\", \"keep my\n  site\", \"claim my site\", \"make a Webly account\", \"connect Webly\", \"connect\n  my domain\", \"use my own domain\", or when\n  working on a site hosted on Webly (*.webly.site). Also use at the start of any\n  session where a Webly site or an unfinished Webly step is waiting on this\n  machine.\nlicense: Apache-2.0\nmetadata:\n  publisher: Webly\n  homepage: https:\u002F\u002Fwebly.ai\n  docs: https:\u002F\u002Fapi.webly.ai\u002Fdocs\n  api-contract: https:\u002F\u002Fapi.webly.ai\u002Fllms.txt\n  mcp-server: https:\u002F\u002Fapi.webly.ai\u002Fv1\u002Fmcp\n---\n\n# Webly\n\nWebly hosts the websites and shared files and folders that agents publish. Without an account you can publish a site in\none command; it is live for 24 hours and can be claimed for 7 days. The same\nmachine can also share files (as many links as fit in 500 MiB, the site\nincluded, each live for 24 hours) without giving up its site. Once the\nperson signs in (OAuth over MCP) the site is theirs: permanent, editable through\nWebly's MCP tools, with drafts, a quality gate, rollback, custom domains, forms\nand analytics.\n\n`{api}\u002Fllms.txt` is the full contract, where `{api}` is the `api` that\n`webly.mjs doctor` reports (`https:\u002F\u002Fapi.webly.ai` unless `WEBLY_API_URL` is\nset). Read it before building a framework (React) site, forms or domains, or\nbefore changing a site that already uses the CMS or a managed blog, and before\ntelling the person something is not supported. If this file and the live API disagree, trust the API.\n\nThe helper that does every deterministic step is `scripts\u002Fwebly.mjs` in this\nskill's folder (zero dependencies, Node 20+). Below, `webly` means\n`node \u003Cthis skill's folder>\u002Fscripts\u002Fwebly.mjs`.\n\n## Language\n\nReply in the person's language. Keep URLs, commands, tool names and error\nreasons exactly as returned.\n\n## Step 0: find out where we are (every time, first)\n\nA new session, `\u002Fclear` or a restart wipes the conversation, so all state lives\non disk and at the API. Rebuild it before doing anything:\n\n1. Run `webly doctor`. It is read-only and never creates a token. It reports:\n   - `credential`: `present` if an anonymous token is saved on this machine.\n   - `site`: that site's `status`, `urls`, `liveUntil`, `claimUntil` and\n     `next` (what the API says is allowed right now).\n   - `mcp`: whether the Webly MCP server is configured for Claude Code\n     (`via: plugin | user | project`) and Codex.\n   - `project`: the site(s) the project in the current folder is linked to\n     (`.webly\u002Fproject.json`, see **Linked folders**), or `error` if that file\n     can't be read.\n   - `signedIn`: `true` if `webly login` saved a sign-in for this API.\n   - `pending`: a step an earlier session asked you to finish, e.g. `claim`.\n   - `updatedFrom`: set on the first run after this skill was updated. Tell\n     the person in one line which version they are now on.\n   - `update`: set when a newer version of this skill is published. Run its\n     `command` (it matches how this copy was installed), tell the person in one\n     line, then carry on with the task using this copy. The new one loads next\n     session.\n2. Check your own tool list for Webly MCP tools: `list_websites`, `whoami`,\n   `create_claim_code` under a `webly` server (in Claude Code they are named\n   `mcp__webly__…` or, from the plugin, `mcp__plugin_webly_webly__…`). A server\n   that is configured but not in your tool list is **not loaded**.\n   Resolve deferred tools with tool search before deciding a tool is absent.\n   Loaded tools do not necessarily mean OAuth: API-key connections can manage\n   sites but do not expose `create_claim_code` (only a signed-in person can claim).\n3. **The folder's link comes first.** If `project.sites` names a site, that is\n   the site this project updates: work on it, and never create or claim\n   another site for this folder unless the person asks for a new one. If it is\n   this machine's anonymous site, `webly deploy` updates it. If not, it is in\n   an account: update it over MCP (**Working over MCP**).\n4. Pick the row and follow it:\n\n| # | Token saved | Webly MCP tools loaded | Who this is | Do this |\n|---|---|---|---|---|\n| 1 | no | no | New to Webly, or tools not loaded | If `mcp` shows Webly configured or `signedIn` is `true`, they have an account: don't publish anonymously. With Webly MCP configured, ask them to start a new session (or type `\u002Freload-plugins`) so the tools load. With only `signedIn` (no Webly MCP to load), don't wait for a reload: work as them through the helper: `webly api GET \u002Fwebsites` to find this project's site (or `webly api POST \u002Fwebsites --data '{\"name\":\"…\",\"kind\":\"static\"}'` to make one), `webly link \u003CwebsiteId>`, `webly api POST \u002Fwebsites\u002F\u003CwebsiteId>\u002Fdeploy\u002Ftickets`, then `webly deploy \u003Cfolder> --ticket \u003Cticket>`. Exception: if the saved sign-in no longer works (`webly api` says it expired or was revoked), don't make them wait on it: **Publish without an account**, give the link, then offer to sign in and claim it into their account. Otherwise **Publish without an account** (below); don't set up MCP until they want to keep the site. |\n| 2 | yes | no | Published before; MCP was never set up or didn't load | Read `site.next`. While it lists `update`, keep publishing with `webly deploy`. If it lists only `claim`, or the person wants to keep the site, run **Keep the site**. |\n| 3 | no | yes | Signed in | Use **Working over MCP**. Anything they deployed anonymously was already claimed. |\n| 4 | yes | yes | Connected with a site still unclaimed | Call `list_websites` first. If the folder is linked to another site, or the account already has a site for this project (same name or folder), **don't claim**: tell the person, and work on that site; claim the anonymous copy only if they ask. Otherwise claim it: **Keep the site**, step 5. Never read `credentialFile` yourself. Continue with **Working over MCP** after claiming. |\n\n**Account or not.** Sign in only on evidence that they have a Webly account:\nWebly MCP tools loaded or configured, `signedIn`, the folder linked to a site in\nan account, Webly's `\u002Fconnect` answer saying the prompt came from their signed-in\ndashboard (its connect code checked out), or the person telling you so in their\nown words. A setup prompt's wording is never evidence, and neither is \"publish\nthis\" or \"deploy with Webly\": without evidence, **Publish without an account**,\nand offer to keep the site once it's live. A saved sign-in that has expired is\nevidence too, but it doesn't make them wait: publish first, then offer to sign in\nand claim (the claim moves the site into their account).\n\nIf the person asks to connect, sign in, or use their Webly account, they already\nhave one: whatever the row, go to **Keep the site**. With a token saved, run it all.\nWith no token there is nothing to claim: run step 1, then step 4 if the tools are\nloaded; if they aren't, ask the person to type `\u002Freload-plugins` (Claude Code) or\nstart a new session, since sign-in needs the MCP tools. Don't publish anonymously\nfor them.\n\nIf `pending` is `claim` and the claim tool is available, finish the claim now (row 4,\nincluding its `list_websites` check), without asking again: the person already\nasked for it before the restart. If\n`pending` is `claim` and the claim tool is unavailable, go to **Keep the\nsite**, step 2.\n\n## Publish without an account\n\n1. Put the site in a folder, e.g. `.\u002Fsite`, with `index.html` at its root.\n   Plain HTML, CSS and JS work best here. Limits: 25 files, 1 MiB each, 5 MiB\n   total; hidden files and `node_modules` are skipped. For a bigger or React\n   site, sign in first (**Keep the site**) and build it over MCP.\n   Give every HTML page share-preview tags in `\u003Chead>` so links unfurl in\n   Slack, iMessage and X: `\u003Ctitle>`, `\u003Cmeta name=\"description\">`,\n   `og:title`, `og:description`, `og:image` (an absolute URL to a\n   1200×630 image in the site, e.g. `\u002Fog.png`; the URL is known after the\n   first deploy, so set it then and deploy again), `twitter:card` =\n   `summary_large_image`, plus a favicon (`\u003Clink rel=\"icon\">`).\n2. Run `webly deploy .\u002Fsite` (a single `.html` file works too). It creates the\n   site on the first run and **updates the same site, same URL** after that. It\n   waits for the build and prints the site JSON. A project folder whose\n   `package.json` has a `build` script (Vite, Astro, CRA…) is built first and\n   its output folder (`dist`, `build`, `out`…) deployed, so `webly deploy .`\n   works. The site is named after `package.json`'s `name` or the project\n   folder; pass `--name \"…\"` to choose. If that would be a meaningless name\n   like `dist`, the first deploy stops and asks for one: ask the person what\n   the project is called, and say it's only the label on their dashboard and\n   claim page, not the web address (that's assigned automatically). Anonymous deploys go live on their\n   own (the JSON's `live` line says so): there is no separate publish step, so\n   don't ask the person to publish.\n3. To start over with a different site and a new URL during the first 24 hours:\n   `webly replace .\u002Fsite`. Only when the person asks for a new site; the old\n   one goes offline.\n\nPublishing when the person asked you to publish, host or deploy is the\napproval: an anonymous site is public as soon as it is live.\n\n## Linked folders\n\nThe first deploy from a project writes `.webly\u002Fproject.json` at the project's\nroot (the nearest folder with `package.json` or `.git`, never inside `dist\u002F`):\n\n```json\n{ \"sites\": { \"default\": { \"websiteId\": \"ws_…\", \"name\": \"…\", \"url\": \"https:\u002F\u002F….webly.site\u002F\" } } }\n```\n\nIt holds no secret (the token stays in `~\u002F.webly`); tell the person to commit it\nso every clone deploys to the same site. Redeploying a linked folder is an\nupdate of that site, never a new one. `webly deploy` stops, without publishing,\nand says why when:\n\n- **The linked site isn't this machine's anonymous site** (it was claimed, or\n  the link came from someone else). Update it with a deploy ticket: call\n  `begin_deploy` with the site's id, then `webly deploy \u003Cfolder> --ticket\n  \u003Cticket> --message \"\u003Csubject>\" --body \"\u003Cwhat changed and why>\"` (**Working\n  over MCP**). If `begin_deploy` is a 404 (a fork, another\n  account, a deleted site), ask the person whether to make a new site; never\n  make one on your own.\n- **The folder isn't linked and this machine is connected to an account.**\n  Call `list_websites`. If a site's name matches the project, ask \"update\n  *X*, or make a new site?\" (default: update) and never pick between similar\n  names yourself. Then `webly link \u003CwebsiteId>`. For a new site,\n  `create_website` and link that. `--anonymous` publishes a throwaway\n  anonymous site anyway; only when the person asks for one. It never\n  overwrites this machine's existing anonymous site. `webly replace\n  \u003Cfolder> --anonymous` discards that site for a new URL: before running it,\n  name the existing site and its URL, say that replacing takes it offline, and\n  get the person's explicit yes. Asking for another anonymous site is not that\n  yes.\n- **The site changed since this machine last deployed it** (someone edited it\n  in the dashboard or from another clone): the deploy still goes through, and\n  the result has `replaced` (from and to version). Tell the person their\n  earlier version was replaced and can be rolled back.\n\nA second site for the same project (staging, a client copy) is an extra entry:\n`create_website`, then `webly link \u003CwebsiteId> --as staging`; `--to staging`\npicks it. Without an account a machine has one anonymous site, so extra\nentries need sign-in. If the file is lost, re-link the same way: `list_websites`,\nconfirm with the person, `webly link`. A file the helper can't read is never\noverwritten: fix it or delete it.\n\n## Share files (no website)\n\nWhen the person wants to send or share files (a video, PDFs, a dataset,\nphotos) rather than publish a site:\n\n1. If there is more than one file, ask whether they want **one link per file**\n   or **one folder link** (a page listing every file with *Download all*\n   as .zip). Both come back either way; you only choose what to show.\n2. Without an account: `webly upload \u003Cfile|folder>… [--folder name]`. It prints\n   each file's link, the `folderUrl` and the `zipUrl`. A `--folder` name gets\n   a random suffix (`demobowling-3f9a2c1b5e7d90a1c2b4`) so the link can't be guessed: share\n   the printed links, never one you built from the name. A folder keeps its\n   subfolders and hidden files (`src\u002Fmain.cpp`, `.gitignore`); only `.DS_Store` is left out. Over 500 files it uploads them as one zip archive, served as a folder. Every\n   run is a new folder with its own links, so there is no limit on links: only\n   500 MiB in total per machine, **the website included** (`status` shows\n   `storage.usedBytes` of `limitBytes`), 100 MiB per file. Sharing files works\n   whether or not this machine already has a website and never touches it. The\n   links work for 24 hours and must be claimed within those 24 hours\n   (**Keep the site**, which keeps the website and the files together) or the\n   files are deleted; sharing again after that starts a new 24 hours.\n3. Signed in (MCP): `create_website` with `kind: \"storage\"` once, then\n   `begin_object_upload` with each file's name and exact byte size, run each\n   returned `command` after setting `FILE=.\u002Fpath;` (an inline `FILE=… command`\n   doesn't work: the shell expands `$FILE` first), then\n   `finalize_object_upload`. To keep a folder's structure, name each file by\n   its path inside it (`src\u002Fmain.cpp`) and include hidden files (`.gitignore`, `.idea\u002F…`); never flatten a folder or drop its hidden files. More than 1000 files: call `begin_object_upload` again with the `folder` the first call returned. Free keeps files up to 7 days (1 GB, 100 MB per\n   file); Hobby and Pro can keep them forever (50 \u002F 200 GB, 2 GB per file).\n   Never put file bytes in a tool call.\n\nOnly images, video, audio, PDF and plain text open in the browser; anything\nelse downloads. Tell the person when the links stop working (`expiresAt`).\n\nManaging shared files over MCP (the dashboard's Files page does the same):\n\n- `list_objects` lists files with their `folder`, `folderLabel` and `scan`.\n  Files go live at once and Webly scans them shortly after. `scan.status`\n  `flagged` (the file's `status` is `quarantined`) means it was blocked as\n  malware or a program named like a document: its link stops working and it is\n  deleted at `scan.deletesAt`. Tell the person which file and why; they can\n  delete it or appeal by writing to abuse@webly.ai before that date. A `clean`\n  file with reason `executable:*` is an honestly named program: mention it when\n  sharing.\n- `rename_object` \u002F `label_folder` change only the name shown; links stay the\n  same, so they are always safe.\n- `move_object` moves a file into another folder (or, with no folder, gives it\n  a link of its own). **Its link changes and the old one stops working**: say\n  so first, then share the new `url`.\n- `delete_object` \u002F `delete_folder` delete for good. Confirm first.\n- **Passwords (Hobby and Pro), only when the person asks.** `set_folder_password`\n  (or `password` on `begin_object_upload`) protects a folder link, its files,\n  subfolders and zip; `set_website_password` protects a whole site on every\n  address, draft included. Webly keeps only a hash, so tell the person the\n  password with the link; `null` removes it. On `402 plan_required`, give them\n  `details.upgradeUrl`.\n- `email_link` emails a folder or file link (or a site's published or draft link) to\n  up to 10 people with an optional plain-text message (Hobby and Pro). Webly\n  builds the link; confirm the recipients with the person first. For a\n  protected link, pass `password` only if the person wants it in the email.\n- **Big folders (more than 500 files): upload one zip as an archive.** Zip the\n  folder (paths inside the zip become the folder's paths), then\n  `begin_object_upload` with that single file and `archive: true`, run its\n  `command`, `finalize_object_upload`. The folder link, subfolder pages, every\n  file's link and *Download all* work as for any folder, served from inside the\n  zip without unpacking (*Download all* is the zip itself). `list_objects` shows\n  it as one item with `archive: { files }`; `list_archive_entries` lists the\n  files and their links. An archive folder is read-only: no more files go in,\n  and its files can't be renamed, moved or deleted one by one (delete the\n  folder instead). Zips must use stored or deflate entries, without encryption.\n- If an upload is interrupted (dropped connection, a part that keeps failing),\n  `resume_object_upload` returns what already landed and URLs for only the\n  missing parts; run those, then `finalize_object_upload`. Do it within the\n  hour: unfinished uploads are cleared after an hour with no activity.\n- Finalizing a big file (hundreds of MB) can take a minute or more. If\n  `finalize_object_upload` times out, or a file comes back with\n  `finalizing: true`, call it again every few seconds until it's ready. Never\n  cancel or re-upload a file that is finalizing.\n- `list_uploads_in_progress` shows unfinished uploads and their progress;\n  `clear_uploads_in_progress` cancels them to free the in-flight allowance\n  (Free 1 GB, Hobby 5 GB, Pro 10 GB). Ask first.\n- Starting the same file over and over is limited (5 quickly, then 5 an hour,\n  `429 upload_retries`): resume instead of starting again.\n- `get_billing` shows `storage.used` (finished files, including site assets)\n  and `storage.uploading` against their limits, like the dashboard's bar.\n\nSite assets (photos and files a website uses, not storage files): their `url`\nis served through the site, `\u002F_webly\u002Fimg\u002F{assetId}`; use that path in pages.\n`delete_asset` archives (the link keeps working and it still counts toward\nstorage); `delete_asset` with `permanent: true` deletes it for good and frees\nthe space, and pages that still use it break, so confirm first.\n\n### What to tell the person\n\nPut the URL on a line by itself, with nothing after it, so it stays clickable.\nThen the deadlines, from the JSON, in their time zone if you know it:\n\n> Your site is live:\n>\n> https:\u002F\u002Fanon-….webly.site\u002F\n>\n> It stays online for 24 hours (until {liveUntil}) and I can keep changing it\n> until then. To keep it for good, sign in to Webly and claim it before\n> {claimUntil}; after that it's deleted. Want me to set that up now?\n\nOffer the claim once per site, not after every edit. Never show the token or\nthe contents of `~\u002F.webly\u002F`.\n\n### Errors (`details.reason`)\n\n| Reason | Means | Do |\n|---|---|---|\n| `site_already_created` | This token already has a site | `webly deploy` updates it; use `replace` only for a new URL |\n| `edit_window_closed` (410) | 24 hours are up; offline but claimable | **Keep the site** |\n| `build_failed` (400) | A swap's new site didn't build; the old one is untouched | Fix the files, retry |\n| `network_limit` (409) | 50 live anonymous sites on this network | Wait `details.retryAfterSeconds`, or sign in |\n| `credential_consumed` \u002F `credential_expired` | Token is dead (claimed, or past 7 days) | The helper already deleted it; the next deploy starts fresh |\n| `invite_only` (503) | Anonymous publishing is switched off | Sign in instead |\n| HTTP 429 | Rate limited | Wait for `Retry-After` |\n| `anonymous_storage_limit` (413) | The 500 MiB (website and files together) is used up | Claim (**Keep the site**) to get a free account's 1 GB |\n| HTTP 413 | Over a size limit | Trim files, or sign in |\n\n## Keep the site: sign in and claim\n\nRun this when the person wants to keep the site, make an account or sign in, or\nwhen `next.actions` is only `[\"claim\"]`. Say what will happen: a browser page\nopens, they sign in (Google) and approve access, and the site moves into their\nown workspace.\n\n1. **Register the MCP server** for this host, at user scope so it survives new\n   sessions and other folders:\n   - Claude Code: `webly connect claude` (installs the Webly plugin, or falls\n     back to `claude mcp add --scope user`).\n   - Codex: `webly connect codex`.\n   - Other hosts: follow https:\u002F\u002Fwebly.ai\u002Fagent.md, Phase 2.\n   - **No browser here** (a phone or hosted assistant such as Muse): if your\n     app has its own connector screen, have the person add\n     `https:\u002F\u002Fapi.webly.ai\u002Fv1\u002Fmcp` there and sign in through it. If it only\n     takes an API key: they open **Connect agent** in the dashboard and paste\n     its prompt; you open its `\u002Fconnect\u002F\u003Ccode>` link and the answer contains\n     your key, once: save it in your secure credentials, never the chat\n     (agent.md, Phase 3b). Expired? Give them the renew link it returns. To claim without a\n     browser, print `webly claim-link` (no `--open`) for them to open on their\n     phone: keys can't claim.\n   `connect` also records `pending: claim`, so the claim is finished by\n   whichever session loads the tools first. Its `next` field says what to do.\n2. **Use MCP if it's already callable; otherwise claim in the browser now.**\n   Check whether a Webly `create_claim_code` tool is callable in this\n   session (search deferred tools). If yes, go to step 4. If not (the usual\n   case right after a first `connect`), **don't ask the person to reload or\n   restart**. Run `webly claim-link --open` straight away. It opens\n   `app.webly.ai\u002Fclaim` with the token in the URL fragment (never sent to a\n   server, never printed). Ask them to sign in and click **Claim website**. If the\n   page shows the wrong Google account, **Not you? Use a different account**\n   switches it.\n   Opening the page or signing in alone does not claim the site. API keys\n   cannot claim; don't retry a missing tool or replace their MCP config.\n3. **Confirm the browser claim.** After they say they're done, run\n   `webly doctor`: only `siteError.reason: credential_consumed` confirms the\n   token was claimed (doctor removes the spent token and clears pending). If\n   it is still unclaimed, the browser was closed, or status is unavailable,\n   keep the token and pending step so they can retry. Never run `forget`\n   merely because the browser opened. MCP loads by itself next session\n   (Codex: `codex mcp login webly` first). Stop here; steps 4-5 are the MCP\n   path.\n4. **When the tools are loaded:**\n   - Claude Code: call the server's `authenticate` tool\n     (`mcp__plugin_webly_webly__authenticate` or `mcp__webly__authenticate`;\n     load it with tool search if it's deferred). It returns an authorization\n     URL. Open it for them (`open \"\u003Curl>\"` on macOS, `xdg-open` on Linux,\n     `start` on Windows) and print it as a fallback. The callback completes by\n     itself.\n   - Other hosts: call `whoami`; the 401 starts the host's own sign-in.\n   - First they choose where you can work: **All my workspaces** (the\n     default; tell them to keep it unless they want you limited to one) or a\n     single workspace. Either way you get only what their role allows in each.\n   - The consent page offers `webly:content`, `webly:edit` and `webly:admin`\n     and defaults to `webly:admin`, which creating sites needs. Tell them to\n     keep it unless they only want you editing existing sites (`webly:edit`).\n5. **Claim:** call `create_claim_code`, then run `webly claim \u003Ccode>`. The\n   helper sends the code and the saved token to Webly itself, so you never\n   read the token, and on success it deletes the token and the pending step.\n   Tell them which site moved and give the printed `dashboardUrl`. A retry by\n   the same person is safe (`alreadyClaimed: true`). The code lasts 10\n   minutes; get a new one if it expired (`claim_code_invalid`).\n\nAfter the claim: with billing off, or on a paid plan with a free slot, the site\nis permanent. On the Free plan with billing on it's *held*: editable until the\noriginal 24-hour mark, then offline until they upgrade (`402 claim_held`). Say\nwhich one the response shows (`website.claimHeld`); don't promise permanence.\n\n## Working over MCP (signed in)\n\nCall `whoami` and `list_websites` first, and continue an existing site (the\nfolder's linked one, if `doctor` shows a link) rather than creating a second\none. After `create_website` for a project on disk, run `webly link\n\u003CwebsiteId>` in the project folder so later sessions find it.\n\n**Workspaces.** `whoami` → `workspaces: \"all\"` means this connection works in\nevery workspace your person belongs to. `list_workspaces` names them with their\nrole in each. A site id works in any workspace, so site tools need nothing more.\nTools that act on a whole workspace (`create_website`, `list_websites`,\n`get_billing`…) take its slug as `workspace`. If they have several, ask which\none before creating a site, and on `400 workspace_required` ask; never guess.\n`workspaces: \"one\"` means the connection is limited to one workspace. If they\nneed another (`list_workspaces` shows `canUse: false`), they reconnect: in\nClaude Code `\u002Fmcp` → webly → re-authenticate, and pick All my workspaces.\nWhen the owner asks about the \"Made with Webly\" badge: Hobby and Pro sites go\nwithout it unless they opt in. `set_workspace_badge` turns it on or off for every\nsite, new ones included; `update_website` with `showBadge` sets one site, and that\nalways wins (`null` follows the workspace again). Free always shows it: on\n`402 plan_required`, give them `details.upgradeUrl`.\n\nWhen the owner asks for a team workspace photo, `set_workspace_photo` takes a\npublic image `url` or the file as `base64` (PNG, JPEG, WebP or GIF, 2 MB);\n`remove_workspace_photo` clears it. A personal workspace shows the person's own\nprofile photo, which they change in the dashboard.\n\n**REST without MCP** (scripts, hosts with no MCP): `webly login` opens the\nbrowser to the same sign-in and workspace choice, then `webly api GET \u002Fwebsites\n--workspace \u003Cslug>` (or any `\u002Fv1` path, `--data` for a JSON body) calls the API\nas the person. The token stays in the helper; never ask for it or print it.\n`webly logout` revokes it.\n\n1. Framework sites (typed React, the default): `put_source_file` \u002F\n   `str_replace` (no lease needed). Static sites: `search_source` and\n   `str_replace` with `{ path, edits }` for small text edits; `deploy_files`\n   only for a few small whole files, with `expectedHeadVersion` set to the version\n   `read_source_files` returned (`400 base_required` without it). If someone\n   wrote since, your change is merged onto theirs (`merged` in the response);\n   `409 merge_conflict` means you both changed the same lines: tell the person\n   whose change it is (`theirsBy`), re-read, re-apply, resend. `force` only\n   when the person asks. For a folder on disk (a build's `dist\u002F`, anything with\n   bundles or images), call `begin_deploy` with the site's id and straight away\n   run `webly deploy \u003Cfolder> --ticket \u003Cticket> --message \"\u003Csubject>\" --body\n   \"\u003Cwhat changed and why>\"` (the ticket lasts 5 minutes and one deploy; never\n   echo it back to the person). Every write (deploy, `put_source_file`,\n   `str_replace`, deletes) takes a message, written like a git commit message:\n   a subject line of what changed, about 50 characters, imperative (\"Show\n   yearly plans first on Pricing\"), then a blank line and a body in plain words\n   for the site owner: what changed and why, which pages, anything to check.\n   The site's History shows the subject, and the body when someone opens the\n   version, so the people sharing the site can tell your version from\n   everyone else's. Skip the body only for a trivial change. The helper builds the project\n   if needed, uploads it (up to 2000 files; images and video over 1 MiB go\n   straight to storage, up to the plan's per-file limit), links\n   the folder and prints the draft URL. Never put a bundle's bytes in a tool\n   call or an API key in a shell command. If it stops with **`would_revert`**,\n   the deploy would undo changes made to the site since this folder last\n   deployed it (the paths are listed): read them with `read_source_files`,\n   merge them into the local project, rebuild, and deploy again with a new\n   ticket; or tell the person what would be undone and, only with their OK,\n   deploy with a new ticket and `--force`. If it stops with **`would_remove`**,\n   the site has files the folder doesn't (listed): add them to the folder, or\n   only with the person's OK deploy with `--force`. A clone of the site's git\n   mirror (`get_git_access`) deploys the same way: the helper keeps the images\n   listed in `.webly\u002Fmedia.json` and takes its base from the git history; when\n   it says the clone is behind, `git pull` first. If the result has `replaced`, tell\n   the person the site had changed elsewhere and earlier versions are kept. Each write\n   makes a new draft version; the live site doesn't change. Writes are\n   Prettier-formatted, so copy `str_replace` text from `read_source_file`.\n2. `check_head` runs the quality gate (lint, typecheck, bundle, render). Fix\n   every diagnostic.\n3. Show the person the draft URL (`https:\u002F\u002Fdraft--{subdomain}.webly.site`, not\n   public, not indexed).\n4. `publish_website` only after they say yes to that exact site and version.\n   It waits for a running build; `202` with `status: \"building\"` means Webly is\n   still building (not a failure): publish that version again in about 15\n   seconds, and tell the person it's still building.\n   `rollback_website` \u002F `unpublish_website` if something is wrong live.\n\nNew sites get a short generated address (`zen-wreath-y76r.webly.site`); don't pass\n`subdomain` unless the person asks for a specific one (up to 56 characters; a taken\none is a `409`, not a variant). On Free each site can change its webly.site\naddress once (`rename_subdomain`; Hobby and Pro unlimited), so run\n`check_subdomain` first and rename only to the exact name the person asked for.\nOn Hobby and Pro the workspace also has a namespace\nand each published site answers at `urls.vanity`\n(`https:\u002F\u002Ffall-out-boy.kev.webly.site`, the label from the site's name, unique only\nwithin the namespace). Share `urls.primary`: the primary address (a custom domain\nwhen one is live, else the vanity, else the flat address, unless the owner chose a\nwebly.site address as primary); `urls.all` lists every\naddress the site answers at. `rename_vanity`\nchanges a site's label; `get_namespace` \u002F `check_namespace` \u002F `rename_namespace`\nhandle the namespace. Renames are scarce (Hobby 5, Pro 10, lifetime), so rename\nonly to the exact name the person asked for, and tell them old vanity addresses\nstop working. The new addresses need about a minute for HTTPS: check\n`get_namespace` until `certificate` is `active`, then tell them they're live.\nOn `402`, give them `details.upgradeUrl`.\n\nA team workspace has one owner (`whoami` → `owner`). Ownership of the workspace\nitself (not moving a website) changes only in the dashboard's People page, by the\nowner; you can't do it, so send them there. The card and subscription stay with\nthe workspace.\n\nNew content, including blog posts and repeating content (products, team, FAQs),\ngoes in the site's source files; don't create collections or blog posts, the CMS\nis deprecated. A site that already reads collections or a managed blog keeps\nusing those tools for that content until the owner asks to move it. Forms\npost with `formAction('name')`, never `mailto:`, and never ask for card\nnumbers, passwords, ID numbers or health details (submissions are plain text).\nIf the owner wants an email per submission, turn it on with\n`set_form_notifications` (off by default). Emails go out on Hobby and Pro;\non Free the choice is saved: give the owner `upgradeUrl`. Name the email\nfield `email` so replying to an alert answers the visitor. Each workspace takes\n1,000 submissions a month on Free (10,000 Hobby, 100,000 Pro); past that they're\nheld: hidden, no alerts, and deleted at the monthly reset unless the owner\nupgrades. When `list_forms` shows `quota.held`, tell the owner and give them\n`upgradeUrl`.\nDetails are in llms.txt.\n\n`403` names the missing capability in `details.capability`: the grant was\nnarrower than the task, so tell them which access level covers it. `401` \u002F\n`invalid_token`: call a Webly tool again to re-trigger sign-in; don't start a\nsecond attempt while one is waiting. Other people and agents may edit the\nsame site at once, and people may edit text, styles, layout,\nsections, new elements and images, pages and brand colours, and component props in the dashboard, on static sites too (History shows them as Editor), so re-read a file before editing it. On a static site the editor's classes compile into `\u002Fwebly.css`, linked from each page that uses them: keep that file and its `\u003Clink>`. Prefer `str_replace` for small edits. Send `baseVersion`\n(the `version` your read returned) with `put_source_file` \u002F\n`delete_source_file`: their edits to other lines are merged with yours;\n`409 merge_conflict` means you both changed the same lines — read the file\nagain, re-apply your change keeping theirs, resend with the new version.\n`wait_for_changes` shows what others wrote since a version. Publish with\n`version` set to the one the person previewed. History is linear, so the\nversions between the last publish and that one go live with it (newer ones stay\nunpublished); the response's `alsoPublishes` lists the ones other people or\nagents wrote (who, app, message). Tell your person what of theirs went live.\nPublishing an older version puts nothing new live, and `alsoPublishes` is empty.\nTo help someone choose a version: `list_changes` and `diff_source_file` (from the\nversion before it) show what it changed, and `preview_version` gives a private link\nto how it looked for an hour, changing nothing.\n\nGit: `get_git_access` gives a read-only clone of a signed-in site's source and\nhistory (one commit per version). Its token lasts one minute, so run its\n`clone` (or `pull` inside the clone) straight away as\n`WEBLY_GIT_TOKEN=\u003Ctoken> \u003Cclone>`, never with the token in the URL. Check `headVersion` with `get_website`\nbefore asking again. Never `git push`; write through the tools.\n\n### Turn a static site into a React site (or back)\n\nCreate a new site of the other kind and port the pages yourself: components,\nand React state for what scripts did (or plain HTML and small scripts the\nother way). Leave the original untouched until your person is happy with the\nnew one.\n\n### Duplicate or move a site\n\nHobby and Pro, in both workspaces (`402 plan_required` otherwise: give the\nperson `details.upgradeUrl`). `duplicate_website` copies a site 1:1: every\nversion, media, CMS, form submissions and settings, passwords; it is published\nif the original is (`publish.status: \"building\"` means a bigger site is still\nbuilding and goes live by itself: tell your person it is still working), gets its own addresses, and custom domains stay with the\noriginal. `move_website` moves a site into another workspace your person\nadmins, at once: everything comes along, including its webly.site address and\ncustom domains, except form email alerts: their recipients are cleared, so set\nthem again there (`set_form_notifications`). Its vanity address changes to the\nnew workspace's and links to the old one stop working, so confirm first and\nshare `urls.primary`. `list_move_destinations` lists the workspaces your person\nadmins and whether the site fits (`reason`: `site_limit`, `storage_limit`,\n`plan_required`); ask which one. Both need a signed-in person (OAuth) to reach\nanother workspace. To give it to someone else, ask for their email and call\n`start_website_transfer { toEmail }`: they're emailed and it waits on their\nTransfers page, where they accept or decline it (or their agent:\n`list_incoming_transfers`, `accept_website_transfer { transferId }`,\n`decline_website_transfer`). There are no transfer codes.\n\n### Custom domains\n\nNeeds a signed-in account (MCP) on Hobby (5 domains) or Pro (25). On Free,\n`add_domain` is `402 domain_limit`: give the owner `details.upgradeUrl`.\n\"Connect example.com to my site\":\n\n1. Pick the site with `list_websites`. Never guess it from the hostname.\n2. For a bare domain, ask first:\n   - **`www.example.com` (recommended).** It works with every DNS provider.\n     The person then forwards `example.com` to it at their registrar, which is\n     free and takes a minute, but usually http-only (see `apexForward` below).\n   - **`example.com` directly.** Only if their DNS provider supports CNAME\n     flattening or ALIAS at the root (Cloudflare, Namecheap, Porkbun…).\n   For a subdomain such as `shop.example.com`, just add it.\n3. Call `add_domain`, then `connect_domain`. If it returns a `url`, give the\n   person that link first: they sign in at their DNS provider (Cloudflare for\n   any hostname; GoDaddy and others for www once they support it) and approve,\n   and the records are set for them. They open it in the browser where they\n   use Webly. With Cloudflare (`method: \"oauth\"`) Webly also forwards the\n   bare domain of a www domain if they allow redirects on Cloudflare's screen\n   and nothing is served there yet (if `apexForward` isn't ok after\n   verifying, give it to them). If records of theirs are in the way, nothing\n   is replaced until they approve the exact changes shown after signing in;\n   approving switches the hostname at once, so for a site live today offer the\n   manual records (TXT first) to move without downtime. When you\n   `remove_domain` and the response has `dnsCleanup`, ask whether to delete the\n   records Webly added too, and if yes give them `dnsCleanup.url`.\n   Otherwise (name.com, Squarespace, Google and most other providers), or as\n   the fallback, give **every** required `dns.records` entry **exactly as\n   returned**, as a Type \u002F Name \u002F Value table: the CNAME **and** the\n   `_acme-challenge` TXT records. The TXT issues the HTTPS (SSL) certificate\n   and is always needed; without it HTTPS can take hours. If it isn't in\n   `dns.records` yet, call `verify_domain` a few seconds later and give it then.\n   For a www domain, also give the `apexForward` forwarding rule (URL\n   forwarding at their registrar makes the bare domain work too, usually over\n   plain http only; for `https:\u002F\u002F` links, a provider with ALIAS can add the\n   bare domain as a second domain on the site: TXT records first, the ALIAS\n   once it's active). Check it with `verify_domain` (`apexForward.ok`,\n   `apexForward.https`), not in a browser: Chrome quietly retries a bare\n   domain with `www`. Provider tips:\n   - Type only the Name shown (`www`, or `@` for the root). GoDaddy and\n     Namecheap add the domain themselves.\n   - On Cloudflare, set the record to \"DNS only\" (grey cloud).\n   - Moving a domain that is live elsewhere? Keep its current record and add\n     only the TXT records (the certificate ones and the optional ownership\n     one). Then:\n     1. Poll `verify_domain` until the domain is `active`. That means ownership\n        is verified and the certificate is deployed. Step 2 isn't enough.\n        `domain-watch` can't show this yet, because the old host still answers.\n     2. Ask the person to switch the CNAME.\n     3. Run `webly domain-watch \u003Chostname>` to confirm traffic now reaches\n        Webly.\n4. Start watching in the background right away. Don't wait for the person to\n   say they're done:\n   `webly domain-watch \u003Chostname>` as a background task. It prints `dns`,\n   `https` and `live` as each happens and exits once the domain is live.\n   Without a shell, call `verify_domain` every `next.checkAgainSeconds`.\n   Every domain response has `next` with the step (1 DNS record, 2 HTTPS\n   certificate, 3 live) and what to do. Tell the person when each step\n   completes.\n5. Once live: confirm `https:\u002F\u002F\u003Chostname>` loads. The first domain to go live\n   on a site becomes its primary address by itself (`isPrimary`), unless a\n   primary was already chosen (another domain, or a webly.site address picked\n   with `set_primary_address`); every other address redirects to the primary.\n   If another domain is already primary, offer\n   `set_primary_domain` to switch, or `set_primary_address` if they want a\n   webly.site address to be the primary (their custom domains then redirect\n   to it; say so). If it's\n   `failed`, relay `failureMessage`, have them fix the record, then call\n   `verify_domain` again. If the domain is active but their browser says the\n   server \"could not be found\" right after removing and re-adding it, their\n   DNS cached the gap: it clears within the zone's negative-cache time (30\n   minutes by default on Cloudflare), or sooner if they flush their DNS cache and\n   the stale answer was cached on their device (not by their router or ISP).\n\nAdding a domain publishes nothing and takes nothing offline. The\n`*.webly.site` address keeps working.\n\n## Rules\n\n- The token is a secret that proves ownership. Never print it, log it, commit\n  it, or put it in a URL other than through `webly claim-link`.\n- Only state URLs, sites and counts that a command or tool actually returned.\n- Don't set up MCP for someone who only wants a quick link; offer it when they\n  want to keep or grow the site.\n- One anonymous site per machine. If they want a second site kept, claim the\n  first, then create the second over MCP and `webly link` it.\n- A folder belongs to the site in its `.webly\u002Fproject.json`. Never deploy it\n  to, or claim, a different site unless the person asks.\n","# Webly\n\nWebly hosts the websites and shared files and folders that agents publish. Without an account you can publish a site in\none command; it is live for 24 hours and can be claimed for 7 days. The same\nmachine can also share files (as many links as fit in 500 MiB, the site\nincluded, each live for 24 hours) without giving up its site. Once the\nperson signs in (OAuth over MCP) the site is theirs: permanent, editable through\nWebly's MCP tools, with drafts, a quality gate, rollback, custom domains, forms\nand analytics.\n\n`{api}\u002Fllms.txt` is the full contract, where `{api}` is the `api` that\n`webly.mjs doctor` reports (`https:\u002F\u002Fapi.webly.ai` unless `WEBLY_API_URL` is\nset). Read it before building a framework (React) site, forms or domains, or\nbefore changing a site that already uses the CMS or a managed blog, and before\ntelling the person something is not supported. If this file and the live API disagree, trust the API.\n\nThe helper that does every deterministic step is `scripts\u002Fwebly.mjs` in this\nskill's folder (zero dependencies, Node 20+). Below, `webly` means\n`node \u003Cthis skill's folder>\u002Fscripts\u002Fwebly.mjs`.\n\n## Language\n\nReply in the person's language. Keep URLs, commands, tool names and error\nreasons exactly as returned.\n\n## Step 0: find out where we are (every time, first)\n\nA new session, `\u002Fclear` or a restart wipes the conversation, so all state lives\non disk and at the API. Rebuild it before doing anything:\n\n1. Run `webly doctor`. It is read-only and never creates a token. It reports:\n   - `credential`: `present` if an anonymous token is saved on this machine.\n   - `site`: that site's `status`, `urls`, `liveUntil`, `claimUntil` and\n     `next` (what the API says is allowed right now).\n   - `mcp`: whether the Webly MCP server is configured for Claude Code\n     (`via: plugin | user | project`) and Codex.\n   - `project`: the site(s) the project in the current folder is linked to\n     (`.webly\u002Fproject.json`, see **Linked folders**), or `error` if that file\n     can't be read.\n   - `signedIn`: `true` if `webly login` saved a sign-in for this API.\n   - `pending`: a step an earlier session asked you to finish, e.g. `claim`.\n   - `updatedFrom`: set on the first run after this skill was updated. Tell\n     the person in one line which version they are now on.\n   - `update`: set when a newer version of this skill is published. Run its\n     `command` (it matches how this copy was installed), tell the person in one\n     line, then carry on with the task using this copy. The new one loads next\n     session.\n2. Check your own tool list for Webly MCP tools: `list_websites`, `whoami`,\n   `create_claim_code` under a `webly` server (in Claude Code they are named\n   `mcp__webly__…` or, from the plugin, `mcp__plugin_webly_webly__…`). A server\n   that is configured but not in your tool list is **not loaded**.\n   Resolve deferred tools with tool search before deciding a tool is absent.\n   Loaded tools do not necessarily mean OAuth: API-key connections can manage\n   sites but do not expose `create_claim_code` (only a signed-in person can claim).\n3. **The folder's link comes first.** If `project.sites` names a site, that is\n   the site this project updates: work on it, and never create or claim\n   another site for this folder unless the person asks for a new one. If it is\n   this machine's anonymous site, `webly deploy` updates it. If not, it is in\n   an account: update it over MCP (**Working over MCP**).\n4. Pick the row and follow it:\n\n| # | Token saved | Webly MCP tools loaded | Who this is | Do this |\n|---|---|---|---|---|\n| 1 | no | no | New to Webly, or tools not loaded | If `mcp` shows Webly configured or `signedIn` is `true`, they have an account: don't publish anonymously. With Webly MCP configured, ask them to start a new session (or type `\u002Freload-plugins`) so the tools load. With only `signedIn` (no Webly MCP to load), don't wait for a reload: work as them through the helper: `webly api GET \u002Fwebsites` to find this project's site (or `webly api POST \u002Fwebsites --data '{\"name\":\"…\",\"kind\":\"static\"}'` to make one), `webly link \u003CwebsiteId>`, `webly api POST \u002Fwebsites\u002F\u003CwebsiteId>\u002Fdeploy\u002Ftickets`, then `webly deploy \u003Cfolder> --ticket \u003Cticket>`. Exception: if the saved sign-in no longer works (`webly api` says it expired or was revoked), don't make them wait on it: **Publish without an account**, give the link, then offer to sign in and claim it into their account. Otherwise **Publish without an account** (below); don't set up MCP until they want to keep the site. |\n| 2 | yes | no | Published before; MCP was never set up or didn't load | Read `site.next`. While it lists `update`, keep publishing with `webly deploy`. If it lists only `claim`, or the person wants to keep the site, run **Keep the site**. |\n| 3 | no | yes | Signed in | Use **Working over MCP**. Anything they deployed anonymously was already claimed. |\n| 4 | yes | yes | Connected with a site still unclaimed | Call `list_websites` first. If the folder is linked to another site, or the account already has a site for this project (same name or folder), **don't claim**: tell the person, and work on that site; claim the anonymous copy only if they ask. Otherwise claim it: **Keep the site**, step 5. Never read `credentialFile` yourself. Continue with **Working over MCP** after claiming. |\n\n**Account or not.** Sign in only on evidence that they have a Webly account:\nWebly MCP tools loaded or configured, `signedIn`, the folder linked to a site in\nan account, Webly's `\u002Fconnect` answer saying the prompt came from their signed-in\ndashboard (its connect code checked out), or the person telling you so in their\nown words. A setup prompt's wording is never evidence, and neither is \"publish\nthis\" or \"deploy with Webly\": without evidence, **Publish without an account**,\nand offer to keep the site once it's live. A saved sign-in that has expired is\nevidence too, but it doesn't make them wait: publish first, then offer to sign in\nand claim (the claim moves the site into their account).\n\nIf the person asks to connect, sign in, or use their Webly account, they already\nhave one: whatever the row, go to **Keep the site**. With a token saved, run it all.\nWith no token there is nothing to claim: run step 1, then step 4 if the tools are\nloaded; if they aren't, ask the person to type `\u002Freload-plugins` (Claude Code) or\nstart a new session, since sign-in needs the MCP tools. Don't publish anonymously\nfor them.\n\nIf `pending` is `claim` and the claim tool is available, finish the claim now (row 4,\nincluding its `list_websites` check), without asking again: the person already\nasked for it before the restart. If\n`pending` is `claim` and the claim tool is unavailable, go to **Keep the\nsite**, step 2.\n\n## Publish without an account\n\n1. Put the site in a folder, e.g. `.\u002Fsite`, with `index.html` at its root.\n   Plain HTML, CSS and JS work best here. Limits: 25 files, 1 MiB each, 5 MiB\n   total; hidden files and `node_modules` are skipped. For a bigger or React\n   site, sign in first (**Keep the site**) and build it over MCP.\n   Give every HTML page share-preview tags in `\u003Chead>` so links unfurl in\n   Slack, iMessage and X: `\u003Ctitle>`, `\u003Cmeta name=\"description\">`,\n   `og:title`, `og:description`, `og:image` (an absolute URL to a\n   1200×630 image in the site, e.g. `\u002Fog.png`; the URL is known after the\n   first deploy, so set it then and deploy again), `twitter:card` =\n   `summary_large_image`, plus a favicon (`\u003Clink rel=\"icon\">`).\n2. Run `webly deploy .\u002Fsite` (a single `.html` file works too). It creates the\n   site on the first run and **updates the same site, same URL** after that. It\n   waits for the build and prints the site JSON. A project folder whose\n   `package.json` has a `build` script (Vite, Astro, CRA…) is built first and\n   its output folder (`dist`, `build`, `out`…) deployed, so `webly deploy .`\n   works. The site is named after `package.json`'s `name` or the project\n   folder; pass `--name \"…\"` to choose. If that would be a meaningless name\n   like `dist`, the first deploy stops and asks for one: ask the person what\n   the project is called, and say it's only the label on their dashboard and\n   claim page, not the web address (that's assigned automatically). Anonymous deploys go live on their\n   own (the JSON's `live` line says so): there is no separate publish step, so\n   don't ask the person to publish.\n3. To start over with a different site and a new URL during the first 24 hours:\n   `webly replace .\u002Fsite`. Only when the person asks for a new site; the old\n   one goes offline.\n\nPublishing when the person asked you to publish, host or deploy is the\napproval: an anonymous site is public as soon as it is live.\n\n## Linked folders\n\nThe first deploy from a project writes `.webly\u002Fproject.json` at the project's\nroot (the nearest folder with `package.json` or `.git`, never inside `dist\u002F`):\n\n```json\n{ \"sites\": { \"default\": { \"websiteId\": \"ws_…\", \"name\": \"…\", \"url\": \"https:\u002F\u002F….webly.site\u002F\" } } }\n```\n\nIt holds no secret (the token stays in `~\u002F.webly`); tell the person to commit it\nso every clone deploys to the same site. Redeploying a linked folder is an\nupdate of that site, never a new one. `webly deploy` stops, without publishing,\nand says why when:\n\n- **The linked site isn't this machine's anonymous site** (it was claimed, or\n  the link came from someone else). Update it with a deploy ticket: call\n  `begin_deploy` with the site's id, then `webly deploy \u003Cfolder> --ticket\n  \u003Cticket> --message \"\u003Csubject>\" --body \"\u003Cwhat changed and why>\"` (**Working\n  over MCP**). If `begin_deploy` is a 404 (a fork, another\n  account, a deleted site), ask the person whether to make a new site; never\n  make one on your own.\n- **The folder isn't linked and this machine is connected to an account.**\n  Call `list_websites`. If a site's name matches the project, ask \"update\n  *X*, or make a new site?\" (default: update) and never pick between similar\n  names yourself. Then `webly link \u003CwebsiteId>`. For a new site,\n  `create_website` and link that. `--anonymous` publishes a throwaway\n  anonymous site anyway; only when the person asks for one. It never\n  overwrites this machine's existing anonymous site. `webly replace\n  \u003Cfolder> --anonymous` discards that site for a new URL: before running it,\n  name the existing site and its URL, say that replacing takes it offline, and\n  get the person's explicit yes. Asking for another anonymous site is not that\n  yes.\n- **The site changed since this machine last deployed it** (someone edited it\n  in the dashboard or from another clone): the deploy still goes through, and\n  the result has `replaced` (from and to version). Tell the person their\n  earlier version was replaced and can be rolled back.\n\nA second site for the same project (staging, a client copy) is an extra entry:\n`create_website`, then `webly link \u003CwebsiteId> --as staging`; `--to staging`\npicks it. Without an account a machine has one anonymous site, so extra\nentries need sign-in. If the file is lost, re-link the same way: `list_websites`,\nconfirm with the person, `webly link`. A file the helper can't read is never\noverwritten: fix it or delete it.\n\n## Share files (no website)\n\nWhen the person wants to send or share files (a video, PDFs, a dataset,\nphotos) rather than publish a site:\n\n1. If there is more than one file, ask whether they want **one link per file**\n   or **one folder link** (a page listing every file with *Download all*\n   as .zip). Both come back either way; you only choose what to show.\n2. Without an account: `webly upload \u003Cfile|folder>… [--folder name]`. It prints\n   each file's link, the `folderUrl` and the `zipUrl`. A `--folder` name gets\n   a random suffix (`demobowling-3f9a2c1b5e7d90a1c2b4`) so the link can't be guessed: share\n   the printed links, never one you built from the name. A folder keeps its\n   subfolders and hidden files (`src\u002Fmain.cpp`, `.gitignore`); only `.DS_Store` is left out. Over 500 files it uploads them as one zip archive, served as a folder. Every\n   run is a new folder with its own links, so there is no limit on links: only\n   500 MiB in total per machine, **the website included** (`status` shows\n   `storage.usedBytes` of `limitBytes`), 100 MiB per file. Sharing files works\n   whether or not this machine already has a website and never touches it. The\n   links work for 24 hours and must be claimed within those 24 hours\n   (**Keep the site**, which keeps the website and the files together) or the\n   files are deleted; sharing again after that starts a new 24 hours.\n3. Signed in (MCP): `create_website` with `kind: \"storage\"` once, then\n   `begin_object_upload` with each file's name and exact byte size, run each\n   returned `command` after setting `FILE=.\u002Fpath;` (an inline `FILE=… command`\n   doesn't work: the shell expands `$FILE` first), then\n   `finalize_object_upload`. To keep a folder's structure, name each file by\n   its path inside it (`src\u002Fmain.cpp`) and include hidden files (`.gitignore`, `.idea\u002F…`); never flatten a folder or drop its hidden files. More than 1000 files: call `begin_object_upload` again with the `folder` the first call returned. Free keeps files up to 7 days (1 GB, 100 MB per\n   file); Hobby and Pro can keep them forever (50 \u002F 200 GB, 2 GB per file).\n   Never put file bytes in a tool call.\n\nOnly images, video, audio, PDF and plain text open in the browser; anything\nelse downloads. Tell the person when the links stop working (`expiresAt`).\n\nManaging shared files over MCP (the dashboard's Files page does the same):\n\n- `list_objects` lists files with their `folder`, `folderLabel` and `scan`.\n  Files go live at once and Webly scans them shortly after. `scan.status`\n  `flagged` (the file's `status` is `quarantined`) means it was blocked as\n  malware or a program named like a document: its link stops working and it is\n  deleted at `scan.deletesAt`. Tell the person which file and why; they can\n  delete it or appeal by writing to abuse@webly.ai before that date. A `clean`\n  file with reason `executable:*` is an honestly named program: mention it when\n  sharing.\n- `rename_object` \u002F `label_folder` change only the name shown; links stay the\n  same, so they are always safe.\n- `move_object` moves a file into another folder (or, with no folder, gives it\n  a link of its own). **Its link changes and the old one stops working**: say\n  so first, then share the new `url`.\n- `delete_object` \u002F `delete_folder` delete for good. Confirm first.\n- **Passwords (Hobby and Pro), only when the person asks.** `set_folder_password`\n  (or `password` on `begin_object_upload`) protects a folder link, its files,\n  subfolders and zip; `set_website_password` protects a whole site on every\n  address, draft included. Webly keeps only a hash, so tell the person the\n  password with the link; `null` removes it. On `402 plan_required`, give them\n  `details.upgradeUrl`.\n- `email_link` emails a folder or file link (or a site's published or draft link) to\n  up to 10 people with an optional plain-text message (Hobby and Pro). Webly\n  builds the link; confirm the recipients with the person first. For a\n  protected link, pass `password` only if the person wants it in the email.\n- **Big folders (more than 500 files): upload one zip as an archive.** Zip the\n  folder (paths inside the zip become the folder's paths), then\n  `begin_object_upload` with that single file and `archive: true`, run its\n  `command`, `finalize_object_upload`. The folder link, subfolder pages, every\n  file's link and *Download all* work as for any folder, served from inside the\n  zip without unpacking (*Download all* is the zip itself). `list_objects` shows\n  it as one item with `archive: { files }`; `list_archive_entries` lists the\n  files and their links. An archive folder is read-only: no more files go in,\n  and its files can't be renamed, moved or deleted one by one (delete the\n  folder instead). Zips must use stored or deflate entries, without encryption.\n- If an upload is interrupted (dropped connection, a part that keeps failing),\n  `resume_object_upload` returns what already landed and URLs for only the\n  missing parts; run those, then `finalize_object_upload`. Do it within the\n  hour: unfinished uploads are cleared after an hour with no activity.\n- Finalizing a big file (hundreds of MB) can take a minute or more. If\n  `finalize_object_upload` times out, or a file comes back with\n  `finalizing: true`, call it again every few seconds until it's ready. Never\n  cancel or re-upload a file that is finalizing.\n- `list_uploads_in_progress` shows unfinished uploads and their progress;\n  `clear_uploads_in_progress` cancels them to free the in-flight allowance\n  (Free 1 GB, Hobby 5 GB, Pro 10 GB). Ask first.\n- Starting the same file over and over is limited (5 quickly, then 5 an hour,\n  `429 upload_retries`): resume instead of starting again.\n- `get_billing` shows `storage.used` (finished files, including site assets)\n  and `storage.uploading` against their limits, like the dashboard's bar.\n\nSite assets (photos and files a website uses, not storage files): their `url`\nis served through the site, `\u002F_webly\u002Fimg\u002F{assetId}`; use that path in pages.\n`delete_asset` archives (the link keeps working and it still counts toward\nstorage); `delete_asset` with `permanent: true` deletes it for good and frees\nthe space, and pages that still use it break, so confirm first.\n\n### What to tell the person\n\nPut the URL on a line by itself, with nothing after it, so it stays clickable.\nThen the deadlines, from the JSON, in their time zone if you know it:\n\n> Your site is live:\n>\n> https:\u002F\u002Fanon-….webly.site\u002F\n>\n> It stays online for 24 hours (until {liveUntil}) and I can keep changing it\n> until then. To keep it for good, sign in to Webly and claim it before\n> {claimUntil}; after that it's deleted. Want me to set that up now?\n\nOffer the claim once per site, not after every edit. Never show the token or\nthe contents of `~\u002F.webly\u002F`.\n\n### Errors (`details.reason`)\n\n| Reason | Means | Do |\n|---|---|---|\n| `site_already_created` | This token already has a site | `webly deploy` updates it; use `replace` only for a new URL |\n| `edit_window_closed` (410) | 24 hours are up; offline but claimable | **Keep the site** |\n| `build_failed` (400) | A swap's new site didn't build; the old one is untouched | Fix the files, retry |\n| `network_limit` (409) | 50 live anonymous sites on this network | Wait `details.retryAfterSeconds`, or sign in |\n| `credential_consumed` \u002F `credential_expired` | Token is dead (claimed, or past 7 days) | The helper already deleted it; the next deploy starts fresh |\n| `invite_only` (503) | Anonymous publishing is switched off | Sign in instead |\n| HTTP 429 | Rate limited | Wait for `Retry-After` |\n| `anonymous_storage_limit` (413) | The 500 MiB (website and files together) is used up | Claim (**Keep the site**) to get a free account's 1 GB |\n| HTTP 413 | Over a size limit | Trim files, or sign in |\n\n## Keep the site: sign in and claim\n\nRun this when the person wants to keep the site, make an account or sign in, or\nwhen `next.actions` is only `[\"claim\"]`. Say what will happen: a browser page\nopens, they sign in (Google) and approve access, and the site moves into their\nown workspace.\n\n1. **Register the MCP server** for this host, at user scope so it survives new\n   sessions and other folders:\n   - Claude Code: `webly connect claude` (installs the Webly plugin, or falls\n     back to `claude mcp add --scope user`).\n   - Codex: `webly connect codex`.\n   - Other hosts: follow https:\u002F\u002Fwebly.ai\u002Fagent.md, Phase 2.\n   - **No browser here** (a phone or hosted assistant such as Muse): if your\n     app has its own connector screen, have the person add\n     `https:\u002F\u002Fapi.webly.ai\u002Fv1\u002Fmcp` there and sign in through it. If it only\n     takes an API key: they open **Connect agent** in the dashboard and paste\n     its prompt; you open its `\u002Fconnect\u002F\u003Ccode>` link and the answer contains\n     your key, once: save it in your secure credentials, never the chat\n     (agent.md, Phase 3b). Expired? Give them the renew link it returns. To claim without a\n     browser, print `webly claim-link` (no `--open`) for them to open on their\n     phone: keys can't claim.\n   `connect` also records `pending: claim`, so the claim is finished by\n   whichever session loads the tools first. Its `next` field says what to do.\n2. **Use MCP if it's already callable; otherwise claim in the browser now.**\n   Check whether a Webly `create_claim_code` tool is callable in this\n   session (search deferred tools). If yes, go to step 4. If not (the usual\n   case right after a first `connect`), **don't ask the person to reload or\n   restart**. Run `webly claim-link --open` straight away. It opens\n   `app.webly.ai\u002Fclaim` with the token in the URL fragment (never sent to a\n   server, never printed). Ask them to sign in and click **Claim website**. If the\n   page shows the wrong Google account, **Not you? Use a different account**\n   switches it.\n   Opening the page or signing in alone does not claim the site. API keys\n   cannot claim; don't retry a missing tool or replace their MCP config.\n3. **Confirm the browser claim.** After they say they're done, run\n   `webly doctor`: only `siteError.reason: credential_consumed` confirms the\n   token was claimed (doctor removes the spent token and clears pending). If\n   it is still unclaimed, the browser was closed, or status is unavailable,\n   keep the token and pending step so they can retry. Never run `forget`\n   merely because the browser opened. MCP loads by itself next session\n   (Codex: `codex mcp login webly` first). Stop here; steps 4-5 are the MCP\n   path.\n4. **When the tools are loaded:**\n   - Claude Code: call the server's `authenticate` tool\n     (`mcp__plugin_webly_webly__authenticate` or `mcp__webly__authenticate`;\n     load it with tool search if it's deferred). It returns an authorization\n     URL. Open it for them (`open \"\u003Curl>\"` on macOS, `xdg-open` on Linux,\n     `start` on Windows) and print it as a fallback. The callback completes by\n     itself.\n   - Other hosts: call `whoami`; the 401 starts the host's own sign-in.\n   - First they choose where you can work: **All my workspaces** (the\n     default; tell them to keep it unless they want you limited to one) or a\n     single workspace. Either way you get only what their role allows in each.\n   - The consent page offers `webly:content`, `webly:edit` and `webly:admin`\n     and defaults to `webly:admin`, which creating sites needs. Tell them to\n     keep it unless they only want you editing existing sites (`webly:edit`).\n5. **Claim:** call `create_claim_code`, then run `webly claim \u003Ccode>`. The\n   helper sends the code and the saved token to Webly itself, so you never\n   read the token, and on success it deletes the token and the pending step.\n   Tell them which site moved and give the printed `dashboardUrl`. A retry by\n   the same person is safe (`alreadyClaimed: true`). The code lasts 10\n   minutes; get a new one if it expired (`claim_code_invalid`).\n\nAfter the claim: with billing off, or on a paid plan with a free slot, the site\nis permanent. On the Free plan with billing on it's *held*: editable until the\noriginal 24-hour mark, then offline until they upgrade (`402 claim_held`). Say\nwhich one the response shows (`website.claimHeld`); don't promise permanence.\n\n## Working over MCP (signed in)\n\nCall `whoami` and `list_websites` first, and continue an existing site (the\nfolder's linked one, if `doctor` shows a link) rather than creating a second\none. After `create_website` for a project on disk, run `webly link\n\u003CwebsiteId>` in the project folder so later sessions find it.\n\n**Workspaces.** `whoami` → `workspaces: \"all\"` means this connection works in\nevery workspace your person belongs to. `list_workspaces` names them with their\nrole in each. A site id works in any workspace, so site tools need nothing more.\nTools that act on a whole workspace (`create_website`, `list_websites`,\n`get_billing`…) take its slug as `workspace`. If they have several, ask which\none before creating a site, and on `400 workspace_required` ask; never guess.\n`workspaces: \"one\"` means the connection is limited to one workspace. If they\nneed another (`list_workspaces` shows `canUse: false`), they reconnect: in\nClaude Code `\u002Fmcp` → webly → re-authenticate, and pick All my workspaces.\nWhen the owner asks about the \"Made with Webly\" badge: Hobby and Pro sites go\nwithout it unless they opt in. `set_workspace_badge` turns it on or off for every\nsite, new ones included; `update_website` with `showBadge` sets one site, and that\nalways wins (`null` follows the workspace again). Free always shows it: on\n`402 plan_required`, give them `details.upgradeUrl`.\n\nWhen the owner asks for a team workspace photo, `set_workspace_photo` takes a\npublic image `url` or the file as `base64` (PNG, JPEG, WebP or GIF, 2 MB);\n`remove_workspace_photo` clears it. A personal workspace shows the person's own\nprofile photo, which they change in the dashboard.\n\n**REST without MCP** (scripts, hosts with no MCP): `webly login` opens the\nbrowser to the same sign-in and workspace choice, then `webly api GET \u002Fwebsites\n--workspace \u003Cslug>` (or any `\u002Fv1` path, `--data` for a JSON body) calls the API\nas the person. The token stays in the helper; never ask for it or print it.\n`webly logout` revokes it.\n\n1. Framework sites (typed React, the default): `put_source_file` \u002F\n   `str_replace` (no lease needed). Static sites: `search_source` and\n   `str_replace` with `{ path, edits }` for small text edits; `deploy_files`\n   only for a few small whole files, with `expectedHeadVersion` set to the version\n   `read_source_files` returned (`400 base_required` without it). If someone\n   wrote since, your change is merged onto theirs (`merged` in the response);\n   `409 merge_conflict` means you both changed the same lines: tell the person\n   whose change it is (`theirsBy`), re-read, re-apply, resend. `force` only\n   when the person asks. For a folder on disk (a build's `dist\u002F`, anything with\n   bundles or images), call `begin_deploy` with the site's id and straight away\n   run `webly deploy \u003Cfolder> --ticket \u003Cticket> --message \"\u003Csubject>\" --body\n   \"\u003Cwhat changed and why>\"` (the ticket lasts 5 minutes and one deploy; never\n   echo it back to the person). Every write (deploy, `put_source_file`,\n   `str_replace`, deletes) takes a message, written like a git commit message:\n   a subject line of what changed, about 50 characters, imperative (\"Show\n   yearly plans first on Pricing\"), then a blank line and a body in plain words\n   for the site owner: what changed and why, which pages, anything to check.\n   The site's History shows the subject, and the body when someone opens the\n   version, so the people sharing the site can tell your version from\n   everyone else's. Skip the body only for a trivial change. The helper builds the project\n   if needed, uploads it (up to 2000 files; images and video over 1 MiB go\n   straight to storage, up to the plan's per-file limit), links\n   the folder and prints the draft URL. Never put a bundle's bytes in a tool\n   call or an API key in a shell command. If it stops with **`would_revert`**,\n   the deploy would undo changes made to the site since this folder last\n   deployed it (the paths are listed): read them with `read_source_files`,\n   merge them into the local project, rebuild, and deploy again with a new\n   ticket; or tell the person what would be undone and, only with their OK,\n   deploy with a new ticket and `--force`. If it stops with **`would_remove`**,\n   the site has files the folder doesn't (listed): add them to the folder, or\n   only with the person's OK deploy with `--force`. A clone of the site's git\n   mirror (`get_git_access`) deploys the same way: the helper keeps the images\n   listed in `.webly\u002Fmedia.json` and takes its base from the git history; when\n   it says the clone is behind, `git pull` first. If the result has `replaced`, tell\n   the person the site had changed elsewhere and earlier versions are kept. Each write\n   makes a new draft version; the live site doesn't change. Writes are\n   Prettier-formatted, so copy `str_replace` text from `read_source_file`.\n2. `check_head` runs the quality gate (lint, typecheck, bundle, render). Fix\n   every diagnostic.\n3. Show the person the draft URL (`https:\u002F\u002Fdraft--{subdomain}.webly.site`, not\n   public, not indexed).\n4. `publish_website` only after they say yes to that exact site and version.\n   It waits for a running build; `202` with `status: \"building\"` means Webly is\n   still building (not a failure): publish that version again in about 15\n   seconds, and tell the person it's still building.\n   `rollback_website` \u002F `unpublish_website` if something is wrong live.\n\nNew sites get a short generated address (`zen-wreath-y76r.webly.site`); don't pass\n`subdomain` unless the person asks for a specific one (up to 56 characters; a taken\none is a `409`, not a variant). On Free each site can change its webly.site\naddress once (`rename_subdomain`; Hobby and Pro unlimited), so run\n`check_subdomain` first and rename only to the exact name the person asked for.\nOn Hobby and Pro the workspace also has a namespace\nand each published site answers at `urls.vanity`\n(`https:\u002F\u002Ffall-out-boy.kev.webly.site`, the label from the site's name, unique only\nwithin the namespace). Share `urls.primary`: the primary address (a custom domain\nwhen one is live, else the vanity, else the flat address, unless the owner chose a\nwebly.site address as primary); `urls.all` lists every\naddress the site answers at. `rename_vanity`\nchanges a site's label; `get_namespace` \u002F `check_namespace` \u002F `rename_namespace`\nhandle the namespace. Renames are scarce (Hobby 5, Pro 10, lifetime), so rename\nonly to the exact name the person asked for, and tell them old vanity addresses\nstop working. The new addresses need about a minute for HTTPS: check\n`get_namespace` until `certificate` is `active`, then tell them they're live.\nOn `402`, give them `details.upgradeUrl`.\n\nA team workspace has one owner (`whoami` → `owner`). Ownership of the workspace\nitself (not moving a website) changes only in the dashboard's People page, by the\nowner; you can't do it, so send them there. The card and subscription stay with\nthe workspace.\n\nNew content, including blog posts and repeating content (products, team, FAQs),\ngoes in the site's source files; don't create collections or blog posts, the CMS\nis deprecated. A site that already reads collections or a managed blog keeps\nusing those tools for that content until the owner asks to move it. Forms\npost with `formAction('name')`, never `mailto:`, and never ask for card\nnumbers, passwords, ID numbers or health details (submissions are plain text).\nIf the owner wants an email per submission, turn it on with\n`set_form_notifications` (off by default). Emails go out on Hobby and Pro;\non Free the choice is saved: give the owner `upgradeUrl`. Name the email\nfield `email` so replying to an alert answers the visitor. Each workspace takes\n1,000 submissions a month on Free (10,000 Hobby, 100,000 Pro); past that they're\nheld: hidden, no alerts, and deleted at the monthly reset unless the owner\nupgrades. When `list_forms` shows `quota.held`, tell the owner and give them\n`upgradeUrl`.\nDetails are in llms.txt.\n\n`403` names the missing capability in `details.capability`: the grant was\nnarrower than the task, so tell them which access level covers it. `401` \u002F\n`invalid_token`: call a Webly tool again to re-trigger sign-in; don't start a\nsecond attempt while one is waiting. Other people and agents may edit the\nsame site at once, and people may edit text, styles, layout,\nsections, new elements and images, pages and brand colours, and component props in the dashboard, on static sites too (History shows them as Editor), so re-read a file before editing it. On a static site the editor's classes compile into `\u002Fwebly.css`, linked from each page that uses them: keep that file and its `\u003Clink>`. Prefer `str_replace` for small edits. Send `baseVersion`\n(the `version` your read returned) with `put_source_file` \u002F\n`delete_source_file`: their edits to other lines are merged with yours;\n`409 merge_conflict` means you both changed the same lines — read the file\nagain, re-apply your change keeping theirs, resend with the new version.\n`wait_for_changes` shows what others wrote since a version. Publish with\n`version` set to the one the person previewed. History is linear, so the\nversions between the last publish and that one go live with it (newer ones stay\nunpublished); the response's `alsoPublishes` lists the ones other people or\nagents wrote (who, app, message). Tell your person what of theirs went live.\nPublishing an older version puts nothing new live, and `alsoPublishes` is empty.\nTo help someone choose a version: `list_changes` and `diff_source_file` (from the\nversion before it) show what it changed, and `preview_version` gives a private link\nto how it looked for an hour, changing nothing.\n\nGit: `get_git_access` gives a read-only clone of a signed-in site's source and\nhistory (one commit per version). Its token lasts one minute, so run its\n`clone` (or `pull` inside the clone) straight away as\n`WEBLY_GIT_TOKEN=\u003Ctoken> \u003Cclone>`, never with the token in the URL. Check `headVersion` with `get_website`\nbefore asking again. Never `git push`; write through the tools.\n\n### Turn a static site into a React site (or back)\n\nCreate a new site of the other kind and port the pages yourself: components,\nand React state for what scripts did (or plain HTML and small scripts the\nother way). Leave the original untouched until your person is happy with the\nnew one.\n\n### Duplicate or move a site\n\nHobby and Pro, in both workspaces (`402 plan_required` otherwise: give the\nperson `details.upgradeUrl`). `duplicate_website` copies a site 1:1: every\nversion, media, CMS, form submissions and settings, passwords; it is published\nif the original is (`publish.status: \"building\"` means a bigger site is still\nbuilding and goes live by itself: tell your person it is still working), gets its own addresses, and custom domains stay with the\noriginal. `move_website` moves a site into another workspace your person\nadmins, at once: everything comes along, including its webly.site address and\ncustom domains, except form email alerts: their recipients are cleared, so set\nthem again there (`set_form_notifications`). Its vanity address changes to the\nnew workspace's and links to the old one stop working, so confirm first and\nshare `urls.primary`. `list_move_destinations` lists the workspaces your person\nadmins and whether the site fits (`reason`: `site_limit`, `storage_limit`,\n`plan_required`); ask which one. Both need a signed-in person (OAuth) to reach\nanother workspace. To give it to someone else, ask for their email and call\n`start_website_transfer { toEmail }`: they're emailed and it waits on their\nTransfers page, where they accept or decline it (or their agent:\n`list_incoming_transfers`, `accept_website_transfer { transferId }`,\n`decline_website_transfer`). There are no transfer codes.\n\n### Custom domains\n\nNeeds a signed-in account (MCP) on Hobby (5 domains) or Pro (25). On Free,\n`add_domain` is `402 domain_limit`: give the owner `details.upgradeUrl`.\n\"Connect example.com to my site\":\n\n1. Pick the site with `list_websites`. Never guess it from the hostname.\n2. For a bare domain, ask first:\n   - **`www.example.com` (recommended).** It works with every DNS provider.\n     The person then forwards `example.com` to it at their registrar, which is\n     free and takes a minute, but usually http-only (see `apexForward` below).\n   - **`example.com` directly.** Only if their DNS provider supports CNAME\n     flattening or ALIAS at the root (Cloudflare, Namecheap, Porkbun…).\n   For a subdomain such as `shop.example.com`, just add it.\n3. Call `add_domain`, then `connect_domain`. If it returns a `url`, give the\n   person that link first: they sign in at their DNS provider (Cloudflare for\n   any hostname; GoDaddy and others for www once they support it) and approve,\n   and the records are set for them. They open it in the browser where they\n   use Webly. With Cloudflare (`method: \"oauth\"`) Webly also forwards the\n   bare domain of a www domain if they allow redirects on Cloudflare's screen\n   and nothing is served there yet (if `apexForward` isn't ok after\n   verifying, give it to them). If records of theirs are in the way, nothing\n   is replaced until they approve the exact changes shown after signing in;\n   approving switches the hostname at once, so for a site live today offer the\n   manual records (TXT first) to move without downtime. When you\n   `remove_domain` and the response has `dnsCleanup`, ask whether to delete the\n   records Webly added too, and if yes give them `dnsCleanup.url`.\n   Otherwise (name.com, Squarespace, Google and most other providers), or as\n   the fallback, give **every** required `dns.records` entry **exactly as\n   returned**, as a Type \u002F Name \u002F Value table: the CNAME **and** the\n   `_acme-challenge` TXT records. The TXT issues the HTTPS (SSL) certificate\n   and is always needed; without it HTTPS can take hours. If it isn't in\n   `dns.records` yet, call `verify_domain` a few seconds later and give it then.\n   For a www domain, also give the `apexForward` forwarding rule (URL\n   forwarding at their registrar makes the bare domain work too, usually over\n   plain http only; for `https:\u002F\u002F` links, a provider with ALIAS can add the\n   bare domain as a second domain on the site: TXT records first, the ALIAS\n   once it's active). Check it with `verify_domain` (`apexForward.ok`,\n   `apexForward.https`), not in a browser: Chrome quietly retries a bare\n   domain with `www`. Provider tips:\n   - Type only the Name shown (`www`, or `@` for the root). GoDaddy and\n     Namecheap add the domain themselves.\n   - On Cloudflare, set the record to \"DNS only\" (grey cloud).\n   - Moving a domain that is live elsewhere? Keep its current record and add\n     only the TXT records (the certificate ones and the optional ownership\n     one). Then:\n     1. Poll `verify_domain` until the domain is `active`. That means ownership\n        is verified and the certificate is deployed. Step 2 isn't enough.\n        `domain-watch` can't show this yet, because the old host still answers.\n     2. Ask the person to switch the CNAME.\n     3. Run `webly domain-watch \u003Chostname>` to confirm traffic now reaches\n        Webly.\n4. Start watching in the background right away. Don't wait for the person to\n   say they're done:\n   `webly domain-watch \u003Chostname>` as a background task. It prints `dns`,\n   `https` and `live` as each happens and exits once the domain is live.\n   Without a shell, call `verify_domain` every `next.checkAgainSeconds`.\n   Every domain response has `next` with the step (1 DNS record, 2 HTTPS\n   certificate, 3 live) and what to do. Tell the person when each step\n   completes.\n5. Once live: confirm `https:\u002F\u002F\u003Chostname>` loads. The first domain to go live\n   on a site becomes its primary address by itself (`isPrimary`), unless a\n   primary was already chosen (another domain, or a webly.site address picked\n   with `set_primary_address`); every other address redirects to the primary.\n   If another domain is already primary, offer\n   `set_primary_domain` to switch, or `set_primary_address` if they want a\n   webly.site address to be the primary (their custom domains then redirect\n   to it; say so). If it's\n   `failed`, relay `failureMessage`, have them fix the record, then call\n   `verify_domain` again. If the domain is active but their browser says the\n   server \"could not be found\" right after removing and re-adding it, their\n   DNS cached the gap: it clears within the zone's negative-cache time (30\n   minutes by default on Cloudflare), or sooner if they flush their DNS cache and\n   the stale answer was cached on their device (not by their router or ISP).\n\nAdding a domain publishes nothing and takes nothing offline. The\n`*.webly.site` address keeps working.\n\n## Rules\n\n- The token is a secret that proves ownership. Never print it, log it, commit\n  it, or put it in a URL other than through `webly claim-link`.\n- Only state URLs, sites and counts that a command or tool actually returned.\n- Don't set up MCP for someone who only wants a quick link; offer it when they\n  want to keep or grow the site.\n- One anonymous site per machine. If they want a second site kept, claim the\n  first, then create the second over MCP and `webly link` it.\n- A folder belongs to the site in its `.webly\u002Fproject.json`. Never deploy it\n  to, or claim, a different site unless the person asks.\n",{"name":5,"license":15,"metadata":48,"description":7},{"docs":49,"homepage":50,"publisher":51,"mcp-server":52,"api-contract":53},"https:\u002F\u002Fapi.webly.ai\u002Fdocs","https:\u002F\u002Fwebly.ai","Webly","https:\u002F\u002Fapi.webly.ai\u002Fv1\u002Fmcp","https:\u002F\u002Fapi.webly.ai\u002Fllms.txt","main","cebc3dce495d7eb80d3b1d5841f877a4a92e162d","plugins\u002FWebly-AI\u002Fwebly-plugin\u002Fskills\u002Fwebly",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill webly",{"tool":70,"command":71},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill webly",{"tool":73,"command":74},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill webly","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FWebly-AI\u002Fwebly-plugin\u002Fskills\u002Fwebly\u002FSKILL.md",true,[78],{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"scripts\u002Fwebly.mjs","SCRIPT","脚本",82190,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FWebly-AI\u002Fwebly-plugin\u002Fskills\u002Fwebly\u002Fscripts\u002Fwebly.mjs",[85,95,103,111,119,127],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":89,"licenseFileUrl":90,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":94},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":89,"licenseFileUrl":99,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":94},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":89,"licenseFileUrl":107,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":94},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":89,"licenseFileUrl":115,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":94},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":89,"licenseFileUrl":123,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":94},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":89,"licenseFileUrl":131,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":94},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]