agentsclimarketplace

Setup

Skill jrausercisco/trmnl-agent-bridge/plugins/trmnl-agent-bridge/skills/setup

Publish local agent status snapshots to TRMNL Private Plugin webhooks.

Install
npx -y skills add jrausercisco/trmnl-agent-bridge --skill setup

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

Help a user install the trmnl-agent CLI, configure a TRMNL Private Plugin webhook, and verify a safe dry-run payload.

SKILL.md

1.6 KB, 371 tokens by cl100k_base, as published. Nobody here has run it

Setup

Use this skill when the user asks to set up TRMNL Agent Bridge for Codex.

Workflow

  1. Verify the CLI is available:
trmnl-agent status

If the package is being used from a local checkout, run from the repository root:

PYTHONPATH=src python3 -m trmnl_agent_bridge.cli status
  1. Have the user create a TRMNL Private Plugin and choose the Webhook data strategy.
  2. Have the user paste templates/agent-status.liquid.html into the TRMNL plugin markup editor. For recipe-style setup, use trmnl_plugin/markup_full.html, trmnl_plugin/markup_half_horizontal.html, trmnl_plugin/markup_half_vertical.html, and trmnl_plugin/markup_quadrant.html.
  3. Store the webhook URL in an environment variable or macOS Keychain:
trmnl-agent keychain-set --account TRMNL_WEBHOOK_URL
  1. Validate with a dry-run synthetic payload:
trmnl-agent sample --source codex | trmnl-agent push --stdin --dry-run
  1. Only after the dry run succeeds, push a synthetic payload:
trmnl-agent sample --source codex | trmnl-agent push --stdin

From a repository checkout, examples/sample-payload.json and examples/sample-codex-status.json can also be used for local validation.

Safety

Webhook URLs, device IDs, and API tokens are secrets. Never put them in committed files, screenshots, logs, issue bodies, or chat output. Keep all setup validation on synthetic payloads until the user explicitly asks for a real status update.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.