BuyerTwin connections include more than a list of technical tools. They combine secure MCP access with bundled skills that help an AI use BuyerTwin context correctly for recognizable business tasks.
What is the difference between a capability, skill, and MCP tool? #
A capability is the business outcome a user wants. A bundled skill is the method the AI follows. An MCP tool is a specific read or controlled action available through the connection.
| Layer | Purpose | Example |
|---|---|---|
| Capability | Describes the user-facing result. | Evaluate messaging for a saved buyer. |
| Bundled skill | Defines how the AI should scope, retrieve, reason, and respond. | Evaluate Messaging. |
| MCP tool | Retrieves approved data or performs one controlled operation. | Load accessible buyer context required by the evaluation. |
Why skills matter #
A raw tool call can retrieve information, but it does not by itself establish a complete business workflow. Skills tell the AI how to resolve buyer scope, preserve meaningful differences, apply evidence boundaries, use writing guidance, and separate drafting from evaluation or knowledge updates.
Current bundled skills #
- Ask Buyers: Answer questions about one or more accessible buyers and selectively explore modeled reactions.
- Compare Buyers: Identify meaningful similarities and differences without flattening distinct buyer contexts.
- Create Buyer-Centric Content: Produce briefs, drafts, and revisions grounded in buyer context and applicable writing guidance.
- Evaluate Messaging: Diagnose supplied messaging before rewriting it.
- Prepare for a Sales Conversation: Build questions, proof priorities, objections, and stakeholder guidance.
- Update Buyer Knowledge: Check, preview, and govern candidate additions or corrections.
- Manage Writing & Voices: Retrieve, export, review, and propose changes to company or named-person guidance.
Tool access and permissions #
The tools available to a user depend on the connection, signed-in account, selected workspace, and permissions. A bundled skill cannot bypass those limits. Tool unavailability is not proof that data does not exist.
Read and change boundaries #
- Reading buyer context does not change shared knowledge.
- Creating content does not save that content into BuyerTwin knowledge.
- Exploring a buyer reaction produces simulation, not customer evidence.
- Evaluating supplied copy does not rewrite it unless requested.
- Proposing a buyer or writing-guidance change does not apply it.
- Applying a shared change requires the matching reviewed proposal and explicit approval.
For the business-oriented view, see BuyerTwin capabilities in your AI. For access and approval rules, see permissions, simulation, and knowledge updates.