← Shika CloudCONTENT HISTORY

Update to Shika Cloud

Snapshot Nov 5, 2026 · 18:11 UTC · version 1.0.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Shika Cloud and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Connect a Shika Cloud workspace and get the first website building — pick the right site, confirm what it is for, and show a preview before going further.",
  "included_files": [],
  "name": "get-started",
  "skill_md_contents": "---\nname: get-started\ndescription: Connect a Shika Cloud workspace and get the first website building — pick the right site, confirm what it is for, and show a preview before going further.\n---\n\n# Get started with Shika Cloud\n\n## 1. Confirm the connection\n\nCall `get_account` first. It returns the account's sites, their status, and how\nmany site slots the plan has left.\n\n- If the call fails or returns no workspace, the connection is not authorized.\n  Ask the user to reconnect Shika Cloud from their ChatGPT plugin settings.\n- If the workspace is full, say how many slots are free and offer to continue an\n  existing site instead of creating another one.\n\n## 2. Choose continue or start fresh\n\nCall `list_sites` when the user has not named a site.\n\n- If a site's name or purpose matches the request, continue that one. Confirm\n  which site you are working on before writing files.\n- If nothing matches and the plan has room, call `create_site` once. Do not\n  create a second site for the same request.\n\n## 3. Learn what the site is for\n\nAsk a few grouped questions: what the business or organisation does, the name,\nthe town or service area, a phone or WhatsApp number, and what a visitor should\ndo first (call, WhatsApp, book, or send an enquiry).\n\nNever stall on a missing fact. Use a clearly marked placeholder and tell the user\nwhat is still needed.\n\n## 4. Build the first page\n\nCall `load_site_recipe` for the kind of site described, then build one complete\npage — usually the home page — before starting the rest. The preview updates as\nfiles are written; share the preview URL from `get_site` so the user can look.\n\n## 5. Finish deliberately\n\n- Keep phone numbers, prices, and locations exactly as the user gave them.\n- Create a form with `create_form` when enquiries or bookings are wanted, and\n  embed the URL it returns.\n- Run `run_site_check` before calling the site finished, and fix anything it\n  blocks.\n- Publish only when the user asks. `publish_site` refuses while the check is\n  blocked, so run the check again after fixes.\n"
}

SHA-256 of public snapshot: 83bf1098d31342b03966ad5c6e1edc6faf58d644b1b0d429a07c91ea2e1274d5