eec-pro-development skillA
eec-pro-development is agent-read markdown (skill) from covagashi/eplan-development-skill: Develop with EPLAN EEC Pro 2026 — the mechatronic model and typicals (variants, conditions), the formula language, configuration interfaces (Form-UI, Excel/CSV/XML/IMX import), commands and C# scripting, and generation into EPLAN Electric P8, Pro Panel, PLC, Graph2D and text/Office targets, locally or through the Job Server. Use when building or debugging EEC Pro libraries, typical workbooks, configurations or generation pipelines, or decoding what an EEC-generated project did..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# EPLAN EEC Pro development EEC Pro generates engineering deliverables — EPLAN Electric P8 schematics, Pro Panel layouts, PLC programs, Graph2D documents, Word/Office files — from a **mechatronic model plus a configuration**, instead of drawing them by hand. This skill teaches the mental model and the workflow; the *details* (every formula function, every command, every parameter) live in a searchable documentation index — see "Looking things up". ## The pipeline ``` mechatronic model + configuration values ──► generation ──► target output (typicals, params, (GUI, Form-UI, (resolve (P8 project, Pro conditions, Excel/CSV/XML/IMX, conditions, Panel, PLC, text) formulas, commands) SAP, manual entry) insert macros) ``` 1. **The mechatronic model** describes the product independent of any target system: functions, parameters, and the rules connecting them. Tutorials: `tutmechatronic`. 2. **Typicals** are the reusable building blocks. A typical wraps target artifacts (macro files, document templates) behind **variants** and **conditions** — e.g. …
Read the whole file at its exact version.
How to install
mdr add covagashi/eplan-development-skill/eec-pro-development@git:20260923.c8be18bmdr add covagashi/eplan-development-skill/eec-pro-development@sha256:83242584ed5e2ecaPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_nmoox5itgzv5u6ay)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260923.c8be18b latest | 2026-09-23 | c8be18b | 6,368 B | A | view · diff |
| git:20260920.72e113c | 2026-09-20 | 72e113c | 6,226 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6368 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
covagashi/eplan-development-skill · 3 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_nmoox5itgzv5u6ay GET https://markdownregistry.com/api/v1/resolve?ref=covagashi/eplan-development-skill/eec-pro-development GET https://markdownregistry.com/api/v1/blob/83242584ed5e2eca333ad65c602b78a0a2d42b0bff5b97bf4f6d7a0fdd22f54f
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.