Skill Package Capabilities Overview
Package a set of business knowledge, operational procedures, prompt rules, SQL templates, or analytical methods so that an Agent follows those rules when it encounters a matching request.
What a Skill can do
- Encode business processes: for example, data profiling, job failure diagnosis, table optimization governance.
- Fix output formats: for example, output a diagnostic report structured as "Conclusion, Evidence, Recommendation".
- Reuse domain knowledge: for example, table relationships, metric definitions, and modeling rules for the Olist e-commerce dataset.
- Manage complex templates: for example, store SQL templates in
references/sql_templates.mdfor the Agent to use. - Improve Agent consistency: avoid re-explaining rules each time and make the same type of task execute more reliably.
A Skill typically contains
SKILL.md: the core description file, containing the skill name, description, trigger scenarios, and execution steps.references/: an optional directory for long documents, SQL templates, rule libraries, metric definitions, etc.- Other supporting files: such as examples, scripts, and templates.
A simple example
Scenarios suited for a Skill
- A category of tasks recurs frequently.
- There is a fixed business process.
- A stable output format is required.
- There is substantial domain knowledge or templates to reuse.
- You want the Agent to follow a standard automatically.
Uploading a Skill
Upload entry point
- Open the Data Agent page.
- Click
Skillsin the left sidebar. - Click
+above the Skill list. - The
Upload Skilldialog appears.
File requirements
-
Supports
.md,.zip, or.skillfiles. -
If uploading a
.mdfile:- The file must contain a YAML front matter block.
- The YAML block must include
nameanddescription.
-
If uploading a
.zipor.skillfile:- The archive must contain exactly one
SKILL.md. - Place
SKILL.mdat the top level of the archive to avoid multi-level directory parsing failures.
- The archive must contain exactly one
Recommended SKILL.md format
YAML rules
- Must start with three hyphens:
--- - Must end with three hyphens:
--- namemust have a value.descriptionmust have a value.descriptionshould be written on a single line.- Do not use
\to breakdescriptionacross lines. - Multi-line descriptions are not recommended.
- The body starts after the second
---and can be written as normal Markdown.
Discouraged formats
Upload steps
-
In the
Upload Skilldialog, click the upload area. -
Select the prepared
.md/.zip/.skillfile. -
In the
Promptinput box, enter a trigger prompt, for example:Run upload skill smoke testUse the data profiling skillProfile all tables in the schema
-
Click
Confirm. -
After a successful upload, the Skill appears in the left Skill list.
-
Click a Skill to view its name, type, update time, owner, description, prompt, and body content.
Using a Skill
- Click
Useon the Skill detail page. - The page returns to the Agent chat box and inserts the Skill tag into the input field.
- Enter your task description and send.
- The Agent should execute or respond according to the Skill content.
Common failure reasons
- No
SKILL.mdinside the zip archive. - Multiple
SKILL.mdfiles inside the zip archive. - YAML does not start with
---. - YAML is missing the closing
---. - Missing
name. - Missing
description. - Line breaks in
descriptioncause parsing errors. - The uploaded file is a fake zip or a corrupted zip.
Recommendations
- Keep
descriptioncompressed to a single line. - Use English letters, digits, and hyphens for file names and
name. - Check
SKILL.mdlocally before each upload. - When an upload fails without a clear error message, first check whether
SKILL.mdis missing or the YAML format is incorrect.
Using a Skill
After selecting a Skill, the Agent will prioritize that Skill as its planning path when formulating a plan, and will plan and execute its current actions accordingly.

