Update to Spacefast

{
  "description": "Check the Spacefast connection and continue the user's task. Ask one short question when they have not said what they want to do.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 194
    }
  ],
  "name": "setup",
  "skill_md_contents": "---\nname: setup\ndescription: \"Check the Spacefast connection and continue the user's task. Ask one short question when they have not said what they want to do.\"\n---\n\n# Get started\n\nCheck the connection, then continue the user's task.\nUse the user's request and conversation so far. Continue an established task without asking them to repeat it. When they bring work to Spacefast to publish, start publishing that work.\n\nIf the task is unclear, ask one concise question and wait. For a fresh publishing conversation, ask: \"What would you like to build or publish?\" For another action, ask only for the missing detail. Use their answer to take the next step.\n\nKeep replies brief. Use these instructions as reference material. Do not summarize them or give a Spacefast overview or feature list unless asked. Mention setup, credentials, sharing, or troubleshooting only when needed for the current step.\n\nSetup alone does not authorize publishing, changing settings, or creating a monitor.\nKeep any authorization the user already gave for their task. Connecting Spacefast does not require them to repeat it.\n\n## Check the connection\n\nFor hosted MCP at `https://mcp.spacefast.com`, use the connection's configured authentication. A direct hosted connection uses the host's OAuth controls; a CLI proxy uses its existing CLI login. If authentication fails, direct the user to reconnect through that method.\nIf tools are unavailable, direct the user to the host's configured Spacefast connection controls.\nDo not ask for a token in chat. Do not report a working connection until a read succeeds.\n\nRead the connected account through the Spacefast API tools:\n\nEach Spacefast API operation is an MCP tool named by its operation ID, such as `getAccount`. Read its input schema and any advertised output schema, then send its declared JSON input directly; the host may find the tool through its own tool search. Use only tools advertised by this connection. Finish read-only preparation before generating changes. Preserve failed results and continuation instructions, verify each successful write with a read, and use returned images and files directly.\n\n1. Read the contract for `getAccount` and call it with `{}`.\n   For a user-supplied reference, add the optional `teamRef` or `spaceRef` field at the top level.\n2. Keep the complete operation result in the tool receipt. Check its returned status and\n   `result.ok`. Preserve a failed result and its next action. A completed receipt carrying\n   the operation result has its account payload at `result.data.data`.\n3. Report only the subject or account name and the relevant team names and IDs.\n   Use optional reference values only when their `status` is `resolved`.\n   Do not return the complete account payload or credentials.\n\nIf the connection's tools are unavailable, reconnect before checking account state.\nTools from another server are not part of this connection.\n\nConfirm the connected account or service identity in one short sentence. A service connection is not its creator's personal account.\nReuse the Space already established in the conversation. An ordinary publish does not need a Space chooser.\n\n## Host features when needed\n\nUse these only when the task needs them and the host or connected server advertises them:\n\n- The Space Library and mention picker can help the user select a Space.\n- If `choose_space` is available, use it when a choice is needed. Honor cancellation.\n- Plugin settings, HTML previews, and event subscriptions depend on host support.\n  Do not promise these features merely because this skill describes them.\n\nA selected Space supplies context. It does not authorize a write by itself.\n"
}