Claude Skills

Claude already knows how your CRM works.

Fourteen skill files that teach Claude the exact endpoints, field shapes and conventions of the Dalil API. Install them once and Claude stops guessing at your schema: it writes the correct request the first time.

Two commands to install all 14Loads the right skill on its own
Claude Codeone-time setup
> /plugin marketplace add Dalil-AI/dalil-docs-and-skills
> /plugin install dalil@dalil-marketplace
✓ 14 skills installed
add Syed at Net Express and log what he asked forRun
Claude, using the Dalil skills
company createdskill: company
person created and linkedskill: person
note attached to bothskill: note-relation
Net ExpressSyed Arfeen3 skills, no schema briefing
Install

Two commands. Every skill.

Run these in Claude Code
/plugin marketplace add Dalil-AI/dalil-docs-and-skills /plugin install dalil@dalil-marketplace

The first command registers the Dalil plugin marketplace from GitHub. The second installs the Dalil AI 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.

Only want one skill, or using a tool without plugin support?

mkdir -p .claude/skills/person curl -o .claude/skills/person/SKILL.md \ https://raw.githubusercontent.com/Dalil-AI/dalil-docs-and-skills/main/.claude/skills/person/SKILL.md

Browse every file on GitHub ↗ or grab them from the download page.

Getting set up

Installed in a minute, then invisible

Add the marketplace

Run /plugin marketplace add Dalil-AI/dalil-docs-and-skills inside Claude Code.

Install the plugin

Run /plugin install dalil@dalil-marketplace, then restart when prompted.

Just ask

Claude loads the right skill on its own based on the request. You never have to name one.

The library

Fourteen skills, one per job

Claude picks the right one based on what you ask, so you never have to name them. Ask it to attach a note to a deal and it reads the note and note-relation skills together.

CRM records7 skillsThe seven objects most work touches, including how to link them.
  • personPeople and contacts: create, search, update, delete
  • companyCompanies: domain, LinkedIn, address, employees, revenue
  • opportunityDeals: amount, stage, close date, contacts
  • taskTasks: title, due date, assignee, status
  • noteNotes with rich body content
  • task-relationAttach tasks to people, companies or opportunities
  • note-relationAttach notes to people, companies or opportunities
Data model3 skillsReshape the workspace itself, safely.
  • fieldCreate, update and delete custom fields on any object or pipeline
  • relationCreate and delete relation fields between objects
  • pipelineDynamic pipelines: discover endpoints, then read and write records
Automation and messaging3 skillsOutreach, workflows and the inbox.
  • sequenceBuild and run multi-channel outreach sequences
  • workflowCreate workflows and versions, activate them, trigger and read runs
  • inboxSearch synced email, LinkedIn and WhatsApp messages
Onboarding1 skillThe interview that sets a new workspace up.
  • crm-onboardingGTM interview that generates a customer’s personalized Sales OS

The plugin also ships a Sales OS generator agent used during customer onboarding.

Why 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
What the skills already knowand Claude otherwise guesses
amount: 50000000 // $50, in micros
stage: "IN_NEGOTIATION" // UPPER_SNAKE_CASE
name: { firstName, lastName }
body: bodyV2 { markdown, blocknote }
→ res.data.people[] // never a plain array
Without vs withsame request
No skillsWith skills
Currencysends 5050000000
Select valuessends "negotiation"UPPER_SNAKE
List responsereads .data[].data.people[]
First attemptfails, retriescorrect
Skills vs MCP

Knowledge, not tools. Use both.

Dalil 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
Two different jobs
MCPSkills
Gives Claudetoolsknowledge
Liveson the serverin your client
Setupone URLtwo commands
Needed foracting livewriting correct code
Together, in one session
Skill supplies the field shapesno schema briefing needed
MCP tool executes the changescoped to your workspace
Correct on the first attemptno failed retries
The conventions

What every skill encodes for you

CurrencyAmounts in micros: multiply by 1,000,000 ($50 becomes 50000000)
SELECT valuesMust be UPPER_SNAKE_CASE
Links{ primaryLinkUrl, primaryLinkLabel, secondaryLinks: [] }
Person nameNested object { firstName, lastName }, not flat fields
Note and task bodybodyV2 with { markdown, blocknote }
List responsesWrapped as .data.people[], never a plain array
PaginationCursor-based via starting_after, 60 records per page by default
Read-only fieldsNever set id, createdAt, updatedAt, position, createdBy
Set up Dalil MCP →View the repository ↗
14
skills covering every core object and API
2
commands to install the whole library
0
schema briefings before a session
FAQs

Claude Skills, explained

What is a Claude skill?

A reference file that teaches Claude how one part of the Dalil 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 Dalil-AI/dalil-docs-and-skills, then /plugin install dalil@dalil-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.

✓ 30 days for $9✓ Cancel anytime