Prepare Rslint npm Release
web-infra-dev/rslint
Prepare a stable release PR for the unified rslint npm packages by updating package versions and rule/TypeScript release metadata.
Guides IEC 61131-3 Structured Text language work in truST - lexer, parser, types, semantics, standard functions and function blocks, OOP, namespaces and editor features - checked against the standard.
Install Trust Lsp Iec
$ npx skills add johannesPettersson80/trust-platform --skill trust-lsp-iec -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install johannesPettersson80/trust-platform trust-lsp-iec --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/johannesPettersson80/trust-platform.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/trust-lsp-iec .claude/skills/trust-lsp-iec && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "trust-lsp-iec" agent skill from https://github.com/johannesPettersson80/trust-platform/tree/main/.codex/skills/trust-lsp-iec into .claude/skills/trust-lsp-iec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trust-lsp-iec", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/johannesPettersson80/trust-platform/tree/main/.codex/skills/trust-lsp-iecType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add johannesPettersson80/trust-platform --skill trust-lsp-iec -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install johannesPettersson80/trust-platform trust-lsp-iec --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/johannesPettersson80/trust-platform.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/trust-lsp-iec .agents/skills/trust-lsp-iec && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "trust-lsp-iec" agent skill from https://github.com/johannesPettersson80/trust-platform/tree/main/.codex/skills/trust-lsp-iec into .agents/skills/trust-lsp-iec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trust-lsp-iec", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add johannesPettersson80/trust-platform --skill trust-lsp-iec -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install johannesPettersson80/trust-platform trust-lsp-iec --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/johannesPettersson80/trust-platform.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/trust-lsp-iec .cursor/skills/trust-lsp-iec && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "trust-lsp-iec" agent skill from https://github.com/johannesPettersson80/trust-platform/tree/main/.codex/skills/trust-lsp-iec into .cursor/skills/trust-lsp-iec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trust-lsp-iec", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/johannesPettersson80/trust-platform.git --path .codex/skills/trust-lsp-iec--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add johannesPettersson80/trust-platform --skill trust-lsp-iec -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install johannesPettersson80/trust-platform trust-lsp-iec --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/johannesPettersson80/trust-platform.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/trust-lsp-iec .gemini/skills/trust-lsp-iec && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "trust-lsp-iec" agent skill from https://github.com/johannesPettersson80/trust-platform/tree/main/.codex/skills/trust-lsp-iec into .gemini/skills/trust-lsp-iec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trust-lsp-iec", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install johannesPettersson80/trust-platform trust-lsp-iecInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add johannesPettersson80/trust-platform --skill trust-lsp-iec -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/johannesPettersson80/trust-platform.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/trust-lsp-iec .github/skills/trust-lsp-iec && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "trust-lsp-iec" agent skill from https://github.com/johannesPettersson80/trust-platform/tree/main/.codex/skills/trust-lsp-iec into .github/skills/trust-lsp-iec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trust-lsp-iec", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add johannesPettersson80/trust-platform --skill trust-lsp-iec -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install johannesPettersson80/trust-platform trust-lsp-iec --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/johannesPettersson80/trust-platform.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/trust-lsp-iec .opencode/skills/trust-lsp-iec && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "trust-lsp-iec" agent skill from https://github.com/johannesPettersson80/trust-platform/tree/main/.codex/skills/trust-lsp-iec into .opencode/skills/trust-lsp-iec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trust-lsp-iec", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
trust-lsp-iec- GitHub stars
- 222
- Token cost
- ~1.1k tokens
- SKILL.md length
- 473 words
- Files
- 1
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Guides IEC 61131-3 Structured Text language work in truST - lexer, parser, types, semantics, standard functions and function blocks, OOP, namespaces and editor features - checked against the standard.
- Works in 7 steps: Identify the area and its specification… → Find the IEC section or table, and cite… → Write the focused test at the closest… → …
- Changing language behaviour
- SKILL.md covers Workflow, Where a decision is recorded and The standard
- Calls cargo, rg and pdftotext
What it does
Trust Lsp Iec is an agent skill from johannesPettersson80/trust-platform. Guides IEC 61131-3 Structured Text language work in truST - lexer, parser, types, semantics, standard functions and function blocks, OOP, namespaces and editor features - checked against the standard. Use when changing language behaviour or the standard library, editing language chapters in docs/specs, or deciding whether something belongs in docs/IECDECISIONS.md, docs/IECDEVIATIONS.md or a product specification.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. It works with Rust, Visual Studio Code and TypeScript. The repository describes itself as: truST Platform — IEC 61131‑3 Structured Text tooling suite. The licence is Apache-2.0.
When your agent uses it
- Changing language behaviour
- The standard library
- Editing language chapters in docs/specs
- Deciding whether something belongs in docs/IECDECISIONS.md
Example prompts
- “Use the trust-lsp-iec skill to guide IEC 61131-3 Structured Text language work in truST - lexer, parser, types, semantics, standard functions and…”
- “/trust-lsp-iec”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Identify the area and its specification in docs/specs/ (docs/specs/README.md maps them).
- Find the IEC section or table, and cite it in the specification edit.
- Write the focused test at the closest layer together with the change (trust-test-authoring).
- Implement in the owning crate
- A new language feature also extends crates/trust-runtime/tests/fixtures/complete_program/. Then
- If you touched standard functions, update docs/specs/coverage/standard-functions-coverage.md.
- For a change visible in the editor, run the VS Code extension tests. Update editors/vscode/README.md
What it can do on your machine
Read from SKILL.md and the folder at commit b7d8ffb. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
cargorgpdftotext
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Trust Lsp Iec loads about 1.1k tokens when it runs. Until then it costs about 108 tokens; SKILL.md has 473 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from johannesPettersson80/trust-platform at commit b7d8ffb, republished under its Apache-2.0 licence (© johannesPettersson80). 473 words, ~1,084 tokens.
Download SKILL.mdSave it as
.claude/skills/trust-lsp-iec/SKILL.md (or your agent's skills folder).- name
- trust-lsp-iec
- description
- Guides IEC 61131-3 Structured Text language work in truST - lexer, parser, types, semantics, standard functions and function blocks, OOP, namespaces and editor features - checked against the standard. Use when changing language behaviour or the standard library, editing language chapters in docs/specs, or deciding whether something belongs in docs/IEC_DECISIONS.md, docs/IEC_DEVIATIONS.md or a product specification.
IEC 61131-3 language work
Hard rule (AGENTS.md): all logic is in Rust. Logic is anything whose result is stored, sent to a runtime or PLC, or decides an engineering or operator outcome. TypeScript only presents (drawing, layout, mouse interaction, view state) and forwards requests to Rust. Never add logic in TypeScript. Existing TypeScript logic is debt to move into Rust, not to extend.
Language behaviour is computed in the Rust crates named below; the extension only shows the language server's answers.
Workflow
- Identify the area and its specification in
docs/specs/(docs/specs/README.mdmaps them). The areas are lexing, parsing, types, semantics, standard functions and function blocks, OOP, namespaces, runtime-assisted language features and editor UX. - Find the IEC section or table, and cite it in the specification edit.
- Write the focused test at the closest layer together with the change (
trust-test-authoring). The layer can be syntax, HIR, IDE, LSP, runtime or extension. - Implement in the owning crate:
trust-syntax: lexer and parser;trust-hir: types, semantics and standard semantics;trust-ide: diagnostics, completion and hover;trust-lsp: wiring;trust-runtimeortrust-debug: when the language server uses runtime data.
- A new language feature also extends
crates/trust-runtime/tests/fixtures/complete_program/. Then runcargo test -p trust-runtime --test complete_program. - If you touched standard functions, update
docs/specs/coverage/standard-functions-coverage.md. - For a change visible in the editor, run the VS Code extension tests. Update
editors/vscode/README.mdwhen the user-facing surface changes.
Show full SKILL.md (242 more words)Show less
Where a decision is recorded
docs/IEC_DEVIATIONS.mdis only for cases where truST intentionally conflicts with, omits or relaxes a normative IEC requirement. Before adding an entry:- cite the exact section or table;
- state the requirement;
- state truST's behaviour;
- explain the concrete conflict.
If you cannot state a conflict, there is no deviation. Existing entries are not precedent.
docs/IEC_DECISIONS.mdrecords the reading chosen where the IEC text genuinely allows several, with the citation.The relevant product specification records behaviour that IEC does not govern, even when it is intentional and tested:
- IEC-silent or out-of-scope behaviour;
- implementation-specific, platform, runtime or CLI behaviour;
- truST-only APIs.
Examples are a runtime API default, a file format, a protocol version or a tool limit.
PLCopen Motion choices go in
docs/PLCOPEN_DECISIONS.mdanddocs/PLCOPEN_DEVIATIONS.md.
The standard
Sources: the authoritative source is
docs/internal/standards/IEC 61131-3_2013 Ed3.pdf. For searching (rg -n), usedocs/internal/standards/iec61131-3.txt. Neither file is in git.If both are missing: when
~/Downloads/iec-61131-3.ocr.txtexists, copy it todocs/internal/standards/iec61131-3.txt. Otherwise, state that the standard is unavailable before claiming conformance.Extract one page:
pdftotext -f <page> -l <page> "docs/internal/standards/IEC 61131-3_2013 Ed3.pdf" - | sed -n '1,200p'Key tables:
Tables Content 1–9 lexical elements and literals 10 and figure 5 elementary types and the generic hierarchy 13–16 variables, direct addressing, arrays 19, 40, 47, 48, 51 FUNCTION, FUNCTION_BLOCK, PROGRAM, CLASS, INTERFACE 22–36 standard functions and conversions 43–46 standard function blocks 71 operators and their precedence 72 statements More references:
docs/internal/standards/IEC_ST_FEATURE_MATRIX.md,docs/specs/10-runtime-semantics.mdanddocs/internal/testing/checklists/lsp.md.
© johannesPettersson80, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .codex/skills/trust-lsp-iec of johannesPettersson80/trust-platform.
Open the folder on GitHubat commit b7d8ffb
Compare with similar skills
Trust Lsp Iec next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Trust Lsp Iec this skilljohannesPettersson80/trust-platform | 222 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Prepare Rslint npm Releaseweb-infra-dev/rslint | 461 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Pnpm Engineteambit/bit | 18k | — | ~1.9k | Automated safety check: Pass | Custom licence | |
| Testing Changespnpm/pnpm | 37k | — | ~1.1k | Automated safety check: Pass | MIT | |
| jscpd Code Migration Trackerkucherenko/jscpd | 6.4k | — | ~5k | Automated safety check: Pass | MIT | |
| Cross-Language Coding Standardszereight/gitlab-mcp | 2k | 1 repos | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
Pnpm Engine
teambit/bit
Work on the pnpm Rust engine (@pnpm/napi, the pacquet crates) that bit install runs through.
Testing Changes
pnpm/pnpm
Run the tests that cover a change in the pnpm repository, in the Rust workspace (pnpm/, pnpr/) or the TypeScript CLI (pnpm11/), and recognize the cases where a scoped run passes without testing…
jscpd Code Migration Tracker
kucherenko/jscpd
Measures a code port between languages or frameworks with jscpd's function-level comparison, porting tests before code and tracking what is left unmatched.
Cross-Language Coding Standards
zereight/gitlab-mcp
Shared reference for naming, function size, complexity and error handling rules that reviewer agents apply across TypeScript, Python, Go, Rust, Java, C# and Swift.
- Official
Code Migration
anthropics/code-migration-kit-with-claude-code
Run a large-scale language migration with the six-step process: create the map and the rules, stress-test the rules, translate everything, compile, run it, match behavior.
More from johannesPettersson80/trust-platform
Trust CI Release Gates
johannesPettersson80/trust-platform
Prepares and ships truST changes - changelog and version updates, CI parity, pre-push checks, the exact-SHA release-candidate guard, merge, tag and release verification.
Trust Remote Builder
johannesPettersson80/trust-platform
Runs truST builds and tests on the shared trust-builder machine.
Trust Test Authoring
johannesPettersson80/trust-platform
Routes truST behaviour changes from the written specification to a native executable test.
St Lsp Solid
johannesPettersson80/trust-platform
Keeps truST's architecture simple and well separated, and runs the automated architecture checks.
Trust Hmi Contracts
johannesPettersson80/trust-platform
Guides work on truST's HMI - the HMI Builder editor, page files, the runtime display at /hmi, bindings, commands and writes, authorization, alarms and trends, the plant library and the HMI tests.
Trust Vscode Quality
johannesPettersson80/trust-platform
Builds and verifies truST's VS Code extension - commands, webviews, snippets, debug flows, Control Studio, HMI Builder, Devices & Connections and the test harness.
Related
Works with
Categories
Questions about Trust Lsp Iec
What does Trust Lsp Iec do?
Guides IEC 61131-3 Structured Text language work in truST - lexer, parser, types, semantics, standard functions and function blocks, OOP, namespaces and editor features - checked against the standard. Trust Lsp Iec is an agent skill from johannesPettersson80/trust-platform. Guides IEC 61131-3 Structured Text language work in truST - lexer, parser, types, semantics, standard functions and function blocks, OOP, namespaces and editor features - checked against the standard.
When should I use Trust Lsp Iec?
Trust Lsp Iec fits situations like: changing language behaviour; the standard library; editing language chapters in docs/specs; deciding whether something belongs in docs/IECDECISIONS.md.
How do I install Trust Lsp Iec in Claude Code?
Run `npx skills add johannesPettersson80/trust-platform --skill trust-lsp-iec -a claude-code`. Or copy the skill folder (.codex/skills/trust-lsp-iec in johannesPettersson80/trust-platform) into .claude/skills/trust-lsp-iec in your project. Claude Code loads it when a task matches its description.
How do I install Trust Lsp Iec in Codex?
Run `npx skills add johannesPettersson80/trust-platform --skill trust-lsp-iec -a codex`. Or copy the skill folder (.codex/skills/trust-lsp-iec in johannesPettersson80/trust-platform) into .agents/skills/trust-lsp-iec in your project. Codex loads it when a task matches its description.
Can I use Trust Lsp Iec in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add johannesPettersson80/trust-platform --skill trust-lsp-iec -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/trust-lsp-iec, .gemini/skills/trust-lsp-iec, .github/skills/trust-lsp-iec and .opencode/skills/trust-lsp-iec in your project.
What does Trust Lsp Iec need to run?
Going by SKILL.md and its folder, Trust Lsp Iec needs the command-line tools its instructions call (cargo, rg and pdftotext).
Does Trust Lsp Iec access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Trust Lsp Iec safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Trust Lsp Iec use?
Trust Lsp Iec is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Trust Lsp Iec use?
About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Trust Lsp Iec?
Skills that share tags, products or a category with Trust Lsp Iec: Prepare Rslint npm Release (web-infra-dev/rslint, 461 stars), Pnpm Engine (teambit/bit, 18k stars), Testing Changes (pnpm/pnpm, 37k stars) and jscpd Code Migration Tracker (kucherenko/jscpd, 6.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Trust Lsp Iec?
johannesPettersson80 (a GitHub user) maintains it in johannesPettersson80/trust-platform, which has 222 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 11, 2026.
Source: johannesPettersson80/trust-platform on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.