Skills

A skill is a short instruction file for one kind of job: how to build the monthly report, how to check a carrier invoice, which steps to follow when a client asks for an offer. "Instructions your agents load when a task calls for them." You write it once, and the assistant loads it whenever a request matches. An agent says who the assistant is; a skill says how a particular job is done.

Before you start

• Skills are part of every plan; they are used by the AI assistant, so they need AI in the plan.
• Everyone reads skills. Members and admins create and change them; for others: "You can read this skill, but you do not have permission to change it."
• Everyone in the organization can read a skill, so keep secrets out of it.

How a skill is used

The assistant always sees the name and the description of the active skills, and nothing else. When a request matches a description, it loads the skill's instructions and follows them; supporting files are read only when the instructions point to them.

That is why the description matters most: "Agents choose a skill by its description." Say what the skill does and when to use it, in the words your team would type. The list the assistant sees holds up to 30 skills and about 4,000 characters in all, with each description cut at 200 characters, so put the key words first.

The Skills tab

Open Agents in the sidebar, then Skills.

• The list has two groups, Your organization and Global, with Search skills on top. Badges mark Global, Inactive, Draft and Unsaved changes.
• New skill: Blank skill or Import SKILL.md or .zip.
• A skill opens in the editor: Source or Preview (Content view), the character count (for example "1240 / 40000 characters"), Allowed tools, and when and by whom it was last changed ("Updated 02.11.2026 by Kasia Próbna").
• Active: agents can use this skill: an inactive skill stays on the list but is not offered to the assistant.
• Save changes / Create skill, Discard changes, and under More actions: Export, Duplicate, Delete ("“carrier-scorecard” will be deleted with its supporting files. Agents will no longer be able to use it.").

The editor checks the file as you type and names each problem under it, for example "The name may only use lowercase letters, digits and single hyphens, for example monthly-report." or "Add a description to the frontmatter. Agents choose a skill by its description." "Fix the problems marked under the editor to save."

Write a SKILL.md

"SKILL.md format: the frontmatter between the --- lines holds name, description and optional allowed-tools. The instructions follow in markdown."

The instructions under the frontmatter can be up to 40,000 characters. Other frontmatter fields are not stored: "These frontmatter fields are not stored and will be dropped on save".

A short, complete example:

---
name: carrier-scorecard
description: Build the monthly carrier scorecard from the Zlecenia table. Use when someone asks for a carrier ranking, on-time delivery or the monthly scorecard.
allowed-tools:
  - read_spreadsheet
  - search_library
---
 
# Carrier scorecard
 
## When to use
 
Requests for a ranking of carriers, on-time delivery or the monthly scorecard.
Not for a single order: answer those directly.
 
## Steps
 
1. Read the Zlecenia table for the month the user asked about.
2. For each carrier count the orders, the late ones and the claims.
3. Rank carriers by the share of on-time deliveries, best first.
4. For the wording of the summary read templates/summary.md.
 
## Rules
 
- An order is late when Rozładunek is after the agreed date.
- Leave out carriers with fewer than 5 orders and say that you did.
- Always state the month and the number of orders the ranking is based on.

The example sets allowed-tools because a scorecard only reads; the narrowing applies when someone picks the skill with /. Most skills do not need it: leave the field out and the assistant keeps everything it normally has.

Habits that make a skill work:

• Start the description with what it does, then when: "Use when...".
• Number the steps in the order they are done.
• Write rules with their numbers ("fewer than 5 orders"), not "be careful".
• Name your real tables, columns, thresholds and wording.
• Keep secrets out: everyone in the organization can read a skill.

Supporting files

"Text files the skill can point to: references, templates, examples." A skill holds up to 10 ("A skill holds up to 10 files.").

1. In Supporting files, click Add file.
2. Give it a Path such as references/pricing.md (up to 120 characters, forward slashes, no ..).
3. Type the Content or Load from a file (text only, up to 60,000 characters). Click Save file.

Point to each file from the instructions by its exact path and say when to read it, as step 4 of the example does. A file the instructions never mention is never read.

Import and export

Skills use the open Agent Skills format (agentskills.io), so a skill written in Quanty works in other tools that read the format, and skills from elsewhere can be brought in.

• Import: Import SKILL.md or .zip, or drop the file on the page ("Drop a SKILL.md or a .zip to import it"). One file, up to 2 MB; a .zip holds the SKILL.md and up to 10 supporting files. What could not be kept is listed under Imported with notes.
• Export: downloads the skill with its supporting files as a .zip. "Exports the saved version, without your unsaved changes."

Global skills

Global skills come with Quanty: "Global skills are maintained by Quanty and cannot be edited. Duplicate this one to make your own version." Duplicate to edit makes a copy in your organization.

Skills per agent

Each agent's settings have a Skills section:

• All active skills: every active skill, including ones added later.
• Selected skills: only the skills you pick (up to 50).

With Selected skills and nothing picked, the agent works without skills. Manage skills opens the Skills tab.

Pick a skill in chat

Type / in the message box. The Generate group comes first (a dashboard, slides, a Word document, an Excel file, a PowerPoint file), then your organization's skills under Skills. Keep typing to narrow the list ("No matching skill"), pick one, and write your request. The skill applies to this one message. If it is no longer available: "The selected skill is not available, so this answer was written without it."

Limits

Related pages

• Agents: who the assistant is, and which skills each agent uses.
• Tables, files, dashboards and decks from chat: the / menu and files created in chat.
• Write a report from chat: a recipe that uses skills.