Skip to main content
A skill is a set of written instructions for one kind of task, such as “build a weekly status report” or “clean up a spreadsheet before analysing it”. Each skill has a short description that says when to use it. Chat and agents read the descriptions of the skills they can use, and when a request matches one, they load its full instructions and follow them. A skill can also carry extra files: scripts the agent can run, and reference notes or templates it can read. Skills use the open SKILL.md format from agentskills.io, so you can write your own or import ones that others have published.
Skills are in Beta and turned on by default. An admin can turn them off for the whole organization under Workspace → Labs → Enable Skills (Beta). While it’s off, Your skills is hidden and chat and agents can’t use any skill.

​
Built-in skills

Every organization gets these skills. They are read-only, so you can open them but not edit them. An admin can switch a built-in skill off for everyone with its Available to agents toggle. No one else can change built-in skills.

​
Create a skill

1

Open Your skills

Go to Workspace → Your skills and click New skill.
2

Name it

Give it a Name in lowercase with hyphens, for example weekly-status-report. Names of built-in skills, such as pdf, are taken.
3

Say when to use it

Write the Description. Describe when the skill applies, not how it works. This is the text chat and agents read to decide whether to load the skill, so name the kinds of requests it covers.
4

Write the instructions

In the Content tab, write the steps the agent should follow. Markdown headings, lists and code blocks all work.
5

Create it

Click Create. The skill is available straight away.
The Metadata tab holds optional details: a category, tags, a license, other skills it relates to, and skills it Requires (skills it depends on). A finished skill is a SKILL.md file: a short header with the name and description, then the instructions.

​
Add scripts and reference files

After the first save, open the skill again and use the Resources tab to add files. Each file has a path inside the skill, such as scripts/check.py or reference/style-guide.md, and text content. In the instructions, tell the agent when to read or run each file. When an agent loads the skill, its files are copied into the agent’s sandbox (an isolated space where it can run code) under skills/<skill-name>/. For example, the instructions can say “run python skills/weekly-status-report/scripts/check.py”. Running scripts needs code execution, which is on by default; see Toolsets. Without it, the agent can still read the files.

​
Versions

Each saved change becomes a new version. The Versions tab lists them, with who made each change. Roll back copies an older version’s content into a new version, so nothing in the history is lost.

​
Import a skill

Click Import on Your skills. PipesHub shows a preview of the skill first, and nothing is saved until you click Import skill. In the preview you can change the name, for example when the original clashes with a built-in skill.
Paste the install command from the skill’s instructions, or just its package name. For example:
  • npx skills add owner/repo --skill skill-name
  • npm install @scope/skill-pack
  • @scope/skill-pack@1.2.0
PipesHub reads the command to find the package. It never runs it. When a package holds several skills, add --skill <name> to pick one.
Only text files are imported. Images and other binary files are skipped, and the preview says how many.

​
Give skills to chat and agents

Chat Assistant can use any available skill in your organization. There is nothing to set up. Agents built in Agent Builder work the same way until you attach skills to them:
  • An agent with no skills attached can use any available skill in your organization, built-in ones included.
  • An agent with skills attached can use only those. If it still needs a built-in skill such as pdf, attach that too.
Some built-in skills rely on another one: docx and pptx need office-utils, and data-visualization needs data-analysis. Chat and agents with no skills attached load these automatically. An agent with skills attached does not, so attach the required skill as well. Otherwise, for example, editing an existing Word or PowerPoint file fails because the office-utils scripts are missing.
To attach a skill, open the agent in Agent Builder, find the Skills section in the left panel, and drag the skill onto the agent. The panel lists the active skills you created and the built-in ones. See Setup guide for building an agent. If an attached skill is later disabled or deprecated, the agent’s canvas shows a warning on it.

​
Who can see a skill

  • Your skills lists the skills you created, plus the built-in ones. Other members don’t see your skills there or in their Agent Builder, and only you can edit them.
  • The Chat Assistant, and any agent with no skills attached, can use every available skill in the organization, including skills other members created. Don’t put anything in a skill that your co-workers shouldn’t read.
  • An agent with skills attached uses only those, whoever created them.
  • A skill attached to an agent keeps working for everyone who uses that agent.
  • Skill names are unique across the organization, so you can’t reuse a name another member already took.

​
Turn off, deprecate or delete a skill

You can’t delete a skill that another skill Requires, because the other skill would break. Deprecate it instead.

​
Limits

​
Troubleshooting

An admin has turned off Enable Skills (Beta) under Workspace → Labs. Turning it back on brings back the page and lets chat and agents use skills again.
Check that Available to agents is on and the skill isn’t deprecated. If the agent has other skills attached, attach this one as well. Then make the description name the kinds of requests the skill is for; that is what the agent matches against. You can also ask for the skill by name in your message.
Code execution is off for your deployment, so the agent has no sandbox to run code in. See Toolsets.
The skill you’re importing uses a reserved name such as pdf or pptx. Change the name in the preview, then import.
Add --skill <name> to the npm command to choose one. The error lists the skills it found.
Someone saved the skill after you opened it, possibly you in another tab. Click Reload to load the latest version, then make your changes again.
Another skill lists this one under Requires, so deleting it would break that skill. Deprecate it instead.