Menu
Guide the user through setting up the Recall.ai API key for the Meeting Bot plugin.
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/vellum-ai/meeting-bot --skill meeting-bot-setupThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Based on SOC occupation classification
Showing SKILL.md
| name | meeting-bot-setup |
| description | Guide the user through setting up the Recall.ai API key for the Meeting Bot plugin. |
| metadata | {"emoji":"⚙️","vellum":{"category":"voice","display-name":"Meeting Bot Setup"}} |
Use this skill when the user needs to set up or fix the Recall.ai API key for the Meeting Bot plugin. This typically happens the first time they want to use the meeting bot, or when joining fails with a 401 authentication error.
Before asking the user for anything, check whether a Recall API key is already stored:
assistant credentials inspect --service meeting-bot --field api_key
If the output shows hasSecret: true, the key is already configured. If the command fails or shows no secret, continue to Step 2.
Tell the user:
Once the user has their API key, store it in the credential store. Ask the user to provide the key, then store it:
assistant credentials set --service meeting-bot --field api_key "<their_key>"
Never ask the user to paste the key directly in chat. Use the credential store prompt so the key is stored securely.
Tell the user the Meeting Bot is ready to use. They can now ask the assistant to join meetings by providing a meeting URL.
If the user's Recall workspace is in a region other than us-east-1 (the default), the plugin's config needs to be updated. The region is set in the plugin's config.json under the region field. Supported regions: us-east-1, us-west-2, eu-central-1, ap-northeast-1.