Skip to main content

Field Skills

Skills are a notepad where you record your plant's rules and know-how. Open them from the lightbulb icon in the sidebar (fa-lightbulb, Skills).

Just as the screen says: "Save engineer know-how as a skill and the agent will use it when building apps."

You no longer have to retype the same explanation in chat every time. For example, once you write down facts such as "our plant's temperature tags follow the TAG_*_TEMP naming convention" or "CRITICAL is the highest alarm priority" as a skill, every app you build afterward follows that rule.

Creating a Skill​

Click New Skill (fa-plus) to open the entry form.

ItemDescription
Skill namee.g., Our plant's alarm priority rules
CategoryFree text. Using 알람, OEE, 명명, 안전, 데이터, or 일반 attaches a matching icon to the card
Description (one line on when to use it)e.g., Refer to this when building alarm-related screens or watchers
ContentThe actual know-how body. e.g., Alarm priority is CRITICAL > ERROR > WARN. TAG_*_SAFETY tags escalate immediately…
Always apply (core rule)Checkbox — see below

Click Create to save.

Always apply (core rule)​

When checked, this rule is always injected into every app generation. When unchecked, it is loaded only for related work. The card shows an 항상 badge.

Use 'Always apply' sparingly

Check it only for the two or three rules that must be followed without exception, such as company standards. If you set every skill to always apply, the content is appended to every request, slowing responses and increasing AI usage. Leave the rest unchecked and the agent will pull them in when needed.

Examples of Well-Written Skills​

Example 1 — Tag naming convention

Name: Our plant's tag naming convention Category: Naming · Description: Refer to this when finding tags or labeling screens

Tag IDs follow the format TAG_`<plant>`_`<equipment-type>`_`<line>`_`<serial-no>`.
Plant codes: DJ=Daejeon, US=Ulsan. Equipment types: M=motor, B=boiler, C=compressor.
Temperature tags end with the suffix _TEMP, pressure with _PRES, flow with _FLOW.
Screen labels should show the alias in preference to the tag ID.

Example 2 — Alarm priority criteria

Name: Alarm priority and color criteria Category: Alarm · Description: Refer to this when building alarm lists and dashboards · Always apply ✔

Priority order is CRITICAL > ERROR > WARN > INFO.
Colors are standardized as CRITICAL red, ERROR orange, WARN yellow, INFO gray.
Safety-related tags (_SAFETY) are always pinned to the top of the list regardless of severity.
CRITICAL alarms occurring at night (22:00–06:00) are highlighted separately.
Tips for writing well
  • List facts in short sentences. A list of rules is followed better than long prose.
  • Write actual tag IDs, codes, and thresholds verbatim. This keeps the agent from guessing.
  • Keep one topic per skill, and split skills when the topic differs.

Editing, Disabling, Deleting​

Handle these directly on each skill card.

  • Enable toggle — the switch at the top right of the card. Turning it off stops the agent from using this skill. Use it to temporarily set a skill aside without deleting it.
  • Edit — the pencil icon (fa-pen). Change the content and click Save.
  • Delete — the trash icon (fa-trash-can). Deleted after confirmation.

Below the card you'll see the note "Used by the agent via use_skill" and the last modified date.

Permissions

Only Admins and Builders can create, edit, and delete skills. Viewers can only browse the list.

Extracting Skills from a Conversation​

While building apps, useful know-how often comes up in chat. Click the Extract Skill button at the top of the Builder screen, and the agent will pick out reusable content from the current conversation and turn it into a draft.

"Here is the know-how found in this conversation. Refine and save it, and the agent will use it starting with your next app."

Refine the content and click Save as Skill — that's it. If there is nothing worth extracting, it reports "No reusable know-how was found in this conversation."

Moving Between Plants (Skill Packs)​

  • Export pack (fa-file-export) — downloads all registered skills as a skills-pack.json file.
  • Import pack (fa-file-import) — select that file to register the skills in another Studio. Skills with duplicate names are skipped automatically, and results are reported in the form {n}개 가져옴 ({m}개 중복 건너뜀).

Even in plants without internet access, you can carry your team's know-how over on a USB drive intact.