‹ 首页

tia-openness-roadmap

@czarnak · 收录于 1 周前

Entry point for ALL TIA Portal engineering automation tasks. Always load this skill FIRST when the user mentions TIA Portal, TIA Openness, TIA Scripting, Siemens PLC, Siemens HMI, TIA Portal Add-In, or any automation/engineering task targeting TIA Portal. This skill routes to the correct domain skill and selects MCP, Python, or C# implementation.

适合你,如果经常用TIA Portal做自动化工程,需要统一入口管理任务。

/ 下载安装
tia-openness-roadmap.skill双击,或拖进 Claude 桌面版 / Cowork,即完成安装↓ .skill↓ .zip
用别的 agent?下载 .zip 解压,把文件夹放进它的技能目录
Claude Code~/.claude/skills/(项目级 .claude/skills/)
Codex CLI~/.codex/skills/
Cursor自动读取上面两处目录
其他工具见其文档的「skills」目录;两个下载是同一份文件,只是名字不同
/ 通过 npx 安装 校验哈希
npx oh-my-skill add czarnak/totally-integrated-claude/tia-openness-roadmap
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- czarnak/totally-integrated-claude/tia-openness-roadmap
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify czarnak/totally-integrated-claude/tia-openness-roadmap
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
29GitHub stars
~1.5K上下文体积 · 单文件
镜像托管

怎么用

技能原文 SKILL.md作者撰写 · MIT · 9147951

tia-openness-roadmap

Goal

Route the task to the correct implementation path and load the right skill files.

Mandatory policy
  1. Prefer TIA Portal MCP for interactive, single-step read/write operations when the MCP server is available.
  2. Prefer TIA Scripting Python for scripted or multi-step automation.
  3. Use C# TIA Portal Openness only if Python is insufficient.
  4. Do not invent Python wrapper methods.
  5. For multi-domain tasks, select all required skills.
Implementation paths
MCP path

Direct tool calls — no code generation. Use when the TIA Portal MCP server is available.

| Skill | Location | |---|---| | tia-portal-mcp | skills/tia-portal-mcp/SKILL.md |

Python path

Single skill owns all Python implementation:

| Skill | Location | |---|---| | tia-python | skills/tia-python/SKILL.md |

tia-python contains its own reference file table that routes to the correct references/*.md file based on the task domain (PLC, HMI, library, project, portal).

C# path

Always starts with the common foundation skill, then domain skill(s):

| Skill | Location | Role | |---|---|---| | tia-csharp-common | skills/tia-csharp-common/SKILL.md | Mandatory first load for every C# task | | tia-project-general | skills/tia-project-general/SKILL.md | Domain skill | | tia-devices-general | skills/tia-devices-general/SKILL.md | Domain skill | | tia-hmi-operations | skills/tia-hmi-operations/SKILL.md | Domain skill | | tia-plc-operations | skills/tia-plc-operations/SKILL.md | Domain skill | | tia-networks | skills/tia-networks/SKILL.md | Domain skill | | tia-simatic-drives | skills/tia-simatic-drives/SKILL.md | Domain skill | | tia-import-export | skills/tia-import-export/SKILL.md | Domain skill | | tia-multiuser | skills/tia-multiuser/SKILL.md | Domain skill | | tia-teamcenter | skills/tia-teamcenter/SKILL.md | Domain skill | | tia-testsuite | skills/tia-testsuite/SKILL.md | Domain skill |

Add-In path

Standalone skill for TIA Portal Add-In development (always C#, VS Code workflow):

| Skill | Location | |---|---| | addin-operations | skills/addin-operations/SKILL.md |

Routing rules

| Task pattern | Implementation | Skill | |---|---|---| | browse / explore project tree structure | MCP | tia-portal-mcp | | read a single PLC block (view logic / generate code) | MCP | tia-portal-mcp | | targeted single-block edit | MCP | tia-portal-mcp | | list tag tables and tags | MCP | tia-portal-mcp | | inspect hardware topology / IP addresses | MCP | tia-portal-mcp | | cross-reference diagnostics / unused objects | MCP | tia-portal-mcp | | prerequisite / environment / missing install diagnostics | Diagnostic probe | tia-doctor | | add a single device to the project | MCP | tia-portal-mcp | | configure device network identity (IP, PN name) | MCP | tia-portal-mcp | | compile check / view errors and warnings | MCP | tia-portal-mcp | | open/create/save/archive/retrieve project | Python | tia-python | | project server / local session / portal attach | Python | tia-python | | PLC blocks / tags / UDTs / sources / compile | Python | tia-python | | PLC online / download / compare-to-online | Python | tia-python | | HMI tags / screens / scripts / alarms / lists | Python | tia-python | | HMI import/export / compile | Python | tia-python | | library types / versions / instantiate / update | Python | tia-python | | XML / SimaticML / AML / CAx import/export | Python | tia-python | | generic device compile / upgrade / properties | Python | tia-python | | topology / subnet / node / IO-system / port | C# | tia-networks | | Startdrive / SINAMICS / drive controller | C# | tia-simatic-drives | | device item slot/subslot/module manipulation | C# | tia-devices-general | | advanced PLC online/security/upload services | C# | tia-plc-operations | | deep Unified HMI / screen items / runtime | C# | tia-hmi-operations | | VCI / version control interface | C# | tia-project-general | | multiuser engineering / server projects / local sessions | C# | tia-multiuser | | Teamcenter integration / managed projects | C# | tia-teamcenter | | automated testing / TestSuite / application test / style guide / system test | C# | tia-testsuite | | TIA Portal Add-In / addin-project / .addin | C# | addin-operations |

MCP vs Python vs C# decision rule

Choose MCP when:

  • the task is a single read or targeted write (one block, one device, one compile check)
  • the user wants to explore or inspect a project interactively
  • no looping, no bulk changes, no code generation is needed
  • the tia-portal MCP server is available (check mcp__tia-portal__* tools)

Choose Python when the exact required operation exists in the tia-python reference files. Choose C# when:

  • the required operation is absent from the Python reference catalogue
  • the task needs low-level object model traversal
  • the task needs topology/network object manipulation
  • the task needs drive-specific APIs
  • the task needs advanced online/security/session/event APIs
  • the task needs Teamcenter, VCI, advanced multiuser, or unsupported safety/Unified features
Multi-skill execution order
  1. project / portal
  2. device selection
  3. domain work
  4. import/export
  5. compile / compare / download / validation
Required response format

Use this exact structure:

  • Use skill(s): ...
  • Implementation path: MCP or Implementation path: Python or Implementation path: C# Openness or Implementation path: Diagnostic probe
  • Reason: ...
  • Execution order: ...
Post-routing action — MANDATORY

If Diagnostic probe: read skills/tia-doctor/SKILL.md and run its probe command. Report the probe output and remediation items. Do not create or modify projects.

If MCP: read skills/tia-portal-mcp/SKILL.md. Use the MCP tools directly — no code generation.

If Python: read skills/tia-python/SKILL.md, then load the reference file(s) it points to for the task domain. Do NOT load domain skills — they are for C# only.

If C#:

  1. Read skills/tia-csharp-common/SKILL.md first — always, for every C# task.
  2. Read the SKILL.md of each selected domain skill, then load only the references/*.md file(s) that skill's own reference table (or its reference_catalogue.md, where present) points to for the task.

If Add-In: read skills/addin-operations/SKILL.md. No other skills needed.

Do NOT write code based solely on the routing response — always load the skill files first.

Escalation rule

If implementation starts in Python and the required call is not documented:

  • stop
  • switch to the corresponding C# domain skill
  • load tia-csharp-common first, then the domain skill
  • keep the same task decomposition
Hard escalation triggers (always C#)
  • device item slot/subslot operations
  • subnet/node/IO-system/port/channel/address manipulation
  • Teamcenter / ConnectSSO
  • VCI / advanced multiuser
  • advanced PLC online/security services
  • advanced Unified internals
  • drive-specific engineering
  • diagnostics / event handlers / self-description APIs
按 MIT 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。