Page History

---
title: "Skill Template — Replace This Title"
tags: [replace, with, relevant, keywords]
description: "One-line summary explaining what this skill teaches Claude to do"
version: "1.0"
author: "Tatsoft"
---

...

Hands-on exercises for navigating Designer interface and using productivity features.
[getting-started, new-solution, tags, simulator, display, beginner, quickstart]

...

...

When to Use This Skill

Describe the trigger conditions. Be specific — Claude uses this to decide whether to load the skill.

Use this skill when:

• The user

...

• asks to ‹describe specific scenario›
• The user

...

• mentions ‹specific keywords or concepts›
• The solution needs ‹specific capability›

...

Do NOT use this skill when:

• The solution already has tags and devices configured
• The user is asking about a specific module (use the module-specific skill instead)

Prerequisites

• ‹Scenario where a different approach is better›
• ‹Common misapplication to avoid›

Prerequisites

What must exist in the solution before this skill can be applied.

• Solution

...

• must be open (

...

• open_solution or

...

• create_solution completed)

...

• ‹Specific tags, channels, or objects that must exist›
• ‹Required ScriptsReferences or NuGet packages›

MCP Tools and Tables Involved

Quick reference for Claude on which tools and table types this skill uses.

...

...

...

Implementation Steps

Step 1:

...

‹Action Name›

Explain what to do and why. Include the exact MCP tool call.

First, fetch the schema to confirm field names:

get_table_schema('

...

TableType')

...

Then write the objects:

{
  "table_type": "

...

TableType",
  "data": [
    {

...

...

 "Name": "

...

ObjectName",
    

...

...

 "Property1": "

...

Value1",

...

...

...

 "

...

Property2": "

...

Value2"
    

...

}
  ]
}

Key decisions:

• Use Double for analog measurements, Integer for states/enums
• Slash paths (Plant/Reactor1/) create a browsable asset tree
• Always add Description — it appears in Designer tooltips and AI context

Step 2: Set Up the Value Simulator

The Value Simulator generates realistic changing values for testing — no real hardware needed.

First, get the protocol schema:

list_protocols('ValueSimulator')

Then create the device pipeline (Channel → Node → Points):

...

• Why this value for Property1
• What to change for different scenarios

Step 2: ‹Action Name›

Continue the pattern. Each step should be self-contained enough that Claude can execute it and verify before moving on.

{
  "table_type": "

...

AnotherTable",
  

...

"data": [

...

...

{

...

...

...

...

"

...

Name": "

...

ObjectName",
      

...

"

...

DependsOn": "

...

ObjectFromStep1"
    }
  ]
}

Step 3: ‹Action Name›

Final configuration step.

Code Examples

Include C# script examples when the skill involves ScriptsClasses or ScriptsTasks.

public static void MethodName(string tagPath)
{
    double value = @Tag.TagPath.Value;
    // Process logic here
    @Tag.OutputTag.Value = result;
}

Expression to trigger this class:

Verification

How to confirm the implementation is correct. List concrete checks.

1. get_objects('TableType') — verify the new objects appear
2. get_designer_state() — confirm no compilation errors (for scripts)
3. Start runtime → check that ‹expected behavior occurs›
4. browse_namespace('Tag.Path') — verify tags have expected values

Common Pitfalls

Variations

Optional section for common variations of this skill.

Variation A: ‹Name›

• Change Step 2 to use ‹alternative approach›
• Useful when ‹scenario›

Variation B: ‹Name›

• Skip Step 3 and instead ‹alternative approach›
• Useful when ‹scenario›

Related Skills

• skill-related-name — ‹How it connects›
• skill-another-name — ‹How it connects›

...

Value Simulator address patterns:

• random(min,max) — random value in range
• sin(center,amplitude,frequency) — sine wave
• ramp(min,max,step) — ramp up then reset

Important: Always call list_protocols('ValueSimulator') first to get the exact address syntax for the current version. The examples above are common patterns but the protocol schema is the source of truth.

Step 3: Create a Basic Display

Create a simple dashboard to visualize the live data.

list_elements('Dashboard')
get_table_schema('DisplaysList')

Create a dashboard with text displays for each tag:

{
  "table_type": "DisplaysList",
  "data": [
    {
      "Name": "MainPage",
      "PanelType": "Dashboard",
      "Columns": 2,
      "Rows": 3,
      "Title": "Reactor 1 Monitor",
      "Elements": [
        {
          "Type": "TextBlock",
          "Column": 0, "Row": 0,
          "LinkedValue": "Tag.Plant/Reactor1/Temperature",
          "Label": "Temperature (°C)"
        },
        {
          "Type": "TextBlock",
          "Column": 1, "Row": 0,
          "LinkedValue": "Tag.Plant/Reactor1/Pressure",
          "Label": "Pressure (bar)"
        },
        {
          "Type": "TextBlock",
          "Column": 0, "Row": 1,
          "LinkedValue": "Tag.Plant/Reactor1/Level",
          "Label": "Level (%)"
        },
        {
          "Type": "TextBlock",
          "Column": 1, "Row": 1,
          "LinkedValue": "Tag.Plant/Reactor1/FlowRate",
          "Label": "Flow Rate (L/min)"
        },
        {
          "Type": "TrendChart",
          "Column": 0, "Row": 2, "ColumnSpan": 2,
          "Pens": [
            { "TagName": "Tag.Plant/Reactor1/Temperature", "Color": "#FF3498DB" },
            { "TagName": "Tag.Plant/Reactor1/Pressure", "Color": "#FFE74C3C" }
          ]
        }
      ]
    }
  ]
}

Key decisions:

• PanelType: "Dashboard" — required, do not omit (defaults to Canvas otherwise)
• MainPage is the default startup display
• Use LinkedValue with full runtime path: Tag.Plant/Reactor1/Temperature
• Omit color properties to use theme defaults (except for trend pens)

Step 4: Start Runtime

designer_action('start_runtime')

Wait a few seconds, then verify:

get_runtime_state()

You should see tag values changing as the simulator feeds data.

Verification

1. get_objects('UnsTags') — confirm 5 tags exist
2. get_objects('DevicesChannels') — confirm Simulator channel exists
3. get_objects('DevicesPoints') — confirm 5 points mapped to tags
4. get_runtime_state() — runtime should be running, tags should have changing values
5. Take one screenshot of the display to confirm visual rendering

Common Pitfalls

• Forgetting PanelType: Omitting PanelType on a display defaults to Canvas, which uses absolute positioning (Left/Top) instead of grid layout. Always set PanelType: "Dashboard" for grid-based layouts.
• Wrong LinkedValue path: Use Tag.Plant/Reactor1/Temperature (with Tag. prefix) in display bindings. The tag Name is Plant/Reactor1/Temperature but the runtime namespace path needs the Tag. prefix.
• Simulator address syntax: Always check list_protocols('ValueSimulator') for current syntax. Don't guess address formats from memory.
• Points without TagName: Every DevicesPoint needs a TagName to map to a UNS tag. Points without TagName don't feed data anywhere.

What's Next

From here, the user can add:

• Alarms → skill-alarm-pipeline
• Historian → skill-historian-configuration
• ML models → skill-edge-ml-pipeline
• MQTT publishing → search for MQTT skills
• More displays → search for display/dashboard skills

In this section...

...

...