Agent skill

System Bridge Testing Workflow

by timmo001 in timmo001/system-bridge

How to test System Bridge - Go table-driven tests and commands, web-client quality checks (lint/typecheck/format, no unit tests), the Chrome DevTools MCP interactive test loop for UI and WebSocket…

Apache-2.0Auto-check passedTesting & QA

Install System Bridge Testing Workflow

skills CLI
$ npx skills add timmo001/system-bridge --skill system-bridge-testing-workflow -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install timmo001/system-bridge system-bridge-testing-workflow --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/timmo001/system-bridge.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/system-bridge-testing-workflow .claude/skills/system-bridge-testing-workflow && rm -rf skills-src

Use ~/.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/

Facts

Skill name
system-bridge-testing-workflow
GitHub stars
356
Token cost
~843 tokens
SKILL.md length
208 words
Files
1
Skills in repo
12
Repo updated
First seen
Licence
Apache-2.0

At a glance

How to test System Bridge - Go table-driven tests and commands, web-client quality checks (lint/typecheck/format, no unit tests), the Chrome DevTools MCP interactive test loop for UI and WebSocket…

  • Works in 3 steps: mise run generate:schemas to regenerate… → mise run run and open the relevant page. → Confirm no console errors, data…
  • Running system-bridge tests
  • SKILL.md covers Go Tests, Web Client Quality, Interactive Testing with… and Verifying Schema Changes, plus 2 more sections
  • Calls mise, go and bun; needs GITHUB_TOKEN

What it does

System Bridge Testing Workflow is an agent skill from timmo001/system-bridge. How to test System Bridge - Go table-driven tests and commands, web-client quality checks (lint/typecheck/format, no unit tests), the Chrome DevTools MCP interactive test loop for UI and WebSocket, the generate:schemas verification cycle, and running GitHub workflows locally with act. Use when writing or running system-bridge tests, verifying Go type/schema changes, or interactively testing the web client.

Its SKILL.md is about 840 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 Testing & QA, covering Browser testing, Realtime and WebSockets and Unit testing. It works with Model Context Protocol, Chrome DevTools and GitHub Actions. The repository describes itself as: A bridge for your systems. The licence is Apache-2.0.

When your agent uses it

  • Running system-bridge tests
  • Verifying Go type/schema changes
  • Interactively testing the web client

Example prompts

  • “/system-bridge-testing-workflow”

Requirements

  • Docker
  • A credential in GITHUB_TOKEN

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. mise run generate:schemas to regenerate the Zod schemas.
  2. mise run run and open the relevant page.
  3. Confirm no console errors, data validates, and new fields render.

What it can do on your machine

Read from SKILL.md and the folder at commit 608d62d. 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:

    • mise
    • go
    • bun

    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 these keys or tokens, usually read from environment variables:

    • GITHUB_TOKEN

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

System Bridge Testing Workflow loads about 843 tokens when it runs. Until then it costs about 110 tokens; SKILL.md has 208 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~110
When it runs · the whole SKILL.md, loaded when a task matches
~843

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 timmo001/system-bridge at commit 608d62d, republished under its Apache-2.0 licence (© timmo001). 208 words, ~843 tokens.

Download SKILL.mdSave it as .claude/skills/system-bridge-testing-workflow/SKILL.md (or your agent's skills folder).
name
system-bridge-testing-workflow
description
How to test System Bridge - Go table-driven tests and commands, web-client quality checks (lint/typecheck/format, no unit tests), the Chrome DevTools MCP interactive test loop for UI and WebSocket, the generate:schemas verification cycle, and running GitHub workflows locally with act. Use when writing or running system-bridge tests, verifying Go type/schema changes, or interactively testing the web client.

System Bridge Testing

Go Tests

bash
mise run test                              # all Go tests
go test -v ./...                           # verbose
go test ./data/module/...                  # one package
go test -run TestCPUModule ./data/module/  # one test
go test -race ./...                        # race detector
go test -cover ./...                       # coverage

Place tests in *_test.go beside the code. Use table-driven tests:

go
tests := []struct {
    name    string
    input   DataInput
    want    DataOutput
    wantErr bool
}{
    {"valid input", validInput, expectedOutput, false},
    {"invalid format", badInput, DataOutput{}, true},
}
for _, tt := range tests {
    t.Run(tt.name, func(t *testing.T) { /* ... */ })
}

Mock external dependencies (filesystem, network, system calls). Keep tests fast; avoid sleeps.

Web Client Quality

The web client has no automated unit tests (Playwright/web-test-runner were removed). Quality is enforced by lint, typecheck, and format:

bash
cd web-client
bun run lint        # Oxlint with type-aware, Lit and Web Components rules
bun run typecheck   # tsc --noEmit
bun run format:check

Run the full application lint (Go + web client) with mise run lint:all. Docs have a separate check: mise run docs:build and mise run docs:lint.

Interactive Testing with Chrome DevTools MCP

Functional web-client testing is done via the chrome-devtools MCP server.

bash
mise run run   # backend (port 9170) + web client (port 5173)

Open http://localhost:5173 in Chrome, then drive it with the MCP tools:

  • take_snapshot to read page state (add verbose=true to inspect ARIA).
  • click uid=..., fill uid=... value=..., navigate_page type="url" url=....
  • list_console_messages / get_console_message msgid=... to catch errors.
  • list_network_requests / get_network_request reqid=... for WebSocket traffic.

Always check the console for Zod validation errors after navigating the module tabs (Battery, CPU, Disks, ...).

Verifying Schema Changes

After changing a Go struct in types/:

  1. mise run generate:schemas to regenerate the Zod schemas.
  2. mise run run and open the relevant page.
  3. Confirm no console errors, data validates, and new fields render.

Never hand-edit web-client/src/lib/system-bridge/types-modules-schemas.ts - it is generated.

Running GitHub Workflows Locally

bash
act                                        # all workflows
act -W .github/workflows/<name>.yml        # one workflow
act -j <job>                               # one job
act -l                                     # list

Docker commands under act need sudo; pass secrets with -s GITHUB_TOKEN=....

Quick Reference

bash
mise run test
cd web-client && bun run lint && bun run typecheck
go run . client data run --module cpu --pretty   # exercise a data module

© timmo001, 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 .agents/skills/system-bridge-testing-workflow of timmo001/system-bridge.

Open the folder on GitHubat commit 608d62d

Compare with similar skills

System Bridge Testing Workflow 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.

System Bridge Testing Workflow compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
System Bridge Testing Workflow this skilltimmo001/system-bridge356—~843Automated safety check: PassApache-2.0
Chrome Devtools MCPmanagedcode/dotnet-skills486—~2.2kAutomated safety check: PassMIT
Playwright Visual Testingmanagedcode/dotnet-skills486—~1.9kAutomated safety check: PassMIT
PlaywrightEliasOulkadi/shokunin114—~3.6kAutomated safety check: NotesMIT
Cdp Connectadobe/skills195—~847Automated safety check: PassApache-2.0
Spider Kingaoyunyang/spider-king-skill507—~7.3kAutomated safety check: PassMIT

Similar skills

  • Chrome Devtools MCP

    managedcode/dotnet-skills

    Use Chrome DevTools MCP from .NET agents and .NET-focused repos to inspect, debug, and automate Chrome through an MCP client.

    486 GitHub stars~2.2k tokensUpdated today
    DevelopmentAuto-check passed
  • Playwright Visual Testing

    managedcode/dotnet-skills

    Add, repair, or review Playwright visual regression tests for browser-facing .NET apps, including screenshot baselines, Pixelmatch thresholds, deterministic rendering, and GitHub Actions artifacts.

    486 GitHub stars~1.9k tokensUpdated today
    Testing & QAAuto-check passed
  • Playwright

    EliasOulkadi/shokunin

    Browser automation, web scraping, E2E testing, and visual regression with Playwright.

    114 GitHub stars~3.6k tokensUpdated 2 days ago
    Testing & QAAuto-check: notes
  • Cdp Connect

    adobe/skills

    Connect Claude Code to an existing Chrome browser via CDP (Chrome DevTools Protocol).

    195 GitHub stars~847 tokensUpdated today
    Productivity & AutomationAuto-check passed
  • Spider King

    aoyunyang/spider-king-skill

    Pure-web protocol reverse skill: turn hostile browser clients into browser-free Python collectors.

    507 GitHub stars~7.3k tokensUpdated 1 mo ago
    Backend & APIsAuto-check passed
  • Connects an agent to a real Chrome instance through the Chrome DevTools MCP server, so it can inspect the DOM, read console errors and profile performance directly.

    102k GitHub starsUsed in 4 repos~3.5k tokens
    Testing & QAAuto-check: warnings

More from timmo001/system-bridge

All 12 skills in this repo
  • Writing Style

    timmo001/system-bridge

    Write commit messages, PR and issue text and comments, docs (README), code comments, and user-facing strings (notifications, UI labels, toasts, error messages) in the project owner's voice: concise…

    356 GitHub stars~3.3k tokensUpdated today
    Auto-check passed
  • System Bridge Go Backend

    timmo001/system-bridge

    System Bridge Go backend conventions - error wrapping, graceful degradation for data modules, nil-pointer safety, context-aware Module.Update, structured slog logging, and errcheck-clean deferred…

    356 GitHub stars~841 tokensUpdated today
    Auto-check passed
  • System Bridge Troubleshooting

    timmo001/system-bridge

    Known System Bridge build and runtime failures and their fixes, plus per-OS token/log/settings/data file locations.

    356 GitHub stars~637 tokensUpdated today
    Auto-check passed
  • System Bridge Docs Page Workflow

    timmo001/system-bridge

    Add or restructure a page in the System Bridge Astro + Starlight docs site under docs/ - create the content file, set frontmatter, and wire the sidebar.

    356 GitHub stars~376 tokensUpdated today
    Auto-check passed
  • Update the System Bridge marketing landing page in the Astro + Starlight docs site.

    356 GitHub stars~313 tokensUpdated today
    Auto-check passed
  • Changeset Scope

    timmo001/system-bridge

    Keep all scoped code work contained to the user-defined changeset.

    356 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

Questions about System Bridge Testing Workflow

What does System Bridge Testing Workflow do?

How to test System Bridge - Go table-driven tests and commands, web-client quality checks (lint/typecheck/format, no unit tests), the Chrome DevTools MCP interactive test loop for UI and WebSocket…. System Bridge Testing Workflow is an agent skill from timmo001/system-bridge. How to test System Bridge - Go table-driven tests and commands, web-client quality checks (lint/typecheck/format, no unit tests), the Chrome DevTools MCP interactive test loop for UI and WebSocket, the generate:schemas verification cycle, and running GitHub workflows locally with act.

When should I use System Bridge Testing Workflow?

System Bridge Testing Workflow fits situations like: running system-bridge tests; verifying Go type/schema changes; interactively testing the web client.

How do I install System Bridge Testing Workflow in Claude Code?

Run `npx skills add timmo001/system-bridge --skill system-bridge-testing-workflow -a claude-code`. Or copy the skill folder (.agents/skills/system-bridge-testing-workflow in timmo001/system-bridge) into .claude/skills/system-bridge-testing-workflow in your project. Claude Code loads it when a task matches its description.

How do I install System Bridge Testing Workflow in Codex?

Run `npx skills add timmo001/system-bridge --skill system-bridge-testing-workflow -a codex`. Or copy the skill folder (.agents/skills/system-bridge-testing-workflow in timmo001/system-bridge) into .agents/skills/system-bridge-testing-workflow in your project. Codex loads it when a task matches its description.

Can I use System Bridge Testing Workflow 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 timmo001/system-bridge --skill system-bridge-testing-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/system-bridge-testing-workflow, .gemini/skills/system-bridge-testing-workflow, .github/skills/system-bridge-testing-workflow and .opencode/skills/system-bridge-testing-workflow in your project.

What does System Bridge Testing Workflow need to run?

Going by SKILL.md and its folder, System Bridge Testing Workflow needs the command-line tools its instructions call (mise, go and bun) and credentials named GITHUB_TOKEN. Our summary lists: Docker; A credential in GITHUB_TOKEN.

Does System Bridge Testing Workflow 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 System Bridge Testing Workflow 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 System Bridge Testing Workflow use?

System Bridge Testing Workflow 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 System Bridge Testing Workflow use?

About 843 tokens (SKILL.md is roughly 3.4k 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 System Bridge Testing Workflow?

Skills that share tags, products or a category with System Bridge Testing Workflow: Chrome Devtools MCP (managedcode/dotnet-skills, 486 stars), Playwright Visual Testing (managedcode/dotnet-skills, 486 stars), Playwright (EliasOulkadi/shokunin, 114 stars) and Cdp Connect (adobe/skills, 195 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains System Bridge Testing Workflow?

timmo001 (a GitHub user) maintains it in timmo001/system-bridge, which has 356 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 7, 2026.

Source: timmo001/system-bridge on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.