Dbg
theodo-group/debug-that
Debug applications using the dbg CLI debugger. An agent skill from theodo-group/debug-that.
Routes truST behaviour changes from the written specification to a native executable test.
Install Trust Test Authoring
$ npx skills add johannesPettersson80/trust-platform --skill trust-test-authoring -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install johannesPettersson80/trust-platform trust-test-authoring --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-test-authoring .claude/skills/trust-test-authoring && 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-test-authoring" agent skill from https://github.com/johannesPettersson80/trust-platform/tree/main/.codex/skills/trust-test-authoring into .claude/skills/trust-test-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trust-test-authoring", 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-test-authoringType 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-test-authoring -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install johannesPettersson80/trust-platform trust-test-authoring --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-test-authoring .agents/skills/trust-test-authoring && 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-test-authoring" agent skill from https://github.com/johannesPettersson80/trust-platform/tree/main/.codex/skills/trust-test-authoring into .agents/skills/trust-test-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trust-test-authoring", 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-test-authoring -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install johannesPettersson80/trust-platform trust-test-authoring --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-test-authoring .cursor/skills/trust-test-authoring && 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-test-authoring" agent skill from https://github.com/johannesPettersson80/trust-platform/tree/main/.codex/skills/trust-test-authoring into .cursor/skills/trust-test-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trust-test-authoring", 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-test-authoring--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-test-authoring -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install johannesPettersson80/trust-platform trust-test-authoring --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-test-authoring .gemini/skills/trust-test-authoring && 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-test-authoring" agent skill from https://github.com/johannesPettersson80/trust-platform/tree/main/.codex/skills/trust-test-authoring into .gemini/skills/trust-test-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trust-test-authoring", 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-test-authoringInstalls 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-test-authoring -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-test-authoring .github/skills/trust-test-authoring && 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-test-authoring" agent skill from https://github.com/johannesPettersson80/trust-platform/tree/main/.codex/skills/trust-test-authoring into .github/skills/trust-test-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trust-test-authoring", 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-test-authoring -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-test-authoring --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-test-authoring .opencode/skills/trust-test-authoring && 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-test-authoring" agent skill from https://github.com/johannesPettersson80/trust-platform/tree/main/.codex/skills/trust-test-authoring into .opencode/skills/trust-test-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trust-test-authoring", 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-test-authoring- GitHub stars
- 222
- Token cost
- ~1.5k tokens
- SKILL.md length
- 823 words
- Files
- 1
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Routes truST behaviour changes from the written specification to a native executable test.
- Works in 7 steps: Read the owning specification. If the… → Read the current native assertions near… → Classify the behaviour as one of → …
- Malformed-input handling
- SKILL.md covers Route, By scenario and PLC verification program
- Calls bash
What it does
Trust Test Authoring is an agent skill from johannesPettersson80/trust-platform. Routes truST behaviour changes from the written specification to a native executable test. Use for any bug fix, feature, refactor, malformed-input handling, runtime-safety, VS Code, hardware, docs-only or supply-chain change, when deciding whether a specification or test is missing, and for PLC verification program work.
Its SKILL.md is about 1.5k 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, covering Debugging and Supply chain security. It works with Visual Studio Code, Rust 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
- Malformed-input handling
- Supply-chain change
- Deciding whether a specification
- Test is missing
Example prompts
- “Use the trust-test-authoring skill to route truST behaviour changes from the written specification to a native executable test”
- “/trust-test-authoring”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Read the owning specification. If the behaviour is missing, ambiguous or contradictory there,
- Read the current native assertions near the behaviour. A test name, catalog entry or report is
- Classify the behaviour as one of
- Write necessary assertions alongside the complete implementation. Before the batch, review
- Freeze implementation and test sources, then execute the deduplicated validation batch under
- Preserve existing behavior-lock assertions for refactors. For bug fixes, retain any existing
- Report
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:
bash
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 Test Authoring loads about 1.5k tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 823 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). 823 words, ~1,545 tokens.
Download SKILL.mdSave it as
.claude/skills/trust-test-authoring/SKILL.md (or your agent's skills folder).- name
- trust-test-authoring
- description
- Routes truST behaviour changes from the written specification to a native executable test. Use for any bug fix, feature, refactor, malformed-input handling, runtime-safety, VS Code, hardware, docs-only or supply-chain change, when deciding whether a specification or test is missing, and for PLC verification program work.
truST test authoring
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.
Logic is proven by a Rust test at the closest Rust boundary. A VS Code or Playwright test proves only wiring and rendering, and never stands in for the Rust test of logic.
A behaviour is part of the product when two things agree:
written specification -> native executable testThe written specification lives in docs/specs/ (or in an IEC or product decision). The native
executable test asserts the behaviour at the closest practical boundary. It can be a Rust test, a
VS Code suite test, a Playwright test or a device-in-the-loop case.
Never derive product work from these: an invariant, a catalog link, a denominator row, an evidence status, a proof level, a mutation result, a scanner fact, or a count of files or functions. They help you find history. Planner, catalog, denominator, and evidence tooling is nonblocking maintenance and cannot invent product requirements or tests. Only reading the owning specification and the native assertions directly shows that a specification or test is missing.
Route
- Read the owning specification. If the behaviour is missing, ambiguous or contradictory there, write or update the specification first. When the choice belongs to the user, ask. Do not invent behaviour.
- Read the current native assertions near the behaviour. A test name, catalog entry or report is not coverage.
- Classify the behaviour as one of:
already_coveredmissing_specmissing_testbehavior_defectexternal_manual
- Write necessary assertions alongside the complete implementation. Before the batch, review test imports/traits, feature and target gates, fixture registration, and the affected production path. For lifecycle changes, trace relevant transitions and alternate callers rather than testing only the reported happy path. Include native regressions plus required UI wiring proof.
- Freeze implementation and test sources, then execute the deduplicated validation batch under AGENTS.md. Include required compile/lint and behavior checks with the intended toolchains. A source review cannot certify that a new test compiles. Do not run per-edit or red/green loops.
- Preserve existing behavior-lock assertions for refactors. For bug fixes, retain any existing pre-fix failure evidence; do not invent it or launch an extra baseline run without authorization. Compile, harness, dependency, registration and timeout failures are not failed behavior assertions.
- Report:
- the specification sections;
- the test paths and names;
- the commands and their results;
- anything left unverified.
Show full SKILL.md (389 more words)Show less
By scenario
- bug fix: clarify the specification if needed, then write the regression assertion, make the fix, and include the regression in the final consolidated batch.
- refactor: use behavior-lock tests. Split large test files by capability and keep test names stable where possible.
- malformed input: assert a stable rejection, and assert that nothing was partly applied.
- VS Code: register the test in
index.ts. Prove visible behaviour in the rendered surface (trust-vscode-quality). - long end-to-end journey (an example or rendered journey that runs for many minutes):
- A check that does not block the next step records its failure, and the journey goes on. The journey fails at the end with every recorded failure, so one run names all the failures it reaches.
- Before asking for another run after a failure, trace every remaining step through the code, including the steps the run never reached, and fix every problem found in one go.
- When one user action has more than one code path, such as a restore in the same session and a restore from a saved checkpoint, the regression assertion covers the path the action really takes.
- runtime safety: run the runtime vertical (AGENTS.md). Fail-closed paths need their own
assertions (
st-lsp-solid). - hardware lab: run the device-in-the-loop case on the real reviewed topology. If the hardware is
unavailable, say so and leave the claim open (
trust-remote-builder). - docs-only: check every claim against native tests. Prose is not execution.
- supply-chain: run
bash scripts/supply_chain_gate.shand the release gates (trust-ci-release-gates). - CI-only regression: this is a failure seen only in a platform compile or warning lane.
- Keep the failed CI command and its log as the baseline.
- Add a focused gate with the same target and flags.
- Include that command in the authorized consolidated batch. Retain failures and follow the current retry authorization; do not loop until green. Host-only tests do not close it.
PLC verification program
The program's boards and history are in
docs/internal/testing/checklists/plc-verification-program/. Its corrective audit is
phase18-zero-debt-execution-board.md there. That audit may list only these items, each directly
confirmed:
- missing specifications;
- missing native tests;
- behaviour defects;
- explicit external or manual boundaries.
Pull-request workflows enforce native tests and specification drift checks. They may report
verification metadata, but they never reject a change only because a test lacks a catalog mapping.
Never derive product work from these metadata states: reviewed_nonmapping, ignored, skipped,
filtered out, unrun or zero-test.
© 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-test-authoring of johannesPettersson80/trust-platform.
Open the folder on GitHubat commit b7d8ffb
Compare with similar skills
Trust Test Authoring 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 Test Authoring this skilljohannesPettersson80/trust-platform | 222 | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Dbgtheodo-group/debug-that | 158 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Prepare Rslint npm Releaseweb-infra-dev/rslint | 461 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Vscode MCP Architecturetjx666/vscode-mcp | 105 | — | ~1.5k | Automated safety check: Pass | Custom licence | |
| Temporal Developertemporalio/skill-temporal-developer | 230 | — | ~2.5k | Automated safety check: Pass | MIT | |
| OpenLogi macOS Permissions TriageAprilNEA/OpenLogi | 23k | — | ~2.5k | Automated safety check: Notes | Apache-2.0 |
Similar skills
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.
Vscode MCP Architecture
tjx666/vscode-mcp
VSCode MCP Bridge project architecture — current monorepo layout, IPC/EventDispatcher flow, per-workspace socket discovery, MCP/CLI adapters, tool filtering, and VSCode extension services.
- Official
Temporal Developer
temporalio/skill-temporal-developer
Develop, debug, and manage Temporal applications across Python, TypeScript, Go, Java, .NET, Ruby, and Rust.
OpenLogi macOS Permissions Triage
AprilNEA/OpenLogi
Decides whether an OpenLogi device problem on macOS is a privacy-permission (TCC) problem, using agent log lines, and says which identity needs which grant.
Pnpm Engine
teambit/bit
Work on the pnpm Rust engine (@pnpm/napi, the pacquet crates) that bit install runs through.
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.
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.
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 Test Authoring
What does Trust Test Authoring do?
Routes truST behaviour changes from the written specification to a native executable test. Trust Test Authoring is an agent skill from johannesPettersson80/trust-platform. Routes truST behaviour changes from the written specification to a native executable test.
When should I use Trust Test Authoring?
Trust Test Authoring fits situations like: malformed-input handling; supply-chain change; deciding whether a specification; test is missing.
How do I install Trust Test Authoring in Claude Code?
Run `npx skills add johannesPettersson80/trust-platform --skill trust-test-authoring -a claude-code`. Or copy the skill folder (.codex/skills/trust-test-authoring in johannesPettersson80/trust-platform) into .claude/skills/trust-test-authoring in your project. Claude Code loads it when a task matches its description.
How do I install Trust Test Authoring in Codex?
Run `npx skills add johannesPettersson80/trust-platform --skill trust-test-authoring -a codex`. Or copy the skill folder (.codex/skills/trust-test-authoring in johannesPettersson80/trust-platform) into .agents/skills/trust-test-authoring in your project. Codex loads it when a task matches its description.
Can I use Trust Test Authoring 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-test-authoring -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-test-authoring, .gemini/skills/trust-test-authoring, .github/skills/trust-test-authoring and .opencode/skills/trust-test-authoring in your project.
What does Trust Test Authoring need to run?
Going by SKILL.md and its folder, Trust Test Authoring needs the command-line tools its instructions call (bash).
Does Trust Test Authoring 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 Test Authoring 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 Test Authoring use?
Trust Test Authoring 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 Test Authoring use?
About 1.5k tokens (SKILL.md is roughly 6.2k 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 Test Authoring?
Skills that share tags, products or a category with Trust Test Authoring: Dbg (theodo-group/debug-that, 158 stars), Prepare Rslint npm Release (web-infra-dev/rslint, 461 stars), Vscode MCP Architecture (tjx666/vscode-mcp, 105 stars) and Temporal Developer (temporalio/skill-temporal-developer, 230 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Trust Test Authoring?
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.