Smoke test

Skill jrausercisco/trmnl-agent-bridge/plugins/trmnl-agent-bridge/skills/smoke-test

Publish local agent status snapshots to TRMNL Private Plugin webhooks.

Install

npx -y skills add jrausercisco/trmnl-agent-bridge --skill smoke-test

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Run the TRMNL Agent Bridge smoke test in dry mode or live mode and summarize push and current-screen verification results.

SKILL.md

1.2 KB, 252 tokens by cl100k_base, as published. Nobody here has run it

Smoke Test

Use this skill when the user asks to test, validate, verify, or smoke-test the TRMNL Agent Bridge.

Dry Mode

Dry mode works without credentials and should be the default first check:

trmnl-agent smoke-test

From a local checkout:

PYTHONPATH=src python3 -m trmnl_agent_bridge.cli smoke-test

Live Mode

Use live mode only when the user has configured a test TRMNL Private Plugin webhook and explicitly wants a live push:

trmnl-agent smoke-test --push

When TRMNL device API credentials are also configured, verify the rendered screen path:

trmnl-agent smoke-test --push --fetch-screen --compare-screen --wait-seconds 30

Result Summary

Report:

overall ok
dry or live mode
payload bytes and limit
credential sources, never credential values
push attempted and HTTP status when present
current-screen fetch result when requested
whether the before/after screen hash changed when comparison was requested

Do not echo webhook URLs, API tokens, device IDs, image URLs, or private payload bodies.

Gives 0 of the 12 instructions most e2e browser skills give in 252 tokens

Counted across 407 of the 410 authors here whose files we hold, read 2026-08-06

use page object model patternin 35 of 407, across 25 files
Snapshot to get element refsin 24 of 407, across 14 files
keep tests independentin 23 of 407, across 18 files
Interact using refs from the latest snapshotin 23 of 407, across 11 files
clean up test data after each testin 21 of 407, across 15 files
test user behavior not implementationin 20 of 407, across 14 files
quarantine flaky tests explicitlyin 19 of 407, across 10 files
wait for specific network conditionsin 18 of 407, across 8 files
re-snapshot after navigation or dom changesin 17 of 407, across 10 files
Detect running dev servers before writing test codein 17 of 407, across 7 files
use web-first assertionsin 17 of 407, across 14 files
capture screenshots or videos on test failurein 17 of 407, across 14 files

Said here and by no other author read

use dry mode first
run the dry smoke test command
run live mode only when explicitly wanted
use live mode with configured webhook
verify screen path with configured credentials
report overall ok status

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.