User skills
The user skill fixes the team’s methodology: rules for building models, acceptable parameters, calculation procedure, verification, and report format. It is stored in your environment Engee and is available to the agent via Engee MIND.
Creating using an agent
Describe the procedure and ask to use engee_skill_create. For example:
Создай пользовательский навык engee_step_response_check для проверки переходной характеристики. На входе — модель, имя выходного сигнала, длительность расчета и допуски. Навык должен запускать модель, получать данные через To Workspace, проверять конечность значений и сравнивать установившееся значение с заданным эталоном. Сохраняй CSV и отчет в каталоге проекта. Не меняй параметры объекта автоматически.
Give the agent the current methodology or some proven examples. Separate mandatory checks from recommendations and specify what to do if there is a lack of data.
Package structure
engee_step_response_check/
├── manifest.yaml
├── SKILL.md
└── reference/
└── acceptance.md
manifest.yaml contains metadata and skill selection criteria. SKILL.md contains an executable sequence of actions. Voluminous help and templates are placed in reference/; each file is listed in the manifest.
Example of a manifest
The example is designed for the file actually created reference/acceptance.md. If there is no help, use reference-files: [].
schema_version: 1
name: engee_step_response_check
version: 0.1.0
title: "Проверка переходной характеристики"
description: >
Расчет заданной модели и сравнение установившегося значения
выходного сигнала с эталоном и допусками пользователя.
language: ru
audience: [assistant]
priority: 0.5
when-to-use:
- "Нужно проверить переходную характеристику по заданному эталону"
when-not:
- "Требуется автоматически настроить регулятор"
requires-tools:
- engee_status
- eval_code
- engee_diagnose
requires-products:
- Engee
reference-files:
- reference/acceptance.md
Content SKILL.md
Describe the purpose and limitations; mandatory input data with units; selection of the project and files; sequence of actions; response to errors; completion criteria and composition of the issue.
Write specifically:
получи данные текущего прогона
проверь отсутствие NaN/Inf
сравни с допуском пользователя
Do not record PAT, passwords, or paths to other people’s projects in the skill. Do not promise features that are not confirmed by the API or a proven example. Explicitly mark the parameters that the user sets.
Installation and verification in your environment
-
Prepare the package locally or instruct the agent to create it immediately in the session Engee.
-
Place it in
/user/.engee-skills/engee_step_response_check/either/user/skills/engee_step_response_check/. When transferring local files, usefile_uploadfor each package file. -
Ask to call
skill_listand find a skill. When starting the environmentengee_startalso performs scanning of user skills. -
Load the skill using the exact path from the scan result, for example
/user/.engee-skills/engee_step_response_check/SKILL.md, viaskill_load. -
Check the content, source
podand the availability of help files. -
Perform a trial run on a separate test model with a known result. Check the usual case and the case when the criterion is not met.
-
Correct the procedure, increase the version, and reload the skill.
If the skill is not detected, check the case of the name, the presence of both main files and the match name with the folder name. Do not restart the computing environment just for the sake of re-searching when enough is enough skill_list.