PLC Skill

---

name: plc-skill description: General PLC development, explanation, review, refactoring, debugging, and troubleshooting skill across IEC 61131-3 style industrial control work. Use when the request involves PLC logic, sequence control, state machines, alarms, interlocks, timers, counters, I/O mapping, Structured Text (ST), Ladder Diagram (LD), Function Block Diagram (FBD), Sequential Function Chart (SFC), program structure, code review, maintainability, or commissioning/debugging. Route through the common PLC layer first, then prefer the matching vendor path when the user mentions Mitsubishi, Siemens, Omron, Allen-Bradley/Rockwell, Schneider, Delta, Keyence, Panasonic, Beckhoff, or Codesys ecosystems, software, CPU families, device models, or vendor-specific terminology. Do not prefer this skill for generic electronics, pure wiring-only work without logic context, broad industrial networking without control-program context, or high-confidence safety conclusions without confirmed field conditions. metadata: { "openclaw": { "requires": { "bins": ["openclaw"] } }, "version": "1.0.0", "author": "OpenClaw Community", "tags": ["plc", "iec61131-3", "st", "ladder", "siemens", "rockwell", "mitsubishi", "omron", "codesys", "beckhoff", "schneider", "delta", "keyence", "panasonic"] }

---

PLC Skill

Treat this as a general PLC skill with explicit vendor routing, not as a vague all-brands encyclopedia.

Work in two layers:

1. Common PLC layer 2. Vendor-specific layer when the platform is identifiable

Always keep these layers separate.

Operating model

First decide whether the request is actually a PLC/programming task.

Then classify it as one of:

common PLC question with no confirmed vendor

vendor-specific PLC question

mixed / ambiguous vendor question

out-of-scope non-PLC question

If the vendor is known, use the matching vendor references first for environment, terminology, program organization, instruction semantics, and tooling behavior.

If the vendor is unknown, answer from the common PLC layer first and explicitly mark which details depend on vendor, model, software, or language.

If the user mixes multiple vendor ecosystems or terms, point out the likely mismatch instead of silently merging them.

Core boundaries

This skill covers:

PLC logic design

sequence / state-machine / step control

alarms, latches, resets, interlocks

timers, counters, edge-triggered behavior

I/O mapping strategy

program organization and modularity

debugging and troubleshooting

code review and refactoring

IEC 61131-3 language-level reasoning

ST / LD / FBD / SFC common concepts

vendor-specific routing when the platform is known

This skill does not default to:

generic electronics or PCB work

pure wiring-only installation answers without control logic context

broad industrial networking coverage with no PLC-program relevance

SIL/PL/safety certification conclusions without confirmed field context

pretending that one vendor's terminology or syntax applies to all vendors

Read order

Start with:

references/skill-architecture.md

references/common/scope-and-trigger-rules.md

references/common/task-router.md

references/common/knowledge-priority.md

references/vendors/vendor-routing.md

templates/common/template-map.md

Then load only the narrowest files needed.

Common layer responsibilities

Use the common layer for:

IEC 61131-3 framing and language-level concepts

sequence, state, alarm, interlock, reset, ownership, and scan-cycle reasoning

engineering structure and maintainability guidance

generic debugging, review, and completeness handling

common templates, checklists, and response format

Read from references/common/ and templates/common/ first when the vendor is unknown.

Vendor layer responsibilities

Use a vendor layer for:

vendor software environment and engineering workflow

vendor terminology and model-family cues

vendor-specific instruction, device, memory, or tag conventions

project organization norms for that platform

debugging behavior and common platform pitfalls

official manual routing and evidence preference for that ecosystem

Current deepest vendor module:

Mitsubishi: mature and preferred when Mitsubishi / MELSEC / GX Works / FX / Q / iQ-F / iQ-R cues are present

Prepared expansion modules:

Siemens

Omron

Rockwell / Allen-Bradley

Schneider

Delta

Keyence

Panasonic

Beckhoff

Codesys

Evidence priority

Use evidence in this order:

1. Bundled common references for PLC-generic engineering rules 2. Bundled vendor references for the identified platform 3. Vendor official manuals / official software docs 4. IEC 61131-3 and PLCopen material 5. Bundled templates and examples 6. Community material as low-priority supplement

If the answer depends on vendor-specific behavior and the vendor is not confirmed, say so.

Response rules

Always:

separate confirmed facts from assumptions

say when implementation details depend on vendor/model/software

prefer modular, reviewable outputs over giant code dumps

use templates/checklists when inputs are incomplete

stay conservative in safety-relevant topics

Reference map

Common:

references/common/scope-and-trigger-rules.md

references/common/task-router.md

references/common/knowledge-priority.md

references/common/query-to-doc-routing.md

references/common/glossary.md

references/common/plcopen-and-iec-notes.md

references/common/st-style-guide.md

references/common/st-output-style.md

references/common/program-templates.md

references/common/alarm-and-interlock-patterns.md

references/common/scan-cycle-and-output-ownership.md

references/common/debugging-and-review.md

references/common/debugging-checklists.md

references/common/code-review-checklists.md

references/common/input-completeness-rules.md

references/common/response-fallback-rules.md

references/common/output-format.md

references/common/safety-boundaries.md

references/common/ide-integration-formats.md

references/common/hmi-interface-patterns.md

references/common/hardware-abstraction-mapping.md

references/common/vendor-pitfalls-and-pro-tips.md

references/common/version-control-and-code-review.md

Routing:

references/skill-architecture.md

references/vendors/vendor-routing.md

references/vendors/vendor-module-map.md

references/vendors/vendor-recognition-signals.md

Mitsubishi:

references/vendors/mitsubishi/mitsubishi-overview.md

references/vendors/mitsubishi/mitsubishi-fx3u-rules.md

references/vendors/mitsubishi/fx3u-focus.md

references/vendors/mitsubishi/fx3u-device-and-instruction-notes.md

references/vendors/mitsubishi/gxworks2-structured-project.md

references/vendors/mitsubishi/gxworks2-structured-project-deep-notes.md

references/vendors/mitsubishi/gxworks2-project-review-patterns.md

references/vendors/mitsubishi/official-doc-index.md

Mature vendor modules:

Siemens:

references/vendors/siemens/siemens-overview.md

references/vendors/siemens/siemens-s7-1200-1500-rules.md

references/vendors/siemens/siemens-st-programming-guide.md

references/vendors/siemens/official-doc-index.md

Rockwell / Allen-Bradley:

references/vendors/rockwell/rockwell-overview.md

references/vendors/rockwell/rockwell-logix-rules.md

references/vendors/rockwell/rockwell-st-programming-guide.md

references/vendors/rockwell/official-doc-index.md

Omron:

references/vendors/omron/omron-overview.md

references/vendors/omron/omron-nj-nx-rules.md

references/vendors/omron/official-doc-index.md

Schneider:

references/vendors/schneider/schneider-overview.md

references/vendors/schneider/schneider-modicon-rules.md

references/vendors/schneider/official-doc-index.md

Beckhoff:

references/vendors/beckhoff/beckhoff-overview.md

references/vendors/beckhoff/beckhoff-twincat-rules.md

references/vendors/beckhoff/official-doc-index.md

Codesys:

references/vendors/codesys/codesys-overview.md

references/vendors/codesys/codesys-v3-rules.md

references/vendors/codesys/official-doc-index.md

Delta:

references/vendors/delta/delta-overview.md

references/vendors/delta/delta-dvp-rules.md

references/vendors/delta/official-doc-index.md

Keyence:

references/vendors/keyence/keyence-overview.md

references/vendors/keyence/keyence-kv-rules.md

references/vendors/keyence/official-doc-index.md

Panasonic:

references/vendors/panasonic/panasonic-overview.md

references/vendors/panasonic/panasonic-fpwin-rules.md

references/vendors/panasonic/official-doc-index.md