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.
Builds and verifies truST's VS Code extension - commands, webviews, snippets, debug flows, Control Studio, HMI Builder, Devices & Connections and the test harness.
Install Trust Vscode Quality
$ npx skills add johannesPettersson80/trust-platform --skill trust-vscode-quality -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install johannesPettersson80/trust-platform trust-vscode-quality --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-vscode-quality .claude/skills/trust-vscode-quality && 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-vscode-quality" agent skill from https://github.com/johannesPettersson80/trust-platform/tree/main/.codex/skills/trust-vscode-quality into .claude/skills/trust-vscode-quality/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trust-vscode-quality", 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-vscode-qualityType 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-vscode-quality -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install johannesPettersson80/trust-platform trust-vscode-quality --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-vscode-quality .agents/skills/trust-vscode-quality && 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-vscode-quality" agent skill from https://github.com/johannesPettersson80/trust-platform/tree/main/.codex/skills/trust-vscode-quality into .agents/skills/trust-vscode-quality/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trust-vscode-quality", 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-vscode-quality -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install johannesPettersson80/trust-platform trust-vscode-quality --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-vscode-quality .cursor/skills/trust-vscode-quality && 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-vscode-quality" agent skill from https://github.com/johannesPettersson80/trust-platform/tree/main/.codex/skills/trust-vscode-quality into .cursor/skills/trust-vscode-quality/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trust-vscode-quality", 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-vscode-quality--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-vscode-quality -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install johannesPettersson80/trust-platform trust-vscode-quality --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-vscode-quality .gemini/skills/trust-vscode-quality && 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-vscode-quality" agent skill from https://github.com/johannesPettersson80/trust-platform/tree/main/.codex/skills/trust-vscode-quality into .gemini/skills/trust-vscode-quality/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trust-vscode-quality", 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-vscode-qualityInstalls 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-vscode-quality -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-vscode-quality .github/skills/trust-vscode-quality && 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-vscode-quality" agent skill from https://github.com/johannesPettersson80/trust-platform/tree/main/.codex/skills/trust-vscode-quality into .github/skills/trust-vscode-quality/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trust-vscode-quality", 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-vscode-quality -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-vscode-quality --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-vscode-quality .opencode/skills/trust-vscode-quality && 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-vscode-quality" agent skill from https://github.com/johannesPettersson80/trust-platform/tree/main/.codex/skills/trust-vscode-quality into .opencode/skills/trust-vscode-quality/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trust-vscode-quality", 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-vscode-quality- GitHub stars
- 222
- Token cost
- ~1.2k tokens
- SKILL.md length
- 585 words
- Files
- 1
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Builds and verifies truST's VS Code extension - commands, webviews, snippets, debug flows, Control Studio, HMI Builder, Devices & Connections and the test harness.
- Any change under editors/vscode
- SKILL.md covers Building a change, Running the tests, Screenshots of the real… and UI acceptance board
- Calls npm and python3
- For extension tests
What it does
Trust Vscode Quality is an agent skill from 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. Use for any change under editors/vscode, for extension tests, for real screenshots of the running extension, and for UI acceptance-board journeys and uxaccepted evidence.
Its SKILL.md is about 1.2k 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 Visual Studio Code, Rust, npm 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
- Any change under editors/vscode
- For extension tests
- For real screenshots of the running extension
- For UI acceptance-board journeys and uxaccepted evidence
Example prompts
- “Use the trust-vscode-quality skill to build and verifies truST's VS Code extension - commands, webviews, snippets, debug flows, Control Studio, HMI…”
- “/trust-vscode-quality”
Requirements
- Python 3
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:
npmpython3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.
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 Vscode Quality loads about 1.2k tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 585 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). 585 words, ~1,209 tokens.
Download SKILL.mdSave it as
.claude/skills/trust-vscode-quality/SKILL.md (or your agent's skills folder).- name
- trust-vscode-quality
- description
- Builds and verifies truST's VS Code extension - commands, webviews, snippets, debug flows, Control Studio, HMI Builder, Devices & Connections and the test harness. Use for any change under editors/vscode, for extension tests, for real screenshots of the running extension, and for UI acceptance-board journeys and ux_accepted evidence.
VS Code extension
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.
The extension is presentation and wiring only. A change that needs logic adds it in Rust, as a
trust-lsp command or a runtime-protocol operation; the extension calls it and renders the answer.
The TypeScript logic in Control Studio and in the HMI Builder is debt, listed in AGENTS.md: do not
extend it.
Building a change
Behaviour changes follow trust-test-authoring: the written specification first, then the native
test.
Surface: find the surface you are changing: a command, snippet, debug flow, webview, runtime lifecycle, diagnostics or the test harness. Update the
package.jsoncontributions when commands, views or snippets change.Behaviour:
- handle cancellation and conflicts;
- a disabled action shows its reason in the UI;
- generated files and config writes are deterministic and idempotent.
Look: new webview chrome uses the shared theme tokens, not one-off colours. Do not add a second Start/Run surface when the existing one can be wired by project kind.
Tests: tests go in
editors/vscode/src/test/suite/**. Register each new file insrc/test/suite/index.ts, then runpython3 scripts/check_vscode_test_registration.py. Cover:- the happy path and the cancel path;
- conflict prompts;
- single-root and multi-root workspaces;
- debug start and attach, when debug code changes;
- the rendered state of webviews.
A source-text assertion does not prove rendered behaviour.
Running the tests
Run them on the builder (see trust-remote-builder).
- Compile:
npm run compileineditors/vscode. Before a push, also runnpm run lint. - Focused:
TRUST_VSCODE_TEST_GREP='<suite title or regex>' npm test. It needs an X display,TMPDIRunder home, and the cargo lease.ST_LSP_TEST_SERVER=<path>/trust-lspreuses a built language server. - Full:
npm test, once, in the final round.
Show full SKILL.md (267 more words)Show less
Screenshots of the real extension
A claim about what the extension shows needs a screenshot of the real extension.
- Saved runners:
docs/internal/testing/evidence/vscode-ui-ux-acceptance/2026-06-25/runners/. This folder is local and ignored by git. If it is missing, say that capture proof is unavailable. There are two kinds:- Command-driven runners (
*-runner.js) start a headless Extension Development Host with@vscode/test-electron. A mocha test drivesvscode.commands.executeCommandand captures the Xvfb root. Use them for:- the first run;
- ST editing;
- Check/Run;
- Live Values (
trust-lsp.debug.io.write|force|releasewith{address, value}); - debugging;
- the HMI.
- CDP runners (
cdp_*.js) add--remote-debugging-port. They drive the webview's inner iframe (document.querySelector('iframe').contentDocument) to click and read the React DOM. One example is the Devices & Connections graph, where they click a.react-flow__nodeby its text with PointerEvents.
- Command-driven runners (
- Running a runner:
xvfb-run -a -s "-screen 0 1920x1080x24" node <runner>.js.- It needs
target/debug/trust-lsp,trust-debugandtrust-runtime. - It needs a cached
.vscode-test/vscode-linux-*. - Live Values and the HMI need addressed I/O: a
Configuration.stwithVAR_CONFIG … AT %QX0.0(or%QW0,%MW0).
- It needs
- On the Pi: Xvfb screenshots come out black unless you use the SwiftShader ANGLE flags and
import -window root. - Review: look at every screenshot yourself and judge it. Correct code is not a correct picture.
UI acceptance board
- Location: the board and its evidence live in
docs/internal/testing/evidence/vscode-ui-ux-acceptance/. - What a row names:
- its VS Code surface;
- the journey, as a user story;
- the preconditions and project kind;
- the tests or runners;
- the screenshot paths;
- the theme coverage: light, dark and high contrast for core surfaces.
- Acceptance: a row reaches
ux_acceptedonly with its evidence attached and a reviewer who is not the implementer. CLI-only proof never closes a visible row.
© 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-vscode-quality of johannesPettersson80/trust-platform.
Open the folder on GitHubat commit b7d8ffb
Compare with similar skills
Trust Vscode Quality 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 Vscode Quality this skilljohannesPettersson80/trust-platform | 222 | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Prepare Rslint npm Releaseweb-infra-dev/rslint | 461 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Testing Changespnpm/pnpm | 37k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Install Language Serversweave-os/router | 5.6k | — | ~745 | Automated safety check: Notes | Apache-2.0 | |
| Pump Build Releasenirholas/pump-fun-sdk | 134 | — | ~620 | Automated safety check: Pass | Custom licence | |
| Vscode Extensionmicrosoft/aspire | 6.4k | — | ~2.8k | Automated safety check: Pass | MIT |
Similar skills
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…
Install Language Servers
weave-os/router
Installs a language server such as gopls, typescript-language-server, pyright or rust-analyzer and, with explicit confirmation, its underlying toolchain so the lsp tool can use it.
Pump Build Release
nirholas/pump-fun-sdk
Build and release pipeline for the Pump SDK — tsup TypeScript builds, Cargo release profiles, semantic release with commitizen, npm publishing, linting, Makefile targets, Vercel deployment, and MCP…
- Official
Vscode Extension
microsoft/aspire
A skill your agent uses when investigating, developing, debugging, testing, or reviewing Aspire VS Code extension behavior under extension/, including extension UI, command, debugger, RPC, DCP, MCP…
Release
Bloom-Engine/engine
Cut a new Bloom Engine release — bump package.json if requested, commit, tag, push, create GitHub Release, and watch the gated release pipeline
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 Lsp Iec
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.
Related
Works with
Categories
Questions about Trust Vscode Quality
What does Trust Vscode Quality do?
Builds and verifies truST's VS Code extension - commands, webviews, snippets, debug flows, Control Studio, HMI Builder, Devices & Connections and the test harness. Trust Vscode Quality is an agent skill from 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.
When should I use Trust Vscode Quality?
Trust Vscode Quality fits situations like: any change under editors/vscode; for extension tests; for real screenshots of the running extension; for UI acceptance-board journeys and uxaccepted evidence.
How do I install Trust Vscode Quality in Claude Code?
Run `npx skills add johannesPettersson80/trust-platform --skill trust-vscode-quality -a claude-code`. Or copy the skill folder (.codex/skills/trust-vscode-quality in johannesPettersson80/trust-platform) into .claude/skills/trust-vscode-quality in your project. Claude Code loads it when a task matches its description.
How do I install Trust Vscode Quality in Codex?
Run `npx skills add johannesPettersson80/trust-platform --skill trust-vscode-quality -a codex`. Or copy the skill folder (.codex/skills/trust-vscode-quality in johannesPettersson80/trust-platform) into .agents/skills/trust-vscode-quality in your project. Codex loads it when a task matches its description.
Can I use Trust Vscode Quality 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-vscode-quality -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-vscode-quality, .gemini/skills/trust-vscode-quality, .github/skills/trust-vscode-quality and .opencode/skills/trust-vscode-quality in your project.
What does Trust Vscode Quality need to run?
Going by SKILL.md and its folder, Trust Vscode Quality needs the command-line tools its instructions call (npm and python3). Our summary lists: Python 3.
Does Trust Vscode Quality access the network?
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Trust Vscode Quality 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 Vscode Quality use?
Trust Vscode Quality 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 Vscode Quality use?
About 1.2k tokens (SKILL.md is roughly 4.8k 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 Vscode Quality?
Skills that share tags, products or a category with Trust Vscode Quality: Prepare Rslint npm Release (web-infra-dev/rslint, 461 stars), Testing Changes (pnpm/pnpm, 37k stars), Install Language Servers (weave-os/router, 5.6k stars) and Pump Build Release (nirholas/pump-fun-sdk, 134 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Trust Vscode Quality?
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.