Claude already knows how your CRM works.
Fourteen skill files that teach Claude the exact endpoints, field shapes and conventions of the Vetta API. Install them once and Claude stops guessing at your schema: it writes the correct request the first time.
- Two commands to install all 14
- Loads the right skill on its own
Terminal · claudeThe conventions
What every skill encodes for you.
Miss one and the call fails, Claude retries, and you burn a session on trial and error.
Currency
Amounts in micros: multiply by 1,000,000 ($50 becomes 50000000).
SELECT values
Must be UPPER_SNAKE_CASE.
Links
{ primaryLinkUrl, primaryLinkLabel, secondaryLinks: [] }
Person name
Nested object { firstName, lastName }, not flat fields.
Note and task body
bodyV2 with { markdown, blocknote }.
List responses
Wrapped as .data.people[], never a plain array.
Pagination
Cursor-based via starting_after, 60 records per page by default.
Read-only fields
Never set id, createdAt, updatedAt, position, createdBy.
The plugin also ships a Sales OS generator agent used during customer onboarding.
01Install
Two commands. Every skill.
The first command registers the Vetta plugin marketplace from GitHub. The second installs the Vetta plugin with all 14 skills. Restart when prompted, and they load automatically whenever they are relevant. Updates arrive through the marketplace, so you never re-download files.
- Add the marketplace with /plugin marketplace add
- Install the plugin, then restart when prompted
- Updates arrive through the marketplace
02Why it matters
The API has conventions that are easy to get wrong
Amounts are in micros. Select values are UPPER_SNAKE_CASE. A person’s name is a nested object. List responses are wrapped, never a plain array. Miss one and the call fails, Claude retries, and you burn a session on trial and error.
- Field shapes and formats encoded up front
- A Gotchas section in every skill
- Correct request on the first attempt
03Skills vs MCP
Knowledge, not tools. Use both.
Vetta MCP gives Claude tools: live, workspace-scoped operations it can execute. Skills give it knowledge: how the API is shaped and where the traps are. MCP lets Claude act on your workspace; skills make sure it acts correctly, and let it write working code against the REST and GraphQL API too.
- MCP: one URL, live operations
- Skills: two commands, correct calls
- In Claude Code, run them together
04Just ask
Claude picks the skill, the record lands in Vetta
Claude loads the right skill on its own based on the request, so you never have to name one. Ask it to add a contact and log what they asked for, and it reads the company, person and note-relation skills together, then writes each record correctly the first time.
- Company created, skill: company
- Person created and linked, skill: person
- Note attached to both, skill: note-relation
- 14
- skills covering every core object and API
- 2
- commands to install the whole library
- 0
- schema briefings before a session
On the route
Claude Skills works at every stop. From the first signal to the signed deal.
Questions
Claude Skills, explained
What is a Claude skill?
A reference file that teaches Claude how one part of the Vetta API actually works: the exact endpoints, required fields, data formats and the gotchas that cause silent failures. Installed once, it loads automatically whenever it is relevant.
How do I install them?
Two commands in Claude Code: /plugin marketplace add Vetta-AI/vetta-docs-and-skills, then /plugin install vetta@vetta-marketplace. That installs all 14 skills. Updates arrive through the marketplace, so you never re-download files.
What is the difference between Skills and MCP?
MCP gives Claude tools: live, workspace-scoped operations it can execute. Skills give Claude knowledge: how the API is shaped and where the traps are. MCP lets it act; skills make sure the call is right the first time. Use both.
Do I need both?
For live operations, MCP alone works and the client discovers the tools itself. Skills matter most when Claude is writing code against the REST and GraphQL API, or when you want fewer failed attempts inside an MCP session.
Can I install just one skill?
Yes. Copy the single SKILL.md file into your project’s .claude/skills/ directory. That also covers tools without plugin support. Every file is public on GitHub.
Do I need to be able to code?
No. The skills are for Claude to read, not you. You describe what you want in plain language; the skill is what stops Claude guessing at your schema while it does it.
Do they work outside Claude Code?
The plugin marketplace flow is Claude Code specific. Anywhere else, drop the SKILL.md files into the project directory your tool reads, and they work the same way.
Claude Skills
Stop explaining your CRM. Claude already read the docs.
Fourteen skills, two commands, and no more guessing at field shapes.
Demo with a founder · 14 skills, two commands · Cancel anytime