Community skillDraft — source instructions not independently live-testedAI & development

Vercel for Meta Muse

Community draft proposes: See your Vercel account, projects, and recent deployments.

Guide description: Read-only visibility into the user's Vercel account: who the token belongs to, all projects, and recent deployments for a project. Use when the user asks about their Vercel projects, deploys, or site status.

Community-authored Draft; OpenTools has not independently installed or live-tested this skill. Choose the Vercel token scope for the intended account/team. This draft reads projects and deployments; it cannot deploy, delete, or alter environment variables.

View original source ↗

How to set it up

Paste a prompt

Draft — these instructions come from the linked source and have not been independently live-tested by OpenTools.

Source maturity: 🧪 Draft: written from Vercel's public REST API docs; not yet live-tested end-to-end.

Before you start

  • personal token (per-user, vercel.com/account/tokens)

Steps

  1. Review the pinned connectors/vercel/SKILL.md and its listed files (SKILL.md, bin/vercel.py). This community draft has not been live-tested end to end.
  2. Before setup: Choose the Vercel token scope for the intended account/team. This draft reads projects and deployments; it cannot deploy, delete, or alter environment variables.
  3. Only if the Muse runtime supports pinned repository installs and the source-declared credential and host flow, try `bin/vercel.py me`. Report the actual response and verify one safe read before any writes.

Prompt to paste into Muse

Inspect this community skill: https://raw.githubusercontent.com/bluman1/muse-connectors/6e31fd44a71f9f28377a1460e64cd7483c3cce22/connectors/vercel/SKILL.md
Read its Files manifest. If this Muse account supports custom skill installation and secure credentials, install exactly those files; otherwise report that the setup is unavailable. Collect credentials through Muse's secure credential flow; never ask me for raw keys in chat. Run the skill's status check and report the actual result.

Account access: personal token from vercel.com/account/tokens via the secure credential flow (`credentials.request_api_access`)

Allowed hosts: api.vercel.com

Source status check: Source-proposed status check (not live-tested by OpenTools): `bin/vercel.py me`

A successful source status check may verify only configuration or credentials; it is not proof of a working end-to-end integration.

Services it connects with

These are the services the connector uses.

← Browse all Muse connectors