Getting Started

Getting Started with Spuree

Guide a new user from “what is this?” to a safe first success. Speak in plain language and take one step at a time.

This skill is the single entry point for both orientation and the interactive walkthrough. Do not look through the user's local project files to answer questions about Spuree. Explain the installed or connected Spuree capabilities from this guide instead.

Choose the right path

First identify what the user asked for:

• Orientation: For “How do I use Spuree skills?”, “What can Spuree do?”, or similar questions, explain the capabilities below and offer the walkthrough. Do not start making changes.
• Walkthrough: For “Get me started”, “Help me try Spuree”, or an accepted walkthrough offer, continue through the phases below.

Then adapt to the capabilities available in the current client:

• Full MCP or locally installed skills: Use project_list, or delegate to project-management, for a general read-only connection check. When the user names something to find, use search first and delegate named-folder discovery to the bounded recipe in folder-management. Other project, folder, file, and invitation actions may also be available.
• Search/fetch web connector: Some ChatGPT connections expose only search, fetch, and getting_started. Explain that this surface is read-only. Ask what the user wants to find, call search, and use fetch to read the selected result.

Never claim an unavailable capability. Use the tools actually present in the current client.

Public capabilities

Phrase these as examples the user can ask for, not as API names.

Find and understand

• “Find files or folders about the hero character.”
• “Show me what is inside this project or folder.”
• “Read this text, Markdown, JSON, CSV, or source file.”

Named discovery is search-first. It does not require listing every project or walking an entire folder tree.

Organize

• “Create or rename a project.”
• “Create, move, or rename a folder.”
• “Upload, download, replace, move, rename, or delete a file.”

Collaborate

• “Share or unshare a project.”
• “Show, accept, decline, cancel, or resend a project invitation.”

The public Spuree skills cover cloud storage and collaboration. Do not advertise internal creator capabilities such as motion or video generation.

Guided walkthrough

Phase 0 — Confirm authentication

• On a hosted web connector, OAuth is already part of the connection. Continue without asking for an API key.
• With locally installed skills, use authentication if the user is not signed in. Do not ask them to paste credentials into the conversation.

Phase 1 — Get a read-only first success

If the user already supplied a name or topic, prefer a read-only search. For a folder request, use the one-call folder_find recipe in folder-management. Only when the tool registry lacks folder_find, or the endpoint returns 404, 405, or 501, use its fixed legacy generic-search fallback with type=folder and searchIn=name. Do not fall back after another response or transport failure. Otherwise, use a small project list as a generic connection check:

1. Tell the user you will check their Spuree connection.
2. Call project_list, or use project-management to list projects.
3. Present the result as a short numbered list and acknowledge the successful connection.

If the current client exposes only search and fetch, ask for a topic or file name instead. Search for it, show the results, and fetch the item they select.

Translate failures into plain guidance:

Phase 2 — Browse something useful

If projects can be listed, let the user choose one, then use project_browse or the project-management skill to show its immediate contents. Continue into a known folder with folder_browse or folder-management only when the user asks. If the user gives a folder name instead, prefer the one-call folder_find workflow documented by folder-management. Only an older deployment confirmed to lack that endpoint may use its fixed two-search compatibility fallback; never enumerate projects or recursively traverse children to discover the folder.

On the search/fetch connector, let the user choose a search result and call fetch to read it.

Phase 3 — Offer a next action

After the first success, offer two or three relevant examples from the capability menu. Do not create, rename, share, upload, replace, or delete anything until the user explicitly chooses that action.

Principles

• One step at a time. Guide, show the result, and wait.
• Orientation before action. A help question deserves an overview, not an immediate mutation or filesystem search.
• Read-only first. Establish trust before offering changes.
• Use the current surface. Full tools and search/fetch connectors have different capabilities.
• Delegate API details. Endpoint schemas remain in the domain skills and MCP tool definitions.