Skip to main content
Meeting Skills let your AI agent load a focused set of instructions mid-conversation, follow them as a guided multi-step flow, and then drop them and return to its base persona. Think of a skill as a playbook the agent only opens when the moment calls for it — instead of stuffing every behavior into one ever-growing system prompt.

​
Why skills

Without skills, every capability an agent has lives in its prompt all the time. That causes two problems:
  • Over-eager behavior — the agent acts on capabilities when the user didn’t ask (e.g. creating a practice scenario because the user mentioned wanting to improve at something).
  • Prompt bloat — instructions for rarely-used flows dilute the persona’s core behavior on every single turn.
A skill fixes both. The base prompt carries only a one-line trigger. The full instructions load only when the skill is invoked, run as a step-by-step flow, and are revoked when the flow completes.

​
How a skill runs

1

Trigger

The agent recognizes a clear user intent that matches a skill — vague or ambiguous remarks never trigger one.
2

Invoke

The agent loads the skill. Its instruction pack activates, and any tools the skill controls unlock.
3

Guided flow

The agent follows the skill’s steps — confirming intent first, gathering what it needs one question at a time. If the user says “just do it,” the skill skips ahead.
4

Revoke

When the flow finishes (or the user declines), the skill unloads: its instructions stop applying, its tools re-lock, and the agent returns fully to its base persona.

​
Built-in skill: Create Scenario

The first built-in skill turns in-meeting scenario creation into a guided, consent-first flow. When a Plus One meeting has skills enabled and the user clearly asks to practice something:
  1. The agent confirms intent — “Would you like me to set up a practice scenario for that?”
  2. It gathers the essentials, one question per turn: who the persona should be, and what the situation is.
  3. It creates the scenario once, in the background, and keeps the conversation going while it builds.
  4. Only after the scenario is ready does it offer to bring the new persona onto the call.
At any point, “just create it” skips the remaining questions. If the user declines, the agent drops the subject — no scenario is created.
The create-scenario tool itself is locked until the skill is invoked. Even if the model tries to create a scenario cold, the platform refuses — the guided flow is enforced server-side, not just suggested in the prompt.

​
Bring your own skills

Custom, user-authored skills are on the roadmap. The authoring model below describes where this is headed.
A custom skill will be a small definition you create once and attach to any scenario:
  • Create once, attach anywhere — skills will live in your workspace and attach to scenarios like goals or knowledge-base documents do.
  • Instructions + tools — a skill can be purely behavioral (an instruction pack) or also grant access to tools (custom functions) that stay locked outside the skill.
  • Active next meeting — attaching or detaching a skill applies from the scenario’s next meeting.

​
Installing a skill package

Some skills come as a package: one file that holds the skill, the tools it calls, the screens it can show, and the events it wants to hear about. Under Developer → Skills → Installed packages, paste the file or give its URL, fill in any settings it asks for, and switch it on for the scenarios you choose. Everything it needs is created for you and removed again if you uninstall. Packages can also tell your agent things and put their screens up while a call is running, so the people who build them can keep improving what your agent does without you changing a prompt. Developers: see Skill Packages.

Custom Functions

The tools a skill can gate — connect your own APIs to the live conversation.

Multi-Agent Meetings

Skills coordinate with persona handoffs — created scenarios can join the same call.