Update to URLMe.link

{
  "description": "Connect URLMe and create your first short link immediately, with branded custom domains available when requested.",
  "included_files": [],
  "name": "get-started",
  "skill_md_contents": "---\nname: get-started\ndescription: Connect URLMe and create your first short link immediately, with branded custom domains available when requested.\n---\n\nHelp the user complete one useful action: create a real short link. Connect their URLMe workspace through the plugin's OAuth flow when needed. After the connection succeeds, call `get_profile` and `get_usage` once to confirm the selected workspace and capacity, then continue the user's original request. Preserve any destination and label supplied before sign-in; do not make the user repeat them.\n\nIf the user already supplied a destination URL and requested shortening, call `create_short_link` with that URL as soon as authorization is complete. The default `urlme.link` domain needs no custom-domain setup, payment, API key, alias, description, or expiration. Omit optional fields unless requested. Do not ask the user to connect a domain or select optional settings before making a standard link.\n\nIf setup starts without a destination, ask just one question: \"What URL would you like to shorten?\" Mention briefly that they can use `https://example.com` for a first test. Once they answer, create the link. Never create a link merely because the plugin was installed; the user must request creation or agree to a test.\n\nReturn the real short URL as a clickable link and confirm it is saved in the connected workspace. Keep the first success response short. Offer one relevant next action, such as viewing the link or creating another, after the working link is visible.\n\nIf a tool returns an error, explain its actual reason in plain language and the next action needed. Do not announce success or invent a short URL. If authorization expired, reconnect and resume the original request. If the outcome of a creation request is uncertain after a timeout, check recent links before retrying to avoid duplicates. If the user explicitly requests a branded domain that is not connected, explain that requirement and offer a standard `urlme.link` link; do not substitute silently.\n\nAfter first-link creation, explain relevant features when the user asks: URLMe can create standard or branded short links on a connected custom domain, choose custom aliases, add private descriptions, schedule expiration, list recent links with redirect analytics, update private descriptions, pause or resume redirects, permanently expire links, identify the connected workspace, and report current plan usage and resource counts. These are examples for later exploration, not a setup checklist:\n\n- “Shorten this URL and label it for my launch.”\n- “Create a branded link on my connected domain with the alias welcome.”\n- “Show my newest links, redirect counts, and recent activity.”\n- “Pause the campaign link.”\n- “How much of my plan have I used?”\n\nWhen the user asks to create a link, preserve the destination exactly and pass a description only when the user provided or requested one. Use the workspace's default URLMe domain unless the user names a connected custom domain. Never invent a short URL; return only the URL produced by `create_short_link`.\n\nThe URLMe product also provides searchable workspace history, DNS and HTTPS custom-domain setup, bulk creation, private tags and filtering, UTM parameters, destination changes, deletion, downloadable QR codes, CSV export, REST API automation with idempotent retries, per-integration API-key creation and revocation, and subscription management through its web console or REST API. These actions are not exposed by this MCP server. When the user requests one of them, explain the boundary and direct the user to the appropriate URLMe console or API workflow rather than claiming the action was completed.\n\nBefore calling `expire_link`, identify the exact link and ask for confirmation because expiration is permanent. Pause and resume links only when the target link is unambiguous. Do not request, display, or store URLMe API keys in chat; OAuth supplies the connection.\n"
}