agentleFS
Sign inStart free
SmailGSmailG/plc-programming/skills/validate/SKILL.md

validate

Skill0 starsChanged 37 days agoMITView on GitHub

Run the plugin's structural validator on PLC files or directories (ST/SCL, PLCopen XML, IEC 61131-10, SimaticML, SIMATIC SD, TwinCAT, L5X/L5K, Control Expert XEF, IEC 61499, AutomationML, DEXPI, CSV) and explain the findings.

63 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use policy-init, create and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • open-coder-aiSkill

    policy-init

    Create conformant Chock policy from request. args(request, target_path,

    Also in 3 projects that use this

  • MicrosoftSkill

    create

    Also in 4 projects that use this

  • HermeticOrmusSkill

    close

    End-of-session ritual. Captures session state, updates auto-memory, writes a session summary, then exits the session cleanly.

    Also in 4 projects that use this

  • Hugging FaceSkill

    sprint

    Work on a batch of GitHub issues in parallel using Agent Teams. Creates one worktree per issue with TDD enforcement, coordinates via a lead agent, then produces stacked PRs.

    Also in 4 projects that use this

  • qtzx06Skill

    eval

    Evaluate trained YOLO model accuracy with mAP metrics and per-class error analysis. Identifies failure cases for targeted improvement. Use after training.

    Also in 4 projects that use this

  • csiddhant796-blipSkill

    board

    Read, write, and browse the AgentHub message board for agent coordination.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 53 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If $ARGUMENTS is empty, use the current directory.

    line 17
  2. Very specific:

    XSD validation: if the user wants it and has no schema, point them to <https://www.plcopen.org/downloads/> ("XML Exchange").

    line 36

“Common” is measured: kept by at least 6 in 10 of the 53 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Validate PLC files

Run:

python3 "${CLAUDE_PLUGIN_ROOT:-scripts}/plc_validate.py" $ARGUMENTS

If $ARGUMENTS is empty, use the current directory.

Then:

  1. Group the findings by file. For each error, explain the cause in one line and give the fix. Rule families:
    • ST Structured Text
    • PX PLCopen XML / IEC 61131-10
    • SM SimaticML, SD SIMATIC SD
    • TC TwinCAT
    • LX Logix
    • CX Control Expert
    • FB IEC 61499
    • AM AutomationML
    • DX DEXPI
    • CS CSV
    • XS XSD
  2. Say plainly that this is a structural check, not a compile. Types, library symbols and cross-file references are not resolved.
  3. XSD validation: if the user wants it and has no schema, point them to https://www.plcopen.org/downloads/ ("XML Exchange"). The schemas cannot be bundled because of their licences. Then re-run with --xsd <path>.
  4. Offer to fix the errors, one file at a time.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free