A skill is a reusable part of an agent: define a standard once — your ICP, your pricing methodology, a report format — and every agent that needs it follows it.
One skill, written once — a building block in every agent that needs it. Update the skill, and all three follow.
Your Ideal Customer Profile — every agent qualifies leads the same way.
Standardize a methodology
Your internal pricing methodology — defined once, applied identically by every agent that prices anything.
Define your data
What each metric or field means, and what it’s called in your systems — shared analytics language.
Standardize outputs
How a report should be structured and worded.
Lock the design
The look for documents and dashboards — always on-brand.
The signal that something should be a skill: you catch yourself typing the same definition or procedure into a second agent — “wait, I’m redoing this work.”Inside, a skill is just clear instructions — here’s a real one:
A skill from the inside: the ICP Scoring Methodology. Editable in chat or manually.
Two ways — out of an agent you already built, or from scratch:
From an agent's chat
From the Skills section
You built an agent and notice one part of it is reusable — just tell Dataleap: “Create a skill out of the scoring logic for new candidates.” It drafts the skill from what you built, proposes name, description, and content, and saves once you confirm.
One sentence in the agent's chat, and the reusable part becomes a skill.
Click Add Skill and pick how: Create in Chat, Create Manually, or Import Markdown (if the standard already exists as a document).
Add Skill: create in chat, write it manually, or import a Markdown file.
There’s no hard size limit on a skill — but every rule in it costs tokens on every run that loads it. Keep skills as lean as possible while still doing the job.
Agents don’t guess which skills to use — you tell them. When building or refining an agent, reference the skill explicitly:
“When it comes to pricing, use the Pricing Methodology skill.”
From then on, that step of the workflow runs on the skill’s definition. And when the methodology changes, you update the skill once — every agent using it follows.
Be proactive: Dataleap won’t suggest skills on its own. Spotting the reusable part is your job; packaging and reusing it is one sentence.
Team — share a skill into a team space (it has its own Skills tab); every teammate’s agents can use it.
Org-wide — publish it for the whole company. The classic case: company-wide metric definitions, so every agent anyone builds speaks the same data language.
The Skills section, grouped by reach: Personal, Team, and Org.
Watch: Skills
See how skills work in the product.
Skills vs. knowledge: knowledge files give one agent context (documents, facts — see Add knowledge); a skill teaches procedure and can be reused by many agents.
Programmatic tool calling
Next: cut costs on deterministic workflows.
Team spaces
Where team skills live.
⌘I
Assistant
Responses are generated using AI and may contain mistakes.
