Update to sync. labs

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,31 +1,32 @@
 ---
 name: setup
-description: First-run setup for sync. labs after the plugin is installed. Confirms the connected account and its credits, shows what sync. labs can make, and walks the user to a first video. Use when the user runs setup for sync. labs or asks how to get started with it.
+description: Connect sync. labs (sync.so) to this agent and get a first lip-synced video. Use when the user explicitly asks to install, set up, connect or get started with sync. labs, when sync. tools are missing or signed out, or for questions about their sync. account, plan or remaining credits. Media requests go to their workflow skill, which links to the same connection steps.
+license: MIT
+compatibility: Uses the hosted sync. MCP server (https://mcp.sync.so/mcp) or a SYNC_API_KEY.
 ---
 
 # Set up sync. labs
 
-Gets a new user from install to a first result in about a minute. Setup itself never starts paid work.
-
-## Tools
-
-| Step | Tool |
-| --- | --- |
-| Account and credits | `get-account-context`, `get-account-usage` |
+Gets a new user from install to a first result in a couple of minutes. Setup itself never starts paid work.
 
 ## Steps
 
-1. **Account.** Call `get-account-context` and `get-account-usage`. Greet the user by their organization name and say what is available: credits, or the free allowance. Don't promote plans or pricing.
-2. **Choices.** Offer the four things sync. labs makes, with one example prompt each:
-   - **Make a photo talk:** "Make this photo say: welcome to my channel"
-   - **Lipsync a video:** "Lipsync my video to this audio"
+1. **Check the connection.** If sync. tools such as `account_get-context` are available, call `account_get-context` and `account_get-usage`, then go to step 3.
+2. **Connect.** Follow [references/connect.md](references/connect.md) for this client: the hosted MCP server with sign-in for most people, or an API key for scripts and CI. If the client needs a restart to load the server, say so and stop there.
+3. **Account.** Greet the user by organization name and say what's available: credits, the free allowance, or the plan's limits (`generationLimits.maxOutputDurationSeconds`, `generationLimits.concurrency`). Don't promote plans.
+4. **What it can do.** Offer these, one example prompt each:
+   - **Lipsync a video:** "Lipsync ./interview.mp4 to ./new-take.wav"
+   - **Make a photo talk:** "Make this portrait say: welcome to the team"
+   - **Make an AI clip talk:** "My Veo clip has no dialogue. Make the character say this line."
    - **Translate and dub:** "Dub this YouTube video into Spanish"
-   - **Fix spoken words:** "Change the price I said in this video to $49"
-3. **Fastest first win.** If the user isn't sure, suggest a talking photo, because it needs no upload. Create a character with image generation, write a one-line greeting together, and pick a voice. Then follow the talking-photo workflow: quote, get approval, create.
-4. **Hand off.** Once the user picks, continue with the matching workflow (talking-photo, lipsync-video, translate-and-dub or edit-dialogue) in this conversation.
+   - **Fix a few spoken words:** "Change the price I say in this video to $49"
+   - **Localize a campaign:** "Make these 3 ads in Spanish, German and Japanese"
+   - **Many videos at once:** "Lipsync each row of this CSV"
+   - **Build it into an app:** "Add sync. lipsync to my Next.js app"
+5. **Fastest first win.** If the user isn't sure, suggest a talking photo: one image and one line of text, no recording needed. Then follow the talking-photo skill: quote, get approval, create.
 
 ## Rules
 
-- Quote before every paid video and wait for approval.
-- If the account has no credits left, say so plainly and point to their sync. labs account; don't start a job that will fail.
-- Keep it short: one message for the account and the choices, then follow the user's lead.
+- Quote before every paid generation and wait for approval.
+- If there are no credits or free generations left, say so plainly and point to https://sync.so/billing/subscription. Don't start a job that will fail.
+- Keep it to one short message for the account and the choices, then follow the user's lead.