← Products

AI agents
⚙ Needs: a Vapi account and VAPI_API_KEY only for live API op…

Vapi Squad creation — multi-assistant voice AI orchestration

Design Vapi Squads — when one assistant suffices vs multi-assistant handoffs, member ordering, context engineering and safe update procedures

At a glance
What
Design Vapi Squads — when one assistant suffices vs multi-assistant handoffs, member ordering, context engineering and safe update procedures
Cost
Free
Needs
a Vapi account and VAPI_API_KEY only for live API operations (design and planning work needs neither) — the skill is guidance, not a hosted service
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

@
Created by: @vapiai
⌁

Install

Prerequisites: a Vapi account and VAPI_API_KEY only for live API operations (design and planning work needs neither) — the skill is guidance, not a hosted service Install "Vapi Squad creation — multi-assistant voice AI orchestration" for me. It gives my agent Vapi's official Squad creation guide: when to use a multi-assistant Squad vs a single assistant, handoff boundaries and member ordering, context engineering plans, version pins, and safety rules (never invent assistant IDs, explicit confirmation before live mutations). IMPORTANT: the repo states no license (the skill's own frontmatter claims MIT, unverifiable) — fetch from the link only, and reproduce nothing beyond the link. Repository: https://github.com/vapiai/skills/blob/main/create-squad/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "create-squad". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. provide my VAPI_API_KEY via the secure vault only if I want live API operations; nothing else — it's a guide). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.

?

Questions

How do I install a build?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.