Skip to main content
Diagram: three agents side by side — Lead Qualifier, Outreach Writer, Pipeline Report — each with the same ICP Definition skill as a building block in its workflowDiagram: three agents side by side — Lead Qualifier, Outreach Writer, Pipeline Report — each with the same ICP Definition skill as a building block in its workflow

One skill, written once — a building block in every agent that needs it. Update the skill, and all three follow.

What makes a good skill

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:
An open skill showing the ICP Scoring Methodology with scoring criteria tables and an Edit dropdown offering Edit in Chat and Edit Manually

A skill from the inside: the ICP Scoring Methodology. Editable in chat or manually.

Create a skill

Two ways — out of an agent you already built, or from scratch:
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.Which agent you use decides who else gets it. Create a skill through a personal agent and it stays private to you. Create one through a team agent and it is still yours, but it is shared with that agent’s team as Can edit in the same step — so the agent can use it from your next message, and a teammate can ask that same agent to refine it.A skill built this way isn’t limited to instructions. Ask for a script, a template, or a long reference document alongside them and the agent packs those in as bundled files — the same way you later ask it to change them.
A chat where the user asks to create a skill out of the scoring logic and Dataleap drafts the Candidate Scoring Model skill

One sentence in the agent's chat, and the reusable part becomes a skill.

A skill’s instructions can be up to 256 KB, but that is far more than you want: every rule in a skill costs tokens on every run that loads it. Keep the instructions as lean as they can be while still doing the job, and move long reference material into a bundled file the agent only reads when it needs it.

Import and export skills

A skill doesn’t have to start in Dataleap, and it doesn’t have to stay there. Bring one in from a file, or take one out as a file — so a standard you already wrote somewhere else moves across without retyping.

Import a skill

In the Skills section, click Add Skill and choose Import Skill. Drag a file onto the dialog, or click Browse files. Dataleap takes .md, .zip, and .skill files up to 30 MB — including an Agent Skills ZIP exported from another platform. Nothing is saved yet. Review Skill Import shows what was found in the file — Name, Description, Bundled Files, and the Instructions — and lets you fix the name or description before anything is created. Skill names have to be unique, so if you already have one with that name, rename it here. Click Import Skill to save, or Cancel to drop it. These limits apply to what you upload: Go over one and the upload is refused with a message naming the limit, so nothing half-imports.

Export a skill

Open the skill, open its actions menu, and choose Export. You get a ZIP of the skill — its instructions and any bundled files — to archive, hand to someone outside your team, or load into another tool that reads the Agent Skills format.

Replace a skill’s contents with an upload

When a skill’s source of truth lives outside Dataleap, you don’t have to delete it and import a new copy. Open the skill, click Edit, and choose Upload. Upload Skill Content accepts the same files as an import, and you need edit access to the skill.
The Edit dropdown on a skill page with the options Edit, Edit in Chat, and Upload

Edit: rewrite the skill here, take it to chat, or upload a file that replaces it.

One upload replaces the whole skill — the instructions and the bundled files together — so you review it first, under Replace Skill Contents. That step names every bundled file the skill has but your upload doesn’t, and those files go when you confirm. Click Replace Contents to apply it.
Replacing is a swap, not a merge: your upload becomes the skill’s entire contents, and bundled files missing from it are removed. Use Export first if you want a backup.

Bundled files

A skill can carry files alongside its instructions, which keeps the instructions themselves short. On the skill’s page they sit behind Other Files, a row giving the number of files and their total size; open it to see each file’s path and size. The agent groups them into three folders: On the skill’s page you can download any bundled file, and edit the markdown ones in place if you have edit access. Other text files open read-only, and anything else is download-only.

Add or change bundled files from chat

The skill’s page lets you edit a bundled markdown file, but not add or remove one. To change which files a skill carries, either replace the lot with an upload, or ask the agent in chat:
“Add this report template to the Pricing Methodology skill, and point the instructions at it.”
The agent stages the files, then shows you the name, description, the full instructions, and the resulting list of bundled files, and waits for you to approve before saving.
Read that file list before you approve. The set you approve becomes the skill’s bundled files, so a file missing from the list is a file the skill loses.

Use a skill

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.

Share a skill

Skills have three levels of reach:
  • Personal — your own skills, visible only to you.
  • 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.
Skills you create in the Skills section start private. A skill you create through a team agent starts shared: it is listed under Your Skills as Shared, with that team set to Can edit. You stay the owner — to change that, open the skill’s actions menu, choose Share, and set the team to Can view and use or remove it.
The Skills section listing skills grouped into Personal, Team, and Org, with an Add Skill button and workspace filters

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.