About

Imported from MIGO-OvO/plc-skill (SKILL.md). Install upstream with npx skills add MIGO-OvO/plc-skill. Copyright stays with the author.

PLC Skill

Name: plc-skill
Author: MIGO-OvO

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

Work in two layers:

Common PLC layer
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
explicit support for reading, writing, and reviewing Structured Text (ST), Ladder Diagram (LD), Function Block Diagram (FBD), and Sequential Function Chart (SFC) code
IEC 61131-3 language-level reasoning
advanced templates for process control, motion, recipes, and data logging
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

Always start with:

references/common/scope-and-trigger-rules.md
references/common/task-router.md
references/common/knowledge-priority.md

Then conditionally load:

references/vendors/vendor-routing.md only when the request includes vendor, software, CPU family, device model, memory/tag, or platform terminology cues.
templates/common/template-map.md only for generation, refactor, or pattern-selection tasks.

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
handling LD, FBD, and SFC code alongside ST
leveraging 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 support depth

Deepest production path:

Mitsubishi FX3U + GX Works2 + Structured Project + ST

Targeted secondary modules:

Siemens
Rockwell / Allen-Bradley
Omron

Baseline routing/reference modules:

Beckhoff
Schneider
Codesys
Delta
Keyence
Panasonic

Do not assume every vendor path has the same depth, examples, or eval coverage.

Evidence priority

Use evidence in this order:

Bundled common references for PLC-generic engineering rules
Bundled vendor references for the identified platform
Vendor official manuals / official software docs
IEC 61131-3 and PLCopen material
Bundled templates and examples
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

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

yaml

targets:
  - https://api.opensmartroute.ai/api/v1/registry/migo-ovo-plc-skill-plc-skill/manifest   # or paste the manifest below

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

migo-ovo-plc-skill-plc-skill.ocm.jsonjson

{
  "ocm": "1",
  "id": "migo-ovo-plc-skill-plc-skill",
  "kind": "skill",
  "name": "plc-skill",
  "description": "Vendor-aware PLC engineering skill for IEC 61131-3 logic design, review, debugging, refactoring, and documentation routing.",
  "publisher": "MIGO-OvO",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "math"
    ],
    "tags": [
      "skill-md",
      "plc",
      "iec61131-3",
      "st",
      "ladder",
      "sfc",
      "siemens",
      "rockwell",
      "mitsubishi",
      "omron"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "Vendor-aware PLC engineering skill for IEC 61131-3 logic design, review, debugging, refactoring, and documentation routing."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "github",
      "repository": "https://github.com/MIGO-OvO/plc-skill",
      "path": "SKILL.md",
      "ref": "82e541946e8f92f688b94d476b1b5fc09f531947",
      "url": "https://github.com/MIGO-OvO/plc-skill/blob/82e541946e8f92f688b94d476b1b5fc09f531947/SKILL.md",
      "key": "MIGO-OvO/plc-skill/SKILL.md"
    }
  },
  "instructions": "# PLC Skill\n\nTreat this as a general PLC skill with explicit vendor routing, not as a vague all-brands encyclopedia.\n\nWork in two layers:\n\n1. Common PLC layer\n2. Vendor-specific layer when the platform is identifiable\n\nAlways keep these layers separate.\n\n## Operating model\n\nFirst decide whether the request is actually a PLC/programming task.\n\nThen classify it as one of:\n\n- common PLC question with no confirmed vendor\n- vendor-specific PLC question\n- mixed / ambiguous vendor question\n- out-of-scope non-PLC question\n\nIf the vendor is known, use the matching vendor references first for environmen",
  "cost": {
    "context_tokens": 1107
  }
}

Fetch it by URL: GET /api/v1/registry/migo-ovo-plc-skill-plc-skill/manifest?version=1.0.0

Reviews

Star ratings from people who tried it. One review per account; edit yours any time.

No reviews yet. Install it, try it, and be the first to rate it.